From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>,
linux-i3c@lists.infradead.org
Subject: [PATCH] i3c: don't fail if GETHDRCAP is unsupported
Date: Wed, 25 Jun 2025 09:34:52 +0200 [thread overview]
Message-ID: <20250625073505.7949-1-wsa+renesas@sang-engineering.com> (raw)
If a target has the HDR_CAP bit set in BCR, the core wants to get
additional information using the CCC 'GETHDRCAP'. Not all controllers
support this CCC, though. This is not fatal. We can just skip it. The
information is not needed if the controller won't support HDR anyhow.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
Found during the I3C plugfest in Warsaw.
drivers/i3c/master.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
index 204b96e6be1e..b6b96cf9e4e0 100644
--- a/drivers/i3c/master.c
+++ b/drivers/i3c/master.c
@@ -1440,7 +1440,7 @@ static int i3c_master_retrieve_dev_info(struct i3c_dev_desc *dev)
if (dev->info.bcr & I3C_BCR_HDR_CAP) {
ret = i3c_master_gethdrcap_locked(master, &dev->info);
- if (ret)
+ if (ret && ret != -ENOTSUPP)
return ret;
}
--
2.47.2
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next reply other threads:[~2025-06-25 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 7:34 Wolfram Sang [this message]
2025-06-25 15:24 ` [PATCH] i3c: don't fail if GETHDRCAP is unsupported Frank Li
2025-06-25 16:41 ` Wolfram Sang
2025-06-26 2:46 ` Joshua Yeong
2025-07-03 6:41 ` Wolfram Sang
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=20250625073505.7949-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-renesas-soc@vger.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;
as well as URLs for NNTP newsgroup(s).