[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/TJs+Arban0ats8@smile.fi.intel.com>
Date: Tue, 21 Feb 2023 15:40:03 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>,
Raul E Rangel <rrangel@...omium.org>,
Wolfram Sang <wsa@...nel.org>, linux-kernel@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-usb@...r.kernel.org
Cc: Robin van der Gracht <robin@...tonic.nl>,
Miguel Ojeda <ojeda@...nel.org>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v1 2/3] auxdisplay: ht16k33: Make use of
device_get_match_data()
On Tue, Feb 21, 2023 at 03:33:06PM +0200, Andy Shevchenko wrote:
> Switching to use device_get_match_data() helps getting of
> i2c_of_match_device() API.
...
> - id = i2c_of_match_device(dev->driver->of_match_table, client);
> - if (id)
> - priv->type = (uintptr_t)id->data;
> + priv->type = (uintptr_t)device_get_match_data(dev);
Looking closer the I²C ID table should provide DISP_MATRIX to keep default and
this needs to be not dropped.
So, the question is what to do with unknown type then, return -EINVAL from
probe()?
P.S. I would like to collect other comments anyway, so I will send a v2 later.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists