mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 04:34:11 +08:00
119c4fce68
The I2C core always reports the MODALIAS uevent as "i2c:<client name" regardless if the driver was matched using the I2C id_table or the of_match_table. So technically there's no need for a driver to export the OF table since currently it's not used. In fact, the I2C device ID table is mandatory for I2C drivers since a i2c_device_id is passed to the driver's probe function even if the I2C core used the OF table to match the driver. And since the I2C core uses different tables, OF-only drivers needs to have duplicated data that has to be kept in sync and also the dev node compatible manufacturer prefix is stripped when reporting the MODALIAS. To avoid the above, the I2C core behavior may be changed in the future to not require an I2C device table for OF-only drivers and report the OF module alias. So, it's better to also export the OF table to prevent breaking module autoloading if that happens. Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by: Jonathan Cameron <jic23@kernel.org> |
||
|---|---|---|
| .. | ||
| acpi-als.c | ||
| adjd_s311.c | ||
| al3320a.c | ||
| apds9300.c | ||
| bh1750.c | ||
| cm3232.c | ||
| cm3323.c | ||
| cm32181.c | ||
| cm36651.c | ||
| gp2ap020a00f.c | ||
| hid-sensor-als.c | ||
| hid-sensor-prox.c | ||
| isl29125.c | ||
| jsa1212.c | ||
| Kconfig | ||
| lm3533-als.c | ||
| ltr501.c | ||
| Makefile | ||
| opt3001.c | ||
| pa12203001.c | ||
| rpr0521.c | ||
| stk3310.c | ||
| tcs3414.c | ||
| tcs3472.c | ||
| tsl2563.c | ||
| tsl4531.c | ||
| vcnl4000.c | ||