From: Wolfram Sang
The current implementation only works if the da9xxx devices are added
before their drivers are registered. Only then it can apply the fixes to
both devices. Otherwise, the driver for the first device gets probed
before the fix for the second
On Thu, Sep 01, 2016 at 09:00:07PM +0200, Geert Uytterhoeven wrote:
> On Thu, Sep 1, 2016 at 4:27 PM, Wolfram Sang wrote:
> > On Thu, Sep 01, 2016 at 04:22:37PM +0200, Simon Horman wrote:
> >> On Tue, Aug 30, 2016 at 05:15:58PM +0200, Geert Uytterhoeven wrote:
> >> > On Tue,
On Thu, Sep 1, 2016 at 4:27 PM, Wolfram Sang wrote:
> On Thu, Sep 01, 2016 at 04:22:37PM +0200, Simon Horman wrote:
>> On Tue, Aug 30, 2016 at 05:15:58PM +0200, Geert Uytterhoeven wrote:
>> > On Tue, Aug 30, 2016 at 4:54 PM, Wolfram Sang
>> >
On Tue, Aug 30, 2016 at 05:15:58PM +0200, Geert Uytterhoeven wrote:
> Hi Wolfram,
>
> On Tue, Aug 30, 2016 at 4:54 PM, Wolfram Sang
> wrote:
> > The current implementation only works if the da9xxx devices are added
> > before their drivers are registered. Only
On Thu, Sep 01, 2016 at 04:22:37PM +0200, Simon Horman wrote:
> On Tue, Aug 30, 2016 at 05:15:58PM +0200, Geert Uytterhoeven wrote:
> > Hi Wolfram,
> >
> > On Tue, Aug 30, 2016 at 4:54 PM, Wolfram Sang
> > wrote:
> > > The current implementation only works if
Hi Wolfram,
On Tue, Aug 30, 2016 at 4:54 PM, Wolfram Sang
wrote:
> The current implementation only works if the da9xxx devices are added
> before their drivers are registered. Only then it can apply the fixes to
> both devices. Otherwise, the driver for the
The current implementation only works if the da9xxx devices are added
before their drivers are registered. Only then it can apply the fixes to
both devices. Otherwise, the driver for the first device gets probed
before the fix for the second device can be applied. This is what
fails when using the