Segher Boessenkool wrote: > For some buses, there is a "slot-names" property; some (non-core) > bindings seem to define a "location" property. > > For "random" human-readable labelling, i.e. not corresponding to > physical markings on the hardware, I recommend you look for a > matching entry in /aliases.
Aliases could work, but are awkward to use for the purposes I'm thinking of (giving the OS a name to present to the user in association with a device). They're more suited to interactive OF use where the device tree is being directly referenced by the user. Plus, you're then restricted to valid property names for the alias, whereas with a label property you could use any string, including spaces and such. > It won't ever be _exactly_ what you > want though, the Linux device namespace is separate from the > device tree. That's Linux's choice. Nothing stops it from showing device tree labels to the user in various situations -- what got me thinking about this was that apparently ALSA lets the driver pass an arbitrary string to identify the device, and it seemed that such a device-tree-derived label would be the most useful to the user. To use aliases for that, it'd have to get the full path to the audio node, compare it to each alias, and hope it finds one and only one, and that that alias was intended to be a user label and not something else. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
