On Tue, Sep 01, 2015 at 12:30:22AM +0200, Javier Martinez Canillas wrote:
> Hello Wolfram,
>
> On 08/31/2015 10:31 PM, Wolfram Sang wrote:
> >
> >>> The dummy driver is always loaded when the i2c core inits.
> >>>
> >>
> >> Ok, I wondered if that was the case but I
> >> was not sure so I posted i
Hello Wolfram,
On 08/31/2015 10:31 PM, Wolfram Sang wrote:
>
>>> The dummy driver is always loaded when the i2c core inits.
>>>
>>
>> Ok, I wondered if that was the case but I
>> was not sure so I posted it just in case.
>
> Check the source code, this part is pretty obvious...
>
Yes, sorry for
> > The dummy driver is always loaded when the i2c core inits.
> >
>
> Ok, I wondered if that was the case but I
> was not sure so I posted it just in case.
Check the source code, this part is pretty obvious...
signature.asc
Description: Digital signature
Hello Wolfram,
On 08/26/2015 06:55 PM, Wolfram Sang wrote:
> On Tue, Aug 25, 2015 at 08:31:11AM +0200, Javier Martinez Canillas wrote:
>> The I2C core always reports the MODALIAS uevent as "i2c:"
>> regardless of the mechanism that was used to register the device
>> (i.e: OF or board code) and the
On Tue, Aug 25, 2015 at 08:31:11AM +0200, Javier Martinez Canillas wrote:
> The I2C core always reports the MODALIAS uevent as "i2c:"
> 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 (
The I2C core always reports the MODALIAS uevent as "i2c:"
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
6 matches
Mail list logo
