[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/dTqynpTWn86wUy@smile.fi.intel.com>
Date: Thu, 23 Feb 2023 13:53:15 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Robin van der Gracht <robin@...tonic.nl>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
"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,
Miguel Ojeda <ojeda@...nel.org>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devicetree@...r.kernel.org
Subject: Re: [PATCH v1 2/3] auxdisplay: ht16k33: Make use of
device_get_match_data()
On Thu, Feb 23, 2023 at 10:55:15AM +0100, Geert Uytterhoeven wrote:
> On Wed, Feb 22, 2023 at 8:21 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Wed, Feb 22, 2023 at 07:46:25PM +0100, Krzysztof Kozlowski wrote:
...
> > I.o.w. the part after comma in the compatible strings of the I²C devices must
> > be unique globally to make that enumeration disambiguous.
>
> Which is not unique to this driver?
> I bet you can find other compatible values that become non-unique
> after stripping the manufacturer.
Yes, exactly my point.
So this all schema is error prone. Hence I would not rely on it at all.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists