public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: hunter.yu@hj-micro.com
To: rafael@kernel.org, lenb@kernel.org,
	jarkko.nikula@linux.intel.com, 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,
	hunter.yu@hj-micro.com
Subject: [PATCH 1/2] ACPI: APD: Add clock frequency for HJMC01 I2C controller
Date: Thu, 19 Sep 2024 14:29:42 +0800	[thread overview]
Message-ID: <20240919062943.1551197-2-hunter.yu@hj-micro.com> (raw)
In-Reply-To: <20240919062943.1551197-1-hunter.yu@hj-micro.com>

From: "hunter.yu" <hunter.yu@hj-micro.com>

I2C clock frequency for HJMC01 is 200M, define a new ACPI
HID for it.

Signed-off-by: hunter.yu <hunter.yu@hj-micro.com>
---
 drivers/acpi/acpi_apd.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/acpi/acpi_apd.c b/drivers/acpi/acpi_apd.c
index 800f97868448..bc271d1cb31b 100644
--- a/drivers/acpi/acpi_apd.c
+++ b/drivers/acpi/acpi_apd.c
@@ -181,6 +181,11 @@ static const struct apd_device_desc hip08_spi_desc = {
 	.setup = acpi_apd_setup,
 	.fixed_clk_rate = 250000000,
 };
+
+static const struct apd_device_desc hjmc_i2c_desc = {
+	.setup = acpi_apd_setup,
+	.fixed_clk_rate = 200000000,
+};
 #endif /* CONFIG_ARM64 */
 
 #endif
@@ -252,6 +257,7 @@ static const struct acpi_device_id acpi_apd_device_ids[] = {
 	{ "HISI02A3", APD_ADDR(hip08_lite_i2c_desc) },
 	{ "HISI0173", APD_ADDR(hip08_spi_desc) },
 	{ "NXP0001", APD_ADDR(nxp_i2c_desc) },
+	{ "HJMC3001", APD_ADDR(hjmc_i2c_desc) },
 #endif
 	{ }
 };
-- 
2.27.0


       reply	other threads:[~2024-09-19  8:56 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 ` hunter.yu [this message]
2024-09-19 15:06   ` [PATCH 1/2] ACPI: APD: Add clock frequency for HJMC01 I2C controller 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
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=20240919062943.1551197-2-hunter.yu@hj-micro.com \
    --to=hunter.yu@hj-micro.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.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