[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfYhMbHK7pMTuVDZ3uc5ZjytA7uC+3fr7u3nWUEosGZHw@mail.gmail.com>
Date: Fri, 7 Jun 2024 22:45:49 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Yasin Lee <yasin.lee.x@...look.com>
Cc: jic23@...nel.org, lars@...afoo.de, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, nuno.a@...log.com, swboyd@...omium.org,
u.kleine-koenig@...gutronix.de, yasin.lee.x@...il.com
Subject: Re: [PATCH v4 2/2] iio:proximity:hx9023s: Add TYHX HX9023S sensor driver
On Fri, Jun 7, 2024 at 10:40 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Fri, Jun 7, 2024 at 2:42 PM Yasin Lee <yasin.lee.x@...look.com> wrote:
...
.
> > +static const struct acpi_device_id hx9023s_acpi_match[] = {
> > + { "TYHX9023" },
> > + {}
> > +};
>
> Btw, do you have a reference to any device on the market that has this ID?
Aaaargh!
Jonathan, we have to have a big rule from now on on ACPI IDs, if
anybody introduces an ID in the driver, they must provide the device
model that is (are going to) use it and excerpt from the ACPI ID
registry to prove the vendor ID is real.
This is the heck fake ID!
NAK.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists