From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] of: Add of_match_machine helper
Date: Fri, 8 Aug 2014 11:41:25 +0200 [thread overview]
Message-ID: <20140808094123.GC5387@ulmo> (raw)
In-Reply-To: <1407452515-2390-2-git-send-email-ttynkkynen@nvidia.com>
On Fri, Aug 08, 2014 at 02:01:53AM +0300, Tuomas Tynkkynen wrote:
> Add of_match_machine function to test the device tree root for an
> of_match array. This can be useful when testing SoC versions at runtime,
> for example.
>
> Signed-off-by: Tuomas Tynkkynen <ttynkkynen@nvidia.com>
> ---
> drivers/of/base.c | 21 +++++++++++++++++++++
> include/linux/of.h | 3 +++
> 2 files changed, 24 insertions(+)
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index d8574ad..37798ea 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -977,6 +977,27 @@ struct device_node *of_find_matching_node_and_match(struct device_node *from,
> EXPORT_SYMBOL(of_find_matching_node_and_match);
>
> /**
> + * of_match_machine - Tell if root of device tree has a matching of_match struct
> + * @matches: array of of device match structures to search in
> + *
> + * Returns the result of of_match_node for the root node.
> + */
I was going to say that this kerneldoc is weirdly formatted, but when I
looked at the other kerneldoc comments in this file it seems that they
use similarly weird formatting...
> +const struct of_device_id *of_match_machine(const struct of_device_id *matches)
> +{
> + const struct of_device_id *match;
> + struct device_node *root;
> +
> + root = of_find_node_by_path("/");
> + if (!root)
> + return NULL;
> +
> + match = of_match_node(matches, root);
> + of_node_put(root);
> + return match;
> +}
> +EXPORT_SYMBOL(of_match_machine);
I wonder if of_find_node_by_path("/") is somewhat overkill here. Perhaps
simply of_node_get(of_allnodes) would be more appropriate here since the
function is implemented in the core?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140808/67e6af16/attachment.sig>
next prev parent reply other threads:[~2014-08-08 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 23:01 [PATCH 0/3] Introduce of_match_machine() helper Tuomas Tynkkynen
2014-08-07 23:01 ` [PATCH 1/3] of: Add of_match_machine helper Tuomas Tynkkynen
2014-08-08 9:41 ` Thierry Reding [this message]
2014-08-08 13:23 ` Tuomas Tynkkynen
2014-08-08 19:01 ` Rob Herring
2014-08-17 15:31 ` Grant Likely
2014-08-17 15:28 ` Grant Likely
2014-08-18 10:10 ` Tuomas Tynkkynen
2014-08-07 23:01 ` [PATCH 2/3] soc/tegra: Use of_match_machine in soc_is_tegra() Tuomas Tynkkynen
2014-08-07 23:28 ` Stephen Warren
2014-08-08 9:43 ` Thierry Reding
2014-08-07 23:01 ` [PATCH 3/3] cpuidle: big.LITTLE: Use of_match_machine Tuomas Tynkkynen
2014-08-08 9:45 ` Thierry Reding
2014-08-25 17:45 ` [PATCH 0/3] Introduce of_match_machine() helper Stephen Warren
2014-09-19 13:12 ` Peter De Schrijver
2014-09-24 7:44 ` Peter De Schrijver
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=20140808094123.GC5387@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).