1. 03 8月, 2015 7 次提交
  2. 02 8月, 2015 2 次提交
    • J
      iio: Export OF module alias information in missing drivers · 119c4fce
      Javier Martinez Canillas 提交于
      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: NJavier Martinez Canillas <javier@osg.samsung.com>
      Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      119c4fce
    • J
      iio: Export I2C module alias information in missing drivers · 58e446fc
      Javier Martinez Canillas 提交于
      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 the driver needs to export the I2C table and this
      be built into the module or udev won't have the necessary information
      to auto load the correct module when the device is added.
      Signed-off-by: NJavier Martinez Canillas <javier@osg.samsung.com>
      Signed-off-by: NJonathan Cameron <jic23@kernel.org>
      58e446fc
  3. 24 7月, 2015 7 次提交
  4. 21 7月, 2015 12 次提交
  5. 19 7月, 2015 11 次提交
  6. 17 7月, 2015 1 次提交