* Device naming based on device tree @ 2013-01-21 10:25 Thomas De Schampheleire [not found] ` <CAAXf6LVDGC_VszCqz992SmMhM6r2w3_4zLL=NkCuzJ8ep7kiMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 2+ messages in thread From: Thomas De Schampheleire @ 2013-01-21 10:25 UTC (permalink / raw) To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ; +Cc: Ronny Meeus Hi, I'm trying to find a proper way for userspace to determine which devices to talk to. Say you have 4 SPI devices that are registered against spidev (the userspace SPI handling driver). The device tree obviously knows which device is which (e.g. a temperature sensor, a memory device, an actuator, ...) but userspace does not. In the case of SPI, it sees things like: /sys/class/spidev/spidev32766.1/ or worse /sys/devices/ffe000000.soc/ffe110000.spi/spi32766.1 but these are too specific. The same problem occurs for devices using i2c-dev, uio, mtd, ... For uio, it's possible to determine which device i (i.e. the userspace program needs to know that a) the device is an SPI devices which by checking the /sys/class/uio/uioX/name files. For mtd it is possible to do something similar by strategically choosing the mtd partition descriptions and creating device nodes or links based on that information. Basically, I'm looking for a way to give device tree nodes a name, so that I can easily access or create devices like /dev/tempsensor0, /dev/actuator, /dev/serialnum_memory, etc. Ideally such a mechanism is bus-agnostic: on one board the temperature sensor may be using SPI, on another I2C. I assume this is what udev is for, but I'm not sure if it fixes my problem. In order to name/rename devices with udev, there need to be rules, and these rules are part of userspace, I cannot dictate them from the device tree. In an embedded world, you may have three boards with the same userspace but with different hardware configurations and thus different device trees. Are there existing solutions to this problem? If not, what do you think about such a device-tree-dictated mechanism? Thanks, Thomas ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <CAAXf6LVDGC_VszCqz992SmMhM6r2w3_4zLL=NkCuzJ8ep7kiMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: Device naming based on device tree [not found] ` <CAAXf6LVDGC_VszCqz992SmMhM6r2w3_4zLL=NkCuzJ8ep7kiMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2013-04-13 12:48 ` Grant Likely 0 siblings, 0 replies; 2+ messages in thread From: Grant Likely @ 2013-04-13 12:48 UTC (permalink / raw) To: Thomas De Schampheleire, devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ Cc: Ronny Meeus On Mon, 21 Jan 2013 11:25:26 +0100, Thomas De Schampheleire <patrickdepinguin+devicetree-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > Hi, > > I'm trying to find a proper way for userspace to determine which > devices to talk to. Say you have 4 SPI devices that are registered > against spidev (the userspace SPI handling driver). The device tree > obviously knows which device is which (e.g. a temperature sensor, a > memory device, an actuator, ...) but userspace does not. In the case > of SPI, it sees things like: > /sys/class/spidev/spidev32766.1/ > or worse > /sys/devices/ffe000000.soc/ffe110000.spi/spi32766.1 > but these are too specific. > > The same problem occurs for devices using i2c-dev, uio, mtd, ... > > For uio, it's possible to determine which device i (i.e. the userspace > program needs to know that a) the device is an SPI devices which by > checking the /sys/class/uio/uioX/name files. > For mtd it is possible to do something similar by strategically > choosing the mtd partition descriptions and creating device nodes or > links based on that information. > > Basically, I'm looking for a way to give device tree nodes a name, so > that I can easily access or create devices like /dev/tempsensor0, > /dev/actuator, /dev/serialnum_memory, etc. Ideally such a mechanism is > bus-agnostic: on one board the temperature sensor may be using SPI, on > another I2C. > > I assume this is what udev is for, but I'm not sure if it fixes my > problem. In order to name/rename devices with udev, there need to be > rules, and these rules are part of userspace, I cannot dictate them > from the device tree. In an embedded world, you may have three boards > with the same userspace but with different hardware configurations and > thus different device trees. Yes, every time a new device is added to /sys/devices, a uevent will be issued that lets udev know that a new device is ready to be handled. The data associated with the uevent is exported via the 'uevent' attribute in the new device. The uevent attribute should have enough information to identify which dt node is associated with the device. Check the OF_FULLNAME value in uevent, and also the OF_ALIAS_* values. g. ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-04-13 12:48 UTC | newest] Thread overview: 2+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-01-21 10:25 Device naming based on device tree Thomas De Schampheleire [not found] ` <CAAXf6LVDGC_VszCqz992SmMhM6r2w3_4zLL=NkCuzJ8ep7kiMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2013-04-13 12:48 ` Grant Likely
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).