From: Frank Wunderlich <linux@fw-web.de>
To: Michal Simek <michal.simek@amd.com>, Heiko Schocher <hs@denx.de>,
Tom Rini <trini@konsulko.com>
Cc: Frank Wunderlich <frank-w@public-files.de>,
Maksim Kiselev <bigunclemax@gmail.com>,
u-boot@lists.denx.de
Subject: [PATCH v1] i2c: muxes: pca954x: add pca9545 support
Date: Fri, 6 Jun 2025 11:50:54 +0200 [thread overview]
Message-ID: <20250606095056.22082-1-linux@fw-web.de> (raw)
From: Frank Wunderlich <frank-w@public-files.de>
Add support for 4 channel pca9545 found on Bananapi R4.
Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
---
drivers/i2c/muxes/pca954x.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/drivers/i2c/muxes/pca954x.c b/drivers/i2c/muxes/pca954x.c
index 9dd269727036..d13947a0d9cc 100644
--- a/drivers/i2c/muxes/pca954x.c
+++ b/drivers/i2c/muxes/pca954x.c
@@ -22,6 +22,7 @@ enum pca_type {
MAX7369,
PCA9543,
PCA9544,
+ PCA9545,
PCA9546,
PCA9547,
PCA9548,
@@ -79,6 +80,10 @@ static const struct chip_desc chips[] = {
.muxtype = pca954x_ismux,
.width = 4,
},
+ [PCA9545] = {
+ .muxtype = pca954x_isswi,
+ .width = 4,
+ },
[PCA9546] = {
.muxtype = pca954x_isswi,
.width = 4,
@@ -141,6 +146,7 @@ static const struct udevice_id pca954x_ids[] = {
{ .compatible = "maxim,max7369", .data = MAX7369 },
{ .compatible = "nxp,pca9543", .data = PCA9543 },
{ .compatible = "nxp,pca9544", .data = PCA9544 },
+ { .compatible = "nxp,pca9545", .data = PCA9545 },
{ .compatible = "nxp,pca9546", .data = PCA9546 },
{ .compatible = "nxp,pca9547", .data = PCA9547 },
{ .compatible = "nxp,pca9548", .data = PCA9548 },
--
2.43.0
next reply other threads:[~2025-06-06 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 9:50 Frank Wunderlich [this message]
2025-06-13 10:27 ` [PATCH v1] i2c: muxes: pca954x: add pca9545 support Michal Simek
2025-07-17 5:57 ` Heiko Schocher
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=20250606095056.22082-1-linux@fw-web.de \
--to=linux@fw-web.de \
--cc=bigunclemax@gmail.com \
--cc=frank-w@public-files.de \
--cc=hs@denx.de \
--cc=michal.simek@amd.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 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.