From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: Re: [PATCH v2 04/12] software node: Implement .get_reference_args fwnode operation
Date: Fri, 12 Apr 2019 10:48:41 +0200 [thread overview]
Message-ID: <CAJZ5v0jTR6TqMxRoRhBzG8Rf8JgGfriuCLsGKBYxjBOZz_7yBA@mail.gmail.com> (raw)
In-Reply-To: <20190410152505.87041-5-heikki.krogerus@linux.intel.com>
On Wed, Apr 10, 2019 at 5:26 PM Heikki Krogerus
<heikki.krogerus@linux.intel.com> wrote:
>
> This makes it possible to support drivers that use
> fwnode_property_get_reference_args() function.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/base/swnode.c | 56 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 56 insertions(+)
>
> diff --git a/drivers/base/swnode.c b/drivers/base/swnode.c
> index 39b8f8f35cfe..d6a9b56cb073 100644
> --- a/drivers/base/swnode.c
> +++ b/drivers/base/swnode.c
> @@ -534,6 +534,61 @@ software_node_get_named_child_node(const struct fwnode_handle *fwnode,
> return NULL;
> }
>
> +static int
> +software_node_get_reference_args(const struct fwnode_handle *fwnode,
> + const char *propname, const char *nargs_prop,
> + unsigned int nargs, unsigned int index,
> + struct fwnode_reference_args *args)
> +{
> + struct software_node *swnode = to_software_node(fwnode);
> + struct software_node_reference *ref;
> + const struct property_entry *prop;
> + int ret = -ENOENT;
> + int i;
> +
> + mutex_lock(&swnode->lock);
> +
> + if (!swnode || list_empty(&swnode->references))
> + goto err_unlock;
> +
> + if (nargs_prop) {
> + prop = property_entry_get(swnode->properties, nargs_prop);
> + if (!prop) {
> + ret = -EINVAL;
> + goto err_unlock;
> + }
> +
> + nargs = prop->value.u32_data;
> + }
> +
> + if (nargs > NR_FWNODE_REFERENCE_ARGS) {
> + ret = -EINVAL;
> + goto err_unlock;
> + }
> +
> + list_for_each_entry(ref, &swnode->references, list) {
> + if (strcmp(ref->name, propname))
> + continue;
> +
> + if (index > (ref->nrefs - 1))
> + break;
> +
> + args->nargs = nargs;
> + args->fwnode = software_node_get(ref->args[index].fwnode);
> +
> + for (i = 0; i < nargs; i++)
> + args->args[i] = ref->args[index].args[i];
If nargs is provided by the caller, can't it be greater than the
number of args[index].args[] entries?
> +
> + ret = 0;
> + break;
> + }
> +
> +err_unlock:
> + mutex_unlock(&swnode->lock);
> +
> + return ret;
> +}
> +
> static const struct fwnode_operations software_node_ops = {
> .get = software_node_get,
> .put = software_node_put,
> @@ -543,6 +598,7 @@ static const struct fwnode_operations software_node_ops = {
> .get_parent = software_node_get_parent,
> .get_next_child_node = software_node_get_next_child,
> .get_named_child_node = software_node_get_named_child_node,
> + .get_reference_args = software_node_get_reference_args,
> };
>
> /* -------------------------------------------------------------------------- */
next prev parent reply other threads:[~2019-04-12 8:48 UTC|newest]
Thread overview: 21+ 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 ` [PATCH v2 01/12] software node: Allow node creation without properties 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 ` [PATCH v2 03/12] software node: Add support for references Heikki Krogerus
2019-04-10 15:24 ` [PATCH v2 04/12] software node: Implement .get_reference_args fwnode operation Heikki Krogerus
2019-04-12 8:48 ` Rafael J. Wysocki [this message]
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 ` [PATCH v2 06/12] ACPI / property: Don't limit named child node matching to data nodes Heikki Krogerus
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 ` [PATCH v2 08/12] usb: typec: Registering real device entries for the muxes Heikki Krogerus
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-11 13:31 ` Andy Shevchenko
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 ` [PATCH v2 11/12] platform/x86: intel_cht_int33fe: Link with external dependencies using fwnodes Heikki Krogerus
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-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=CAJZ5v0jTR6TqMxRoRhBzG8Rf8JgGfriuCLsGKBYxjBOZz_7yBA@mail.gmail.com \
--to=rafael@kernel.org \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).