From: Kai-Heng Feng <kai.heng.feng@canonical.com>
To: jic23@kernel.org, lars@metafoo.de
Cc: andy.shevchenko@gmail.com,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Matt Ranostay <matt.ranostay@konsulko.com>,
Your Name <you@example.com>,
Chris Lesiak <chris.lesiak@licor.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3] iio: humidity: hdc100x: Add ACPI HID table
Date: Fri, 28 Jan 2022 12:20:51 +0800 [thread overview]
Message-ID: <20220128042054.2062060-1-kai.heng.feng@canonical.com> (raw)
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 add an ACPI match table for that accordingly.
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
next reply other threads:[~2022-01-28 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 4:20 Kai-Heng Feng [this message]
2022-01-28 13:53 ` [PATCH v3] iio: humidity: hdc100x: Add ACPI HID table Andy Shevchenko
2022-01-30 13:45 ` Jonathan Cameron
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=20220128042054.2062060-1-kai.heng.feng@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=andy.shevchenko@gmail.com \
--cc=chris.lesiak@licor.com \
--cc=jic23@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.