On 08/09/2017 01:05 PM, Kieran Bingham wrote:
> On 09/08/17 11:58, Javier Martinez Canillas wrote:
>> Hi Kieran,
>>
>> On 08/09/2017 12:29 PM, Kieran Bingham wrote:
>>> Hi Javier,
>>>
>>> Thankyou for the patch
>>
>> You are welcome.
>>
>>> On 09/08/17 10:37, Javier Martinez Canillas wrote:
On 09/08/17 11:58, Javier Martinez Canillas wrote:
> Hi Kieran,
>
> On 08/09/2017 12:29 PM, Kieran Bingham wrote:
>> Hi Javier,
>>
>> Thankyou for the patch
>
> You are welcome.
>
>> On 09/08/17 10:37, Javier Martinez Canillas wrote:
>>> The I2C core always reports a MODALIAS of the form i2c: e
Hi Kieran,
On 08/09/2017 12:29 PM, Kieran Bingham wrote:
> Hi Javier,
>
> Thankyou for the patch
>
You are welcome.
> On 09/08/17 10:37, Javier Martinez Canillas wrote:
>> The I2C core always reports a MODALIAS of the form i2c: even if the
>> device was registered via OF, and the driver is onl
Hi Javier,
Thankyou for the patch
On 09/08/17 10:37, Javier Martinez Canillas wrote:
> The I2C core always reports a MODALIAS of the form i2c: even if the
> device was registered via OF, and the driver is only exporting the OF ID
> table entries as module aliases.
>
> So if the driver is built a
The I2C core always reports a MODALIAS of the form i2c: even if the
device was registered via OF, and the driver is only exporting the OF ID
table entries as module aliases.
So if the driver is built as module, autoload won't work since udev/kmod
won't be able to match the registered OF device wit
