From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Hanjun Guo <guohanjun@huawei.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
linuxarm@huawei.com, Sheng Feng <fengsheng5@huawei.com>
Subject: Re: [PATCH v2 2/2] i2c: designware: Add ACPI HID for Hisilicon Hip08-Lite I2C controller
Date: Mon, 3 Feb 2020 11:01:02 +0200 [thread overview]
Message-ID: <4e1889bd-39e0-9b87-9f47-e460a782ee09@linux.intel.com> (raw)
In-Reply-To: <1580693767-5185-2-git-send-email-guohanjun@huawei.com>
On 2/3/20 3:36 AM, Hanjun Guo wrote:
> Add ACPI HID HISI02A3 for Hisilicon Hip08 Lite, which has different
> clock frequency from Hip08 for I2C controller.
>
> Tested-by: Sheng Feng <fengsheng5@huawei.com>
> Signed-off-by: Hanjun Guo <guohanjun@huawei.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 16dd338..3b7d58c 100644
> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
> @@ -130,6 +130,7 @@ static int dw_i2c_acpi_configure(struct platform_device *pdev)
> { "APMC0D0F", 0 },
> { "HISI02A1", 0 },
> { "HISI02A2", 0 },
> + { "HISI02A3", 0 },
> { }
> };
> MODULE_DEVICE_TABLE(acpi, dw_i2c_acpi_match);
> --
Acked-by: Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2020-02-03 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 1:36 [PATCH v2 1/2] ACPI / APD: Add clock frequency for Hisilicon Hip08-Lite I2C controller Hanjun Guo
2020-02-03 1:36 ` Hanjun Guo
2020-02-03 1:36 ` [PATCH v2 2/2] i2c: designware: Add ACPI HID " Hanjun Guo
2020-02-03 1:36 ` Hanjun Guo
2020-02-03 9:01 ` Jarkko Nikula [this message]
2020-02-03 9:23 ` Andy Shevchenko
2020-02-03 9:00 ` [PATCH v2 1/2] ACPI / APD: Add clock frequency " Jarkko Nikula
2020-02-03 11:04 ` Rafael J. Wysocki
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=4e1889bd-39e0-9b87-9f47-e460a782ee09@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fengsheng5@huawei.com \
--cc=guohanjun@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxarm@huawei.com \
--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 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.