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 02/12] device property: Add fwnode_get_parent()
Date: Tue, 28 Mar 2017 10:52:17 +0300 [thread overview]
Message-ID: <1490687547-18311-3-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>
Now that ACPI has support for returning parent firmware node for both types
of nodes we can expose this to others as well. This adds a new function
fwnode_get_parent() that can be used for DT and ACPI nodes to retrieve the
parent firmware node.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
---
drivers/base/property.c | 25 +++++++++++++++++++++++++
include/linux/property.h | 2 ++
2 files changed, 27 insertions(+)
diff --git a/drivers/base/property.c b/drivers/base/property.c
index c458c63..a252334 100644
--- a/drivers/base/property.c
+++ b/drivers/base/property.c
@@ -932,6 +932,31 @@ int device_add_properties(struct device *dev,
EXPORT_SYMBOL_GPL(device_add_properties);
/**
+ * fwnode_get_parent - Return parent firwmare node
+ * @fwnode: Firmware whose parent is retrieved
+ *
+ * Return parent firmware node of the given node if possible or %NULL if no
+ * parent was available.
+ */
+struct fwnode_handle *fwnode_get_parent(struct fwnode_handle *fwnode)
+{
+ struct fwnode_handle *parent = NULL;
+
+ if (is_of_node(fwnode)) {
+ struct device_node *node;
+
+ node = of_get_parent(to_of_node(fwnode));
+ if (node)
+ parent = &node->fwnode;
+ } else if (is_acpi_node(fwnode)) {
+ parent = acpi_node_get_parent(fwnode);
+ }
+
+ return parent;
+}
+EXPORT_SYMBOL_GPL(fwnode_get_parent);
+
+/**
* device_get_next_child_node - Return the next child node handle for a device
* @dev: Device to find the next child node for.
* @child: Handle to one of the device's child nodes or a null handle.
diff --git a/include/linux/property.h b/include/linux/property.h
index 64e3a9c..ab0a816 100644
--- a/include/linux/property.h
+++ b/include/linux/property.h
@@ -70,6 +70,8 @@ int fwnode_property_read_string(struct fwnode_handle *fwnode,
int fwnode_property_match_string(struct fwnode_handle *fwnode,
const char *propname, const char *string);
+struct fwnode_handle *fwnode_get_parent(struct fwnode_handle *fwnode);
+
struct fwnode_handle *device_get_next_child_node(struct device *dev,
struct fwnode_handle *child);
--
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
2017-03-28 7:52 ` Sakari Ailus [this message]
2017-03-28 7:52 ` [PATCH v6 03/12] ACPI / property: Add fwnode_get_next_child_node() Sakari Ailus
2017-03-28 7:52 ` [PATCH v6 04/12] device property: Add fwnode_get_named_child_node() Sakari Ailus
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
[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
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-3-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).