From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 06/12] ACPI / property: Don't limit named child node matching to data nodes
Date: Thu, 11 Apr 2019 16:02:33 +0300 [thread overview]
Message-ID: <20190411130233.GA29292@kuha.fi.intel.com> (raw)
In-Reply-To: <20190410152505.87041-7-heikki.krogerus@linux.intel.com>
Hi Rafael,
On Wed, Apr 10, 2019 at 06:24:59PM +0300, Heikki Krogerus wrote:
> There is no reason why we should limit the use of
> fwnode_get_named_child_node() to data nodes only.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/acpi/property.c | 26 ++++++++++++++++++++------
> 1 file changed, 20 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/acpi/property.c b/drivers/acpi/property.c
> index 77abe0ec4043..c3fb52c387a6 100644
> --- a/drivers/acpi/property.c
> +++ b/drivers/acpi/property.c
> @@ -602,15 +602,29 @@ static struct fwnode_handle *
> acpi_fwnode_get_named_child_node(const struct fwnode_handle *fwnode,
> const char *childname)
> {
> + char name[ACPI_PATH_SEGMENT_LENGTH];
> struct fwnode_handle *child;
> + struct acpi_buffer path;
> + acpi_status status;
>
> - /*
> - * Find first matching named child node of this fwnode.
> - * For ACPI this will be a data only sub-node.
> - */
> - fwnode_for_each_child_node(fwnode, child)
> - if (acpi_data_node_match(child, childname))
> + path.length = sizeof(name);
> + path.pointer = name;
> +
> + fwnode_for_each_child_node(fwnode, child) {
> + if (is_acpi_data_node(child)) {
> + if (acpi_data_node_match(child, childname))
> + return child;
> + continue;
> + }
> +
> + status = acpi_get_name(ACPI_HANDLE_FWNODE(child),
> + ACPI_SINGLE_NAME, &path);
> + if (ACPI_FAILURE(status))
> + break;
> +
> + if (!strncmp(name, childname, ACPI_NAME_SIZE))
I rebased these on of todays linux-next, and noticed that Bob renamed
ACPI_NAME_SIZE to ACPI_NAMESEG_SIZE in commit 3278675567df ("ACPICA:
Rename nameseg length macro/define for clarity").
I'll fix that and resend these tomorrow.
thanks,
--
heikki
next prev parent reply other threads:[~2019-04-11 13:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 15:24 [PATCH 00/12] Software fwnode references Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 01/12] software node: Allow node creation without properties Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 02/12] software node: Simplify software_node_release() function Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 03/12] software node: Add support for references Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 04/12] software node: Implement .get_reference_args fwnode operation Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-12 8:48 ` Rafael J. Wysocki
2019-04-12 8:48 ` Rafael J. Wysocki
2019-04-12 11:40 ` Heikki Krogerus
2019-04-12 11:40 ` Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 05/12] driver core: Add helper device_find_child_by_name() Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 06/12] ACPI / property: Don't limit named child node matching to data nodes Heikki Krogerus
2019-04-10 15:24 ` Heikki Krogerus
2019-04-11 13:02 ` Heikki Krogerus [this message]
2019-04-11 13:02 ` Heikki Krogerus
2019-04-10 15:25 ` [PATCH v2 07/12] device connection: Find connections also by checking the references Heikki Krogerus
2019-04-10 15:25 ` Heikki Krogerus
2019-04-10 15:25 ` [PATCH v2 08/12] usb: typec: Registering real device entries for the muxes Heikki Krogerus
2019-04-10 15:25 ` Heikki Krogerus
2019-04-11 12:34 ` Andy Shevchenko
2019-04-11 12:34 ` Andy Shevchenko
2019-04-10 15:25 ` [PATCH v2 09/12] platform/x86: intel_cht_int33fe: Provide software nodes for the devices Heikki Krogerus
2019-04-10 15:25 ` Heikki Krogerus
2019-04-11 13:31 ` Andy Shevchenko
2019-04-11 13:31 ` Andy Shevchenko
2019-04-11 13:35 ` Heikki Krogerus
2019-04-11 13:35 ` Heikki Krogerus
2019-04-10 15:25 ` [PATCH v2 10/12] platform/x86: intel_cht_int33fe: Provide fwnode for the USB connector Heikki Krogerus
2019-04-10 15:25 ` Heikki Krogerus
2019-04-10 15:25 ` [PATCH v2 11/12] platform/x86: intel_cht_int33fe: Link with external dependencies using fwnodes Heikki Krogerus
2019-04-10 15:25 ` Heikki Krogerus
2019-04-11 13:28 ` Andy Shevchenko
2019-04-11 13:28 ` Andy Shevchenko
2019-04-10 15:25 ` [PATCH v2 12/12] platform/x86: intel_cht_int33fe: Replacing the old connections with references Heikki Krogerus
2019-04-10 15:25 ` Heikki Krogerus
2019-04-11 13:30 ` Andy Shevchenko
2019-04-11 13:30 ` Andy Shevchenko
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=20190411130233.GA29292@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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