mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Michael Graichen <michael.graichen@hotmail.com>
To: "johannes@gnu-linux.rocks" <johannes@gnu-linux.rocks>,
	"a.fatoum@pengutronix.de" <a.fatoum@pengutronix.de>,
	"l.stach@pengutronix.de" <l.stach@pengutronix.de>,
	"m.tretter@pengutronix.de" <m.tretter@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: [PATCH] add zynq-7000 i2c support
Date: Mon, 19 May 2025 07:13:11 +0000	[thread overview]
Message-ID: <VI1PR02MB44299AB6784FA5F3340F6CF9AB9CA@VI1PR02MB4429.eurprd02.prod.outlook.com> (raw)

This adds support to use the i2c bus on zynq-7000

Signed-off-by: Michael Graichen <michael.graichen@hotmail.com>
---
 drivers/i2c/busses/Kconfig       | 4 ++--
 drivers/i2c/busses/i2c-cadence.c | 1 +
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index b7ad9e6ecf..16f039dfea 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -84,10 +84,10 @@ config I2C_RK3X
 config I2C_CADENCE
 	bool "Cadence I2C adapter"
 	depends on HAVE_CLK
-	depends on ARCH_ZYNQMP || COMPILE_TEST
+	depends on ARCH_ZYNQ || ARCH_ZYNQMP || COMPILE_TEST
 	help
 	  Say Y here to include support for the Cadence I2C host controller found
-	  in Zynq UltraScale+ MPSoCs.
+	  in Zynq-7000 or Zynq UltraScale+ MPSoCs.
 
 config I2C_EFI
 	bool "EFI I2C Master driver"
diff --git a/drivers/i2c/busses/i2c-cadence.c b/drivers/i2c/busses/i2c-cadence.c
index 8551cd05da..e8ad26c91e 100644
--- a/drivers/i2c/busses/i2c-cadence.c
+++ b/drivers/i2c/busses/i2c-cadence.c
@@ -441,6 +441,7 @@ static int cdns_i2c_probe(struct device *dev)
 }
 
 static const struct of_device_id cdns_i2c_match[] = {
+	{ .compatible = "cdns,i2c-r1p10" },
 	{ .compatible = "cdns,i2c-r1p14" },
 	{},
 };
-- 
2.43.0


             reply	other threads:[~2025-05-19  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19  7:13 Michael Graichen [this message]
2025-05-22 20:24 ` Sascha Hauer

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=VI1PR02MB44299AB6784FA5F3340F6CF9AB9CA@VI1PR02MB4429.eurprd02.prod.outlook.com \
    --to=michael.graichen@hotmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=johannes@gnu-linux.rocks \
    --cc=l.stach@pengutronix.de \
    --cc=m.tretter@pengutronix.de \
    /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