On Mon, Mar 05, 2018 at 08:09:29PM +, Sasha Levin wrote:
> On Mon, Mar 05, 2018 at 10:42:03AM +, Mark Brown wrote:
> >As the commit message itself says this is not fixing anything, it's
> >defence against future changes.
> I was under the impression that this refers to future HW changes
On Mon, Mar 05, 2018 at 08:09:29PM +, Sasha Levin wrote:
> On Mon, Mar 05, 2018 at 10:42:03AM +, Mark Brown wrote:
> >As the commit message itself says this is not fixing anything, it's
> >defence against future changes.
> I was under the impression that this refers to future HW changes
On Mon, Mar 05, 2018 at 10:42:03AM +, Mark Brown wrote:
>On Sat, Mar 03, 2018 at 10:29:00PM +, Sasha Levin wrote:
>> From: Javier Martinez Canillas
>>
>> [ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
>>
>> The driver doesn't have a struct
On Mon, Mar 05, 2018 at 10:42:03AM +, Mark Brown wrote:
>On Sat, Mar 03, 2018 at 10:29:00PM +, Sasha Levin wrote:
>> From: Javier Martinez Canillas
>>
>> [ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
>>
>> The driver doesn't have a struct of_device_id table but supported
On Mon, Mar 5, 2018 at 11:42 AM, Mark Brown wrote:
> On Sat, Mar 03, 2018 at 10:29:00PM +, Sasha Levin wrote:
>> From: Javier Martinez Canillas
>>
>> [ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
>>
>> The driver doesn't have a
On Mon, Mar 5, 2018 at 11:42 AM, Mark Brown wrote:
> On Sat, Mar 03, 2018 at 10:29:00PM +, Sasha Levin wrote:
>> From: Javier Martinez Canillas
>>
>> [ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
>>
>> The driver doesn't have a struct of_device_id table but supported devices
On Sat, Mar 03, 2018 at 10:29:00PM +, Sasha Levin wrote:
> From: Javier Martinez Canillas
>
> [ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
>
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees.
On Sat, Mar 03, 2018 at 10:29:00PM +, Sasha Levin wrote:
> From: Javier Martinez Canillas
>
> [ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
>
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the
From: Javier Martinez Canillas
[ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF
From: Javier Martinez Canillas
[ Upstream commit 9ba2da5f5d18daaa365ab5426b05e16f1d114786 ]
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy
10 matches
Mail list logo