From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
rafael@kernel.org
Cc: sudeep.holla@arm.com, lorenzo.pieralisi@arm.com,
mika.westerberg@linux.intel.com, mark.rutland@arm.com,
broonie@kernel.org, robh@kernel.org, ahs3@redhat.com,
frowand.list@gmail.com
Subject: [PATCH v6 04/12] device property: Add fwnode_get_named_child_node()
Date: Tue, 28 Mar 2017 10:52:19 +0300 [thread overview]
Message-ID: <1490687547-18311-5-git-send-email-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <1490687547-18311-1-git-send-email-sakari.ailus@linux.intel.com>
From: Mika Westerberg <mika.westerberg@linux.intel.com>
Since now we have means to enumerate all children of any fwnode even in
ACPI we can implement fwnode_get_named_child_node(). This is similar than
device_get_named_child_node() with the exception that it can be called to
any fwnode handle. Make device_get_named_child_node() call directly this
new function.
This is useful in cases where we need to be able to find child nodes which
are not direct descendants of the parent device.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
---
drivers/base/property.c | 22 +++++++++++++++++-----
include/linux/property.h | 2 ++
2 files changed, 19 insertions(+), 5 deletions(-)
diff --git a/drivers/base/property.c b/drivers/base/property.c
index bc0f07a..538b248 100644
--- a/drivers/base/property.c
+++ b/drivers/base/property.c
@@ -1000,20 +1000,20 @@ struct fwnode_handle *device_get_next_child_node(struct device *dev,
EXPORT_SYMBOL_GPL(device_get_next_child_node);
/**
- * device_get_named_child_node - Return first matching named child node handle
- * @dev: Device to find the named child node for.
+ * fwnode_get_named_child_node - Return first matching named child node handle
+ * @fwnode: Firmware node to find the named child node for.
* @childname: String to match child node name against.
*/
-struct fwnode_handle *device_get_named_child_node(struct device *dev,
+struct fwnode_handle *fwnode_get_named_child_node(struct fwnode_handle *fwnode,
const char *childname)
{
struct fwnode_handle *child;
/*
- * Find first matching named child node of this device.
+ * Find first matching named child node of this fwnode.
* For ACPI this will be a data only sub-node.
*/
- device_for_each_child_node(dev, child) {
+ fwnode_for_each_child_node(fwnode, child) {
if (is_of_node(child)) {
if (!of_node_cmp(to_of_node(child)->name, childname))
return child;
@@ -1025,6 +1025,18 @@ struct fwnode_handle *device_get_named_child_node(struct device *dev,
return NULL;
}
+EXPORT_SYMBOL_GPL(fwnode_get_named_child_node);
+
+/**
+ * device_get_named_child_node - Return first matching named child node handle
+ * @dev: Device to find the named child node for.
+ * @childname: String to match child node name against.
+ */
+struct fwnode_handle *device_get_named_child_node(struct device *dev,
+ const char *childname)
+{
+ return fwnode_get_named_child_node(dev_fwnode(dev), childname);
+}
EXPORT_SYMBOL_GPL(device_get_named_child_node);
/**
diff --git a/include/linux/property.h b/include/linux/property.h
index f4786a86..514b195 100644
--- a/include/linux/property.h
+++ b/include/linux/property.h
@@ -85,6 +85,8 @@ struct fwnode_handle *device_get_next_child_node(struct device *dev,
for (child = device_get_next_child_node(dev, NULL); child; \
child = device_get_next_child_node(dev, child))
+struct fwnode_handle *fwnode_get_named_child_node(struct fwnode_handle *fwnode,
+ const char *childname);
struct fwnode_handle *device_get_named_child_node(struct device *dev,
const char *childname);
--
2.7.4
next prev parent reply other threads:[~2017-03-28 7:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 7:52 [PATCH v6 00/12] ACPI graph support Sakari Ailus
[not found] ` <1490687547-18311-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-28 7:52 ` [PATCH v6 01/12] ACPI / property: Add possiblity to retrieve parent firmware node Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 12/12] ACPI / DSD: Document references, ports and endpoints Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 02/12] device property: Add fwnode_get_parent() Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 03/12] ACPI / property: Add fwnode_get_next_child_node() Sakari Ailus
2017-03-28 7:52 ` Sakari Ailus [this message]
2017-03-28 7:52 ` [PATCH v6 05/12] ACPI / property: Add support for remote endpoints Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 06/12] device " Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 07/12] device property: Add fwnode_handle_get() Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 08/12] of: Add of_fwnode_handle() to convert device nodes to fwnode_handle Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 09/12] device property: Make dev_fwnode() public Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 10/12] device property: Add support for fwnode endpoints Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 11/12] device property: Add fwnode_get_next_parent() Sakari Ailus
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=1490687547-18311-5-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
/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).