mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH fixup v1] of: base: register DT root as device
Date: Wed, 12 Aug 2020 20:15:21 +0200	[thread overview]
Message-ID: <8face7c6-f022-797d-af37-b2b66e6eb255@pengutronix.de> (raw)
In-Reply-To: <20200812161109.66jgmksevsru3w5c@pengutronix.de>

Hi,

On 8/12/20 6:11 PM, Oleksij Rempel wrote:
>>> dt is used to make clear: it is root of dt and not some random root of
>>> what ever.
>>
>> It's redundant, there is already a .of suffix.
>> I like machine.of more though.

Makes me think. If we have a top level "dt-root" node,
won't this clash?


>> Do you have any examples of oftree resources for the root node?
> 
> Do you have any example of the root node used as device?

I am asking about an example of this particular usage in the root node
in device tree sources or bindings. You are asking about handling of the
device tree root node in the barebox device/driver model.

I don't see how that addresses my question.

>> I'd rather not litter core code with an if-clause that evaluates to
>> true only once,
> 
> How many ifs are added in this patch and how many ifs will by added by
> your suggestion? 

Mine adds none.

>> to support your (IMHO wrong)  use of a helper.
> 
> Interesting change of conversation. Please stay technical.

My technical opinion is that the helper is wrongly used.

>> of_device_make_bus_id is taken from Linux and does per comment:
>>
>> This routine will first try using the translated bus address to
>> derive a unique name. If it cannot, then it will prepend names from
>> parent nodes until a unique name can be derived.
>>
>> IMO, it should stay that way.
> 
> Ok, i'll send a patch to rename of_device_make_bus_id to of_device_make_id.
> In this case it will reflect new reality and keep the code readable.
> 
> If you have arguments in following topics:
> - it will significantly affect performance
> - it will affect size of executable
> - it will affect maintainability
> 
> Please use them

Shouldn't you be the one who argues in favor of his code?

It's ultimately Sascha's choice what to merge. To me this is
poor code, check my previous arguments.

Cheers,
Ahmad

> 
> Regards,
> Oleksij
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2020-08-12 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12  8:55 Oleksij Rempel
2020-08-12  9:42 ` Sascha Hauer
2020-08-12 12:40 ` Ahmad Fatoum
2020-08-12 13:08   ` Ahmad Fatoum
2020-08-12 15:13   ` Oleksij Rempel
2020-08-12 15:37     ` Ahmad Fatoum
2020-08-12 16:11       ` Oleksij Rempel
2020-08-12 18:15         ` Ahmad Fatoum [this message]
2020-08-12 18:24         ` Lucas Stach
2020-08-13  4:45           ` Oleksij Rempel
2020-08-17  4:45 ` Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8face7c6-f022-797d-af37-b2b66e6eb255@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=o.rempel@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox