From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/4] of/address: Add of_find_matching_node_by_address helper
Date: Sun, 01 May 2011 23:07:50 -0600 [thread overview]
Message-ID: <20110502050750.24800.98133.stgit@ponder> (raw)
In-Reply-To: <20110502045207.24800.91172.stgit@ponder>
of_find_matching_node_by_address() can be used to find a device tree
node for a device at a specific address.
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
---
drivers/of/address.c | 18 ++++++++++++++++++
include/linux/of_address.h | 4 ++++
2 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/drivers/of/address.c b/drivers/of/address.c
index b43ff66..deefc0c 100644
--- a/drivers/of/address.c
+++ b/drivers/of/address.c
@@ -591,6 +591,24 @@ int of_address_to_resource(struct device_node *dev, int index,
}
EXPORT_SYMBOL_GPL(of_address_to_resource);
+struct device_node *of_find_matching_node_by_address(struct device_node *from,
+ const struct of_device_id *matches,
+ u64 base_address)
+{
+ struct device_node *dn = of_find_matching_node(from, matches);
+ struct resource res;
+
+ while (dn) {
+ if (of_address_to_resource(dn, 0, &res))
+ continue;
+ if (res.start == base_address)
+ return dn;
+ dn = of_find_matching_node(dn, matches);
+ }
+
+ return NULL;
+}
+
/**
* of_iomap - Maps the memory mapped IO for a given device_node
diff --git a/include/linux/of_address.h b/include/linux/of_address.h
index 6711d5f..4fbea28 100644
--- a/include/linux/of_address.h
+++ b/include/linux/of_address.h
@@ -7,6 +7,10 @@ extern int of_address_count(struct device_node *np);
extern u64 of_translate_address(struct device_node *np, const __be32 *addr);
extern int of_address_to_resource(struct device_node *dev, int index,
struct resource *r);
+extern struct device_node *of_find_matching_node_by_address(
+ struct device_node *from,
+ const struct of_device_id *matches,
+ u64 base_address);
extern void __iomem *of_iomap(struct device_node *device, int index);
/* Extract an address from a device, returns the region size and
next prev parent reply other threads:[~2011-05-02 5:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 5:07 [RFC PATCH 0/4] ARM: Basic Xilinx Support Grant Likely
2011-05-02 5:07 ` [RFC PATCH 1/4] arm/dt: Add dt machine definition Grant Likely
2011-05-02 5:07 ` Grant Likely [this message]
2011-05-02 5:07 ` [RFC PATCH 3/4] dt/irq: add of_irq_domain_add_simple() helper Grant Likely
2011-05-02 5:08 ` [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support Grant Likely
2011-05-02 7:06 ` Michal Simek
2011-05-02 8:39 ` Arnd Bergmann
2011-05-02 13:29 ` Rob Herring
2011-05-02 15:52 ` Arnd Bergmann
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=20110502050750.24800.98133.stgit@ponder \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.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).