From: Segher Boessenkool <segher@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] use of aliases in device trees
Date: Sun, 4 Nov 2007 10:24:37 +0100 [thread overview]
Message-ID: <6eabf485a3aae685b1847bbb3d5a2dd0@kernel.crashing.org> (raw)
In-Reply-To: <DD2A9B2C-5D35-4F53-8542-3470C6FA5265@kernel.crashing.org>
> In some discussion on the u-boot dev list it became clear that having
> aliases in the device tree might be useful as a common way to deal
> with finding specific nodes that need fixing up by the firmware.
> One common solution would be having a top level aliases like the pmac
> tree's have:
>
> aliases {
> enet0 = "...";
> enet1 = "...";
> pci0 = "...";
> pci1 = "...";
> };
It's not just Apple that uses this; this is standard OF stuff.
> I wanted to see what people think of this idea and about trying to
> use common names for the aliases?
I'm obviously all for it, having suggested it myself a few times.
For common names, I think a good starting point would be to use
the generic names (as defined in the "generic names" recommended
practice; this should be the name of the nodes pointed to as well),
followed by a number; and/or a generic name without any suffix,
which points to the "main" device of that type.
This is a lot like your example, except that "enet" isn't a generic
name (that would be "network" I believe). It is perfectly fine to
have to or more aliases pointing to the same node though.
This won't solve all identification problems of course, it only gives
an ordering per class of devices, but in most cases this will be enough,
esp. when platform code uses this. We'll likely need a few extra names
for special cases, but let's use some restraint there, and esp. not
define something as a generic solution when it isn't.
Segher
prev parent reply other threads:[~2007-11-04 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 1:02 [U-Boot-Users] use of aliases in device trees Kumar Gala
2007-11-04 3:29 ` Grant Likely
2007-11-04 22:42 ` David Gibson
2007-11-04 23:32 ` Grant Likely
2007-11-04 9:24 ` Segher Boessenkool [this message]
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=6eabf485a3aae685b1847bbb3d5a2dd0@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=u-boot@lists.denx.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