Re: [PATCHv2] i2c: omap: Disable default probing of i2c devices for omap i2c.

[Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>]

[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]

On Wed, Apr 09, 2014 at 04:06:48PM +0530, Sourav Poddar wrote:
> I2c core supports defualt probing functionality for devices not registered through
> dt/board files. If there are any client driver registered, i2c core will try to
> check if there is any device present corresponding to the address supplied by
> the client driver. If the device is actually present and not registered, core
> will register it, else the device default probe will fail and we get a omap i2c controller
> specific timeout messages.
> For example, Using multi_v7_config on omap5-uevm, CONFIG_SENSORS_LM90 and CONFIG_ICS932S401
> is the driver which is enabled and gets registered. I2c core tries to find a valid
> corresponding device on each of the address supplied by registered driver,
> but could not find anyone. Hence, keep dumping the controller timeout speciic message.

This is exactly why I2C_CLASS_DEPRECATED was implemented. So, users
which are using classes can migrate away. But this needs time. Given
that I2C_CLASS_DEPRECATED is new in 3.15, I'd think setting classes to 0
(thus totally disabling them) should not be before 3.17. You don't need
to resend, I'll do it for all drivers I added this new class to when I
feel it is safe to do.

Thanks,

   Wolfram


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]