On 05/03/2016 12:43 PM, Gregor Boirie wrote: > Just to let you know that I'm facing a problem to support multiple > instances of > the ms5607 barometer onto the same board. > > Referencing (i2c) id->name from indio_dev->name is not suitable in this > case as > libiio and kernel iio tools such as generic_buffer all rely upon a > unique iio > name to distinguish devices. Here is why. > > generic_buffer expects a device name passed as argument to -n option > to get a reference to a device. In this case, it is not possible to > distinguish between devices holding the same name. > > When libiio based apps use iio_context_find_device() to get a reference > to a device (by name), names should be unique across devices as above. > When retrieving a device reference by index through > iio_context_get_device() > it is not possible to uniquely identify devices in a consistent way either. > Indeed, as indices assignment is automatically done at boot time, it is > highly > dependent on module / driver loading ordering, devices / daughter board > presence, > etc... > As a result, apps cannot assume indices are persistent across reboots. > > Hence, using dev_name(&client->dev) to name a device is most certainly > an acceptable > option despites inconsistencies it introduces with i2c name space. > > I re-use device tree names to do the job. However, it will not work if > not compiled > in (and needs patching). What would be a robust and generic naming > solution then ? > Identifying iio devices by numeric ID seems to be the correct solution. These are also the minor device numbers, right? Perhaps you can create devices nodes with pretty names through udev rules. In particular OF_FULLNAME seems to be available as a property. Example: # ssh -t local2222 udevadm info /sys/bus/iio/devices/iio:device0 DEVNAME=/dev/iio:device0 DEVTYPE=iio_device MAJOR=250 MINOR=0 OF_COMPATIBLE_0=inv,mpu6500 OF_COMPATIBLE_N=1 OF_FULLNAME=/spi/mpu6500@0 OF_NAME=mpu6500 SUBSYSTEM=iio -- Regards Leonard -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
