From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org
Cc: sudeep.holla@arm.com, lorenzo.pieralisi@arm.com,
mika.westerberg@linux.intel.com, rafael@kernel.org,
mark.rutland@arm.com, broonie@kernel.org, robh@kernel.org,
ahs3@redhat.com
Subject: [PATCH v3 2/4] device property: Implement fwnode_get_next_parent() using fwnode interface
Date: Thu, 16 Mar 2017 15:34:47 +0200 [thread overview]
Message-ID: <1489671289-20406-3-git-send-email-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <1489671289-20406-1-git-send-email-sakari.ailus@linux.intel.com>
fwnode_get_next_parent() can be implemented using fwnode interface. Do
that to avoid implementing an additional callback for the function in
struct fwnode_operations.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
drivers/base/property.c | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/base/property.c b/drivers/base/property.c
index 6d9476a..9f3d80d 100644
--- a/drivers/base/property.c
+++ b/drivers/base/property.c
@@ -945,17 +945,9 @@ EXPORT_SYMBOL_GPL(device_add_properties);
*/
struct fwnode_handle *fwnode_get_next_parent(struct fwnode_handle *fwnode)
{
- struct fwnode_handle *parent = NULL;
+ struct fwnode_handle *parent = fwnode_call_ptr_op(fwnode, get_parent);
- if (is_of_node(fwnode)) {
- struct device_node *node;
-
- node = of_get_next_parent(to_of_node(fwnode));
- if (node)
- parent = &node->fwnode;
- } else if (is_acpi_node(fwnode)) {
- parent = acpi_node_get_parent(fwnode);
- }
+ fwnode_handle_put(fwnode);
return parent;
}
--
2.7.4
next prev parent reply other threads:[~2017-03-16 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:34 [PATCH v3 0/4] Move firmware specific code to firmware specific locations Sakari Ailus
2017-03-16 13:34 ` [PATCH v3 1/4] device property: Read strings using string array reading functions Sakari Ailus
2017-03-16 13:34 ` Sakari Ailus [this message]
[not found] ` <1489671289-20406-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-16 13:34 ` [PATCH v3 3/4] device property: Move FW type specific functionality to FW specific files Sakari Ailus
2017-03-20 20:57 ` Rob Herring
2017-03-21 8:27 ` Sakari Ailus
2017-03-21 8:28 ` Sakari Ailus
2017-03-16 13:34 ` [PATCH v3 4/4] device property: Move fwnode graph ops to firmware specific locations Sakari Ailus
[not found] ` <1489671289-20406-5-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-20 21:15 ` Rob Herring
2017-03-21 10:54 ` Sakari Ailus
2017-03-21 11:17 ` 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=1489671289-20406-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=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).