Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Matt Ranostay <matt.ranostay@konsulko.com>,
	Your Name <you@example.com>,
	Chris Lesiak <chris.lesiak@licor.com>,
	linux-iio <linux-iio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] iio: humidity: hdc100x: Add ACPI HID table
Date: Sun, 30 Jan 2022 13:45:57 +0000	[thread overview]
Message-ID: <20220130134557.5e211d45@jic23-huawei> (raw)
In-Reply-To: <CAHp75VfC873djcc4Z2+HhzR8z3Uaute3g0Fgr1dvOs_v=gD3Lw@mail.gmail.com>

On Fri, 28 Jan 2022 15:53:11 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> wrote:

> On Fri, Jan 28, 2022 at 6:21 AM Kai-Heng Feng
> <kai.heng.feng@canonical.com> wrote:
> >
> > x86 boards may use ACPI HID "TXNW1010" for the hdc100x device.
> >
> > TI told us "The ACPI ID for TI is: https://uefi.org/node/1028 (TXNW),
> > therefore it would most likely be appropriate to use TXNW1010."  
> 
> So, they basically agree on using it, did I get it right?
> 
> > So add an ACPI match table for that accordingly.  
> 
> Assuming TI is aware of the ID,
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
With that assumption I'm applying this to the togreg branch of iio.git which
will be pushed out as testing for 0-day to take a look at.

Still time to pull it out before I push this out as non rebasing if
we have misunderstood the above.

Thanks,

Jonathan

> 
> > Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> > ---
> > v3:
> >  - Add info from vendor
> >  - Drop redundant line and comma.
> >  - Wording change.
> >
> > v2:
> >  - Change the ID to follow ACPI Spec
> >  - Add __maybe_unused to avoid compiler warning
> >
> >  drivers/iio/humidity/hdc100x.c | 7 +++++++
> >  1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/iio/humidity/hdc100x.c b/drivers/iio/humidity/hdc100x.c
> > index 9e0fce917ce4c..47f8e8ef56d68 100644
> > --- a/drivers/iio/humidity/hdc100x.c
> > +++ b/drivers/iio/humidity/hdc100x.c
> > @@ -417,10 +417,17 @@ static const struct of_device_id hdc100x_dt_ids[] = {
> >  };
> >  MODULE_DEVICE_TABLE(of, hdc100x_dt_ids);
> >
> > +static const struct acpi_device_id hdc100x_acpi_match[] = {
> > +       { "TXNW1010" },
> > +       { }
> > +};
> > +MODULE_DEVICE_TABLE(acpi, hdc100x_acpi_match);
> > +
> >  static struct i2c_driver hdc100x_driver = {
> >         .driver = {
> >                 .name   = "hdc100x",
> >                 .of_match_table = hdc100x_dt_ids,
> > +               .acpi_match_table = hdc100x_acpi_match,
> >         },
> >         .probe = hdc100x_probe,
> >         .id_table = hdc100x_id,
> > --
> > 2.33.1
> >  
> 
> 


      reply	other threads:[~2022-01-30 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  4:20 [PATCH v3] iio: humidity: hdc100x: Add ACPI HID table Kai-Heng Feng
2022-01-28 13:53 ` Andy Shevchenko
2022-01-30 13:45   ` Jonathan Cameron [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220130134557.5e211d45@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=chris.lesiak@licor.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.ranostay@konsulko.com \
    --cc=you@example.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox