From: Pranav Tilak <pranav.vinaytilak@amd.com>
To: <u-boot@lists.denx.de>, <michal.simek@amd.com>
Cc: <git@amd.com>, <padmarao.begari@amd.com>,
Pranav Tilak <pranav.vinaytilak@amd.com>,
Dinesh <dinesh.maniyam@altera.com>, Tom Rini <trini@konsulko.com>
Subject: [PATCH v2 1/4] i3c: dw: make resets optional in probe
Date: Thu, 9 Jul 2026 14:42:52 +0530 [thread overview]
Message-ID: <20260709091357.1860417-2-pranav.vinaytilak@amd.com> (raw)
In-Reply-To: <20260709091357.1860417-1-pranav.vinaytilak@amd.com>
Treat -ENOENT and -ENOTSUPP from reset_get_bulk() as non-fatal to
support platforms where no resets are defined in the DTS. The resets
property is not yet documented in the DT binding.
Fixes: 1009c96f1590 ("drivers: i3c: Add driver for MIPI DWI3C")
Signed-off-by: Pranav Tilak <pranav.vinaytilak@amd.com>
---
drivers/i3c/master/dw-i3c-master.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i3c/master/dw-i3c-master.c b/drivers/i3c/master/dw-i3c-master.c
index 0c4af7e528a..c6ce54a1d3b 100644
--- a/drivers/i3c/master/dw-i3c-master.c
+++ b/drivers/i3c/master/dw-i3c-master.c
@@ -972,7 +972,7 @@ static int dw_i3c_probe(struct udevice *dev)
}
ret = reset_get_bulk(dev, &master->resets);
- if (ret) {
+ if (ret && ret != -ENOTSUPP && ret != -ENOENT) {
dev_err(dev, "Can't get reset: %d\n", ret);
return ret;
}
--
2.34.1
next prev parent reply other threads:[~2026-07-09 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 9:12 [PATCH v2 0/4] i3c: dw: fix slave device setup and probe issues Pranav Tilak
2026-07-09 9:12 ` Pranav Tilak [this message]
2026-07-09 9:12 ` [PATCH v2 2/4] cmd: i3c: fix list and current needing pre-selected controller Pranav Tilak
2026-07-09 9:12 ` [PATCH v2 3/4] configs: versal2: enable I3C support Pranav Tilak
2026-07-09 9:12 ` [PATCH v2 4/4] i3c: dw: fix slave device setup after DAA Pranav Tilak
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=20260709091357.1860417-2-pranav.vinaytilak@amd.com \
--to=pranav.vinaytilak@amd.com \
--cc=dinesh.maniyam@altera.com \
--cc=git@amd.com \
--cc=michal.simek@amd.com \
--cc=padmarao.begari@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.