From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
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: Re: [PATCH v4 15/16] device property: Add fwnode_get_next_parent()
Date: Tue, 14 Mar 2017 09:51:02 +0200 [thread overview]
Message-ID: <d2c06f1b-fd77-83b1-341e-04c61f8bd839@linux.intel.com> (raw)
In-Reply-To: <2027673.WAD1C0MHDO@aspire.rjw.lan>
On 03/13/17 23:58, Rafael J. Wysocki wrote:
> On Monday, March 06, 2017 04:19:29 PM Sakari Ailus wrote:
>> In order to differentiate the functionality between dropping a reference
>> to the node (or not) for the benefit of OF, introduce
>> fwnode_get_next_parent().
>>
>> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>> ---
>> drivers/base/property.c | 29 +++++++++++++++++++++++++++++
>> include/linux/property.h | 1 +
>> 2 files changed, 30 insertions(+)
>>
>> diff --git a/drivers/base/property.c b/drivers/base/property.c
>> index b8c1017..defeba9 100644
>> --- a/drivers/base/property.c
>> +++ b/drivers/base/property.c
>> @@ -953,6 +953,35 @@ int device_add_properties(struct device *dev,
>> EXPORT_SYMBOL_GPL(device_add_properties);
>>
>> /**
>> + * fwnode_get_next_parent - Iterate to the node's parent
>> + * @fwnode: Firmware whose parent is retrieved
>> + *
>> + * This is like fwnode_get_parent() except that it drops the refcount
>> + * on the passed node, making it suitable for iterating through a
>> + * node's parents.
>> + *
>> + * Returns a node pointer with refcount incremented, use
>> + * fwnode_handle_node() on it when done.
>> + */
>> +struct fwnode_handle *fwnode_get_next_parent(struct fwnode_handle *fwnode)
>> +{
>> + struct fwnode_handle *parent = NULL;
>> +
>> + if (is_of_node(fwnode)) {
>> + struct device_node *node;
>> +
>> + node = of_get_next_parent(to_of_node(fwnode));
>
> So I would fold the [14/15] into this one and then it should be clear why that
> change was useful.
Ok, I'll fold the two patches.
--
Regards,
Sakari Ailus
sakari.ailus@linux.intel.com
prev parent reply other threads:[~2017-03-14 7:51 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 14:19 [PATCH v4 00/16] Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 02/16] device property: Add fwnode_get_parent() Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 03/16] ACPI / property: Add fwnode_get_next_child_node() Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 04/16] device property: Add fwnode_get_named_child_node() Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 06/16] device property: Add support for remote endpoints Sakari Ailus
[not found] ` <1488809970-25568-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-06 14:19 ` [PATCH v4 01/16] ACPI / property: Add possiblity to retrieve parent firmware node Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 05/16] ACPI / property: Add support for remote endpoints Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 07/16] device property: Add fwnode_handle_get() Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 09/16] driver core: Arrange headers alphabetically Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 12/16] device property: Move dev_fwnode() to linux/property.h Sakari Ailus
2017-03-13 21:49 ` Rafael J. Wysocki
[not found] ` <5262143.K42JDpMSHF-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2017-03-14 7:28 ` Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 13/16] device property: Add support for fwnode endpoints Sakari Ailus
2017-03-13 21:52 ` Rafael J. Wysocki
2017-03-14 7:46 ` Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 14/16] of: Add nop implementation of of_get_next_parent() Sakari Ailus
2017-03-13 21:55 ` Rafael J. Wysocki
2017-03-17 12:10 ` Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 16/16] ACPI / DSD: Document references, ports and endpoints Sakari Ailus
2017-03-13 22:08 ` Rafael J. Wysocki
2017-03-14 8:08 ` Sakari Ailus
2017-03-14 8:09 ` Sakari Ailus
2017-03-14 17:05 ` Rafael J. Wysocki
[not found] ` <CAJZ5v0j1i-tNOdyhhknYCSPbOg7KAQpYgeReH_KwgebO3AcjRA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-14 17:54 ` Sakari Ailus
[not found] ` <cf2ab8be-a351-f1ea-28a9-f5cca57061cd-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-14 20:43 ` Rafael J. Wysocki
[not found] ` <CAJZ5v0i4pEKkz+3Ob42x96YHpPWasH2O8VnDCz8aKw_wxywLyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-14 21:16 ` Sakari Ailus
2017-03-14 22:11 ` Rafael J. Wysocki
[not found] ` <CAJZ5v0hCvcPgYYV0Hysfu0pEYCzzHp7KKdW3nYyjm7RGS3bHoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-14 22:53 ` Sakari Ailus
2017-03-14 23:13 ` Rafael J. Wysocki
2017-03-15 8:23 ` Sakari Ailus
2017-03-15 9:33 ` Sakari Ailus
2017-03-15 11:28 ` Rafael J. Wysocki
[not found] ` <1595427.gxrcIpTbyD-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2017-03-15 11:45 ` Sakari Ailus
2017-03-15 11:53 ` Rafael J. Wysocki
2017-03-15 12:26 ` Sakari Ailus
[not found] ` <ceae0f71-dbac-36b8-f8df-fa138e6f24b2-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-15 14:21 ` Rafael J. Wysocki
2017-03-16 11:30 ` Sakari Ailus
2017-03-07 7:49 ` [PATCH v4 00/16] ACPI graph support Sakari Ailus
2017-03-07 13:23 ` Rafael J. Wysocki
2017-03-07 13:49 ` Sakari Ailus
2017-03-09 23:05 ` Rafael J. Wysocki
2017-03-10 8:19 ` Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 08/16] of: Add of_fwnode_handle() to convert device nodes to fwnode_handle Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 10/16] irqchip/gic: Add missing forward declaration for struct device Sakari Ailus
2017-03-13 21:45 ` Rafael J. Wysocki
2017-03-06 14:19 ` [PATCH v4 11/16] of: No need to include linux/property.h, linux/fwnode.h is sufficient Sakari Ailus
2017-03-13 21:46 ` Rafael J. Wysocki
2017-03-15 13:58 ` Sakari Ailus
2017-03-06 14:19 ` [PATCH v4 15/16] device property: Add fwnode_get_next_parent() Sakari Ailus
2017-03-13 21:58 ` Rafael J. Wysocki
2017-03-14 7:51 ` Sakari Ailus [this message]
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=d2c06f1b-fd77-83b1-341e-04c61f8bd839@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=rjw@rjwysocki.net \
--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).