From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: hunter.yu@hj-micro.com, rafael@kernel.org, lenb@kernel.org,
andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, jsd@semihalf.com,
andi.shyti@kernel.org
Cc: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 2/2] i2c: designware: Add a new ACPI HID for HJMC01 I2C controller
Date: Thu, 19 Sep 2024 13:26:00 +0300 [thread overview]
Message-ID: <81af4ed3-dbbf-482f-9e24-5fc0d1edac6f@linux.intel.com> (raw)
In-Reply-To: <20240919062943.1551197-3-hunter.yu@hj-micro.com>
On 9/19/24 9:29 AM, hunter.yu@hj-micro.com wrote:
> From: "hunter.yu" <hunter.yu@hj-micro.com>
>
> Define a new ACPI HID for HJMC01
>
> Signed-off-by: hunter.yu <hunter.yu@hj-micro.com>
> ---
> drivers/i2c/busses/i2c-designware-platdrv.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
> index df3dc1e8093e..06dcefa3b103 100644
> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
> @@ -58,6 +58,7 @@ static const struct acpi_device_id dw_i2c_acpi_match[] = {
> { "HISI02A2", 0 },
> { "HISI02A3", 0 },
> { "HYGO0010", ACCESS_INTR_MASK },
> + { "HJMC3001", 0 },
> { }
> };
> MODULE_DEVICE_TABLE(acpi, dw_i2c_acpi_match);
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2024-09-19 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240919062943.1551197-1-hunter.yu@hj-micro.com>
2024-09-19 6:29 ` [PATCH 1/2] ACPI: APD: Add clock frequency for HJMC01 I2C controller hunter.yu
2024-09-19 15:06 ` Andy Shevchenko
2024-09-19 6:29 ` [PATCH 2/2] i2c: designware: Add a new ACPI HID " hunter.yu
2024-09-19 10:26 ` Jarkko Nikula [this message]
2024-09-19 15:07 ` Andy Shevchenko
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=81af4ed3-dbbf-482f-9e24-5fc0d1edac6f@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hunter.yu@hj-micro.com \
--cc=jsd@semihalf.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
/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