[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200826095617.GH1891694@smile.fi.intel.com>
Date: Wed, 26 Aug 2020 12:56:17 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: Wolfram Sang <wsa@...nel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-i2c@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] i2c: consider devices with of_match_table during i2c
device probing
On Wed, Aug 26, 2020 at 12:53:56PM +0300, Andy Shevchenko wrote:
> On Wed, Aug 26, 2020 at 02:25:44PM +0900, Sergey Senozhatsky wrote:
> > On (20/08/26 07:08), Wolfram Sang wrote:
...
> You probably meant simply:
>
> if (!i2c_device_match(dev, dev->driver)) {
>
> > status = -ENODEV;
> > goto put_sync_adapter;
> > }
>
> On the first glance it will work the same way but slightly longer in case of ID
> table matching.
>
> Send a patch!
But then the question is why we have this code in the ->probe() at all?
->match() is run before probe by bus core, no?
Wolfram?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists