[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABxcv=kSNZMKkL7Ge2WkvDqH1V-CVSJN-agPcMmU4qvdy9HRiQ@mail.gmail.com>
Date: Mon, 15 Jan 2018 13:31:12 +0100
From: Javier Martinez Canillas <javier@...hile0.org>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Dmitry Mastykin <mastichi@...il.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Jacopo Mondi <jacopo+renesas@...ndi.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
Rob Herring <robh@...nel.org>,
linux-iio <linux-iio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] iio: adc: max9611: fix module auto-loading
On Sun, Jan 14, 2018 at 11:51 AM, Jonathan Cameron <jic23@...nel.org> wrote:
> On Wed, 10 Jan 2018 12:01:07 +0100
> Javier Martinez Canillas <javier@...hile0.org> wrote:
>
>> Hello Jonathan,
>>
>> On Mon, Jan 1, 2018 at 10:53 AM, Jonathan Cameron <jic23@...nel.org> wrote:
>>
>> [snip]
>>
>> >
>> > I may well be missing some subtle detail of course having spent only a few
>> > minute looking at this!
>> >
>>
>> Your understanding is correct. This change has nothing to do with
>> module autoloading.
>>
>> The .probe_new callback is only used to avoid requiring an I2C device
>> ID table since the old .probe callback has a struct i2c_device_id as a
>> parameter and so requires a table even in OF (or ACPI) only drivers.
>
> OK, then let us revisit this patch once we have an answer on your one
> fixing the autoprobing more generally. Until we then we don't know
> whether we need to add the i2c table in or not whether this suffices.
>
That's correct. If the driver is for a device that's OF-only (e.g:
will never be used from a non-DT platform) then I don't think we
should add a I2C table.
Now, if Wolfram nacks my patch then we should add it as a workaround
to have auto-loading working.
> Jonathan
>
Best regards,
Javier
Powered by blists - more mailing lists