From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
alexandre.belloni@bootlin.com
Cc: Ben Dooks <ben.dooks@codethink.co.uk>
Subject: [RFC 4/5] i3c: show error messages in of_i3c_master_add_i3c_boardinfo
Date: Wed, 21 Jun 2023 17:20:04 +0100 [thread overview]
Message-ID: <20230621162005.473049-5-ben.dooks@codethink.co.uk> (raw)
In-Reply-To: <20230621162005.473049-1-ben.dooks@codethink.co.uk>
If of_i3c_master_add_i3c_boardinfo() fails, then there's no much to say
what the issue was (most of the error returns are -EINVAL), so add some
printing of the errors using dev_err() showing the node that failed and
what the issue was.
This should help with finding which device-tree node was causing the
issue and also mirrors the i2c case where it shows the node and the
error.
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
---
drivers/i3c/master.c | 20 +++++++++++++++-----
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/drivers/i3c/master.c b/drivers/i3c/master.c
index bc42669f5c6d..2a9ebb1d9d57 100644
--- a/drivers/i3c/master.c
+++ b/drivers/i3c/master.c
@@ -2050,32 +2050,42 @@ of_i3c_master_add_i3c_boardinfo(struct i3c_master_controller *master,
return -ENOMEM;
if (reg[0]) {
- if (reg[0] > I3C_MAX_ADDR)
+ if (reg[0] > I3C_MAX_ADDR) {
+ dev_err(dev, "%pOF: address too big\n", node);
return -EINVAL;
+ }
addrstatus = i3c_bus_get_addr_slot_status(&master->bus,
reg[0]);
- if (addrstatus != I3C_ADDR_SLOT_FREE)
+ if (addrstatus != I3C_ADDR_SLOT_FREE) {
+ dev_err(dev, "%pOF: slot in use\n", node);
return -EINVAL;
+ }
}
boardinfo->static_addr = reg[0];
if (!of_property_read_u32(node, "assigned-address", &init_dyn_addr)) {
- if (init_dyn_addr > I3C_MAX_ADDR)
+ if (init_dyn_addr > I3C_MAX_ADDR) {
+ dev_err(dev, "%pOF: cannot assign address\n", node);
return -EINVAL;
+ }
addrstatus = i3c_bus_get_addr_slot_status(&master->bus,
init_dyn_addr);
- if (addrstatus != I3C_ADDR_SLOT_FREE)
+ if (addrstatus != I3C_ADDR_SLOT_FREE) {
+ dev_err(dev, "%pOF: slot in use\n", node);
return -EINVAL;
+ }
}
boardinfo->pid = ((u64)reg[1] << 32) | reg[2];
if ((boardinfo->pid & GENMASK_ULL(63, 48)) ||
- I3C_PID_RND_LOWER_32BITS(boardinfo->pid))
+ I3C_PID_RND_LOWER_32BITS(boardinfo->pid)) {
+ dev_err(dev, "%pOF: bad PID\n", node);
return -EINVAL;
+ }
boardinfo->init_dyn_addr = init_dyn_addr;
boardinfo->of_node = of_node_get(node);
--
2.40.1
next prev parent reply other threads:[~2023-06-21 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 16:20 [RFC 0/5] updates for i3c error printing Ben Dooks
2023-06-21 16:20 ` [RFC 1/5] i3c: show error with node for invalid reg property Ben Dooks
2023-06-21 16:20 ` [RFC 2/5] i3c: add error print to show device failing during populate bus Ben Dooks
2023-06-21 16:20 ` [RFC 3/5] i3c: show node when printing unsupported 10-bit i2c dev Ben Dooks
2023-06-21 16:20 ` Ben Dooks [this message]
2023-06-21 16:20 ` [RFC 5/5] i3c: dw; add print if cannot get resources Ben Dooks
2023-07-04 21:37 ` Alexandre Belloni
2023-07-11 8:52 ` Ben Dooks
2023-07-04 8:24 ` [RFC 0/5] updates for i3c error printing Ben Dooks
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=20230621162005.473049-5-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@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