summaryrefslogtreecommitdiffstats
path: root/scripts/ver_linux
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier@osg.samsung.com>2015-08-25 08:31:16 +0200
committerJacek Anaszewski <j.anaszewski@samsung.com>2015-08-28 14:06:30 +0200
commit4d59ed85451befda203d72462f1b7ead0fde3267 (patch)
treec58d388f7bc1ca3461513781d85a14fe782e1370 /scripts/ver_linux
parentleds:lp55xx: use the private data instead of updating I2C device platform data (diff)
downloadlinux-4d59ed85451befda203d72462f1b7ead0fde3267.tar.xz
linux-4d59ed85451befda203d72462f1b7ead0fde3267.zip
leds: Export OF module alias information in missing drivers
The I2C core always reports the MODALIAS uevent as "i2c:<modalias>" regardless of the mechanism that was used to register the device (i.e: OF or board code) and the table that is used later to match the driver with the device (i.e: I2C id table or OF match table). So drivers needs to export the I2C id table and this be built into the module or udev won't have the necessary information to autoload the needed driver module when the device is added. But this means that OF-only drivers needs to have both OF and I2C id tables that have to be kept in sync and also the dev node compatible manufacturer prefix is stripped when reporting the MODALIAS. Which can lead to issues if two vendors use the same I2C device name for example. To avoid the above, the I2C core behavior may be changed in the future to not require an SPI device table for OF-only drivers and report the OF module alias. So, it's better to also export the OF table even when is unused now to prevent breaking module loading when the core changes. Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
Diffstat (limited to 'scripts/ver_linux')
0 files changed, 0 insertions, 0 deletions