From: Michael Tretter <m.tretter@pengutronix.de>
To: barebox@lists.infradead.org
Cc: mtr@pengutronix.de
Subject: [PATCH] of_firmware: fix lookup of fpga manager
Date: Tue, 11 Jul 2023 12:19:07 +0200 [thread overview]
Message-ID: <20230711101907.1814921-1-m.tretter@pengutronix.de> (raw)
The of_parse_phandle() looks for the phandle in the root device tree,
but as np is resolved for the target device tree, the phandle refers to
the target device tree and may return a wrong node in the root tree.
Therefore, we must ensure that we look for the manager-node in the
target device tree and look for the manager with that name.
firmwaremgr_find_by_node already uses the name for the lookup.
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
---
drivers/of/of_firmware.c | 30 ++++++++++++++++++++++++------
1 file changed, 24 insertions(+), 6 deletions(-)
diff --git a/drivers/of/of_firmware.c b/drivers/of/of_firmware.c
index 80feb3b90dba..0429875a26c4 100644
--- a/drivers/of/of_firmware.c
+++ b/drivers/of/of_firmware.c
@@ -9,14 +9,32 @@
static struct firmware_mgr *of_node_get_mgr(struct device_node *np)
{
struct device_node *mgr_node;
+ const __be32 *property;
+ phandle phandle;
+ int size;
+ /* Find fpga-mgr phandle, which may be set in a parent fpga-region. */
do {
- mgr_node = of_parse_phandle(np, "fpga-mgr", 0);
- if (mgr_node)
- return firmwaremgr_find_by_node(mgr_node);
- } while ((np = of_get_parent(np)) != NULL);
-
- return NULL;
+ property = of_get_property(np, "fpga-mgr", &size);
+ if (property && size == sizeof(*property))
+ break;
+ } while ((np = of_get_parent(np)) != NULL &&
+ of_device_is_compatible(np, "fpga-region"));
+ if (!property)
+ return NULL;
+ phandle = be32_to_cpup(property);
+
+ /*
+ * The phandle in the np will refer to a device node in the target
+ * tree, which may differ from the phandle in the root tree. We need
+ * the name of the target node, as firmwaremgr_find_by_node performs
+ * the lookup by the node name.
+ */
+ mgr_node = of_find_node_by_phandle_from(phandle, of_find_root_node(np));
+ if (!mgr_node)
+ return NULL;
+
+ return firmwaremgr_find_by_node(mgr_node);
}
struct fw_load_entry {
--
2.39.2
next reply other threads:[~2023-07-11 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 10:19 Michael Tretter [this message]
2023-07-26 12:15 ` Sascha Hauer
2023-08-07 12:02 ` Michael Tretter
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=20230711101907.1814921-1-m.tretter@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mtr@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