devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alexander Sverdlin
	<alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] of: Export __of_find_all_nodes()
Date: Thu, 19 Jan 2017 14:42:28 -0800	[thread overview]
Message-ID: <588140D4.1060103@gmail.com> (raw)
In-Reply-To: <d9525715-be49-1cfa-f623-084237e44b4c-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>

On 01/19/17 01:43, Alexander Sverdlin wrote:
> Hi!
> 
> On 18/01/17 22:33, Frank Rowand wrote:
>>> This is necessary for for_each_of_allnodes() to work in the modules.
>>>
>>> Signed-off-by: Alexander Sverdlin <alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
>>> Cc: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
>>> Cc: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>>> ---
>>>  drivers/of/base.c | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/of/base.c b/drivers/of/base.c
>>> index 2eb4dea62b84..f576c33e0b84 100644
>>> --- a/drivers/of/base.c
>>> +++ b/drivers/of/base.c
>>> @@ -270,6 +270,7 @@ struct device_node *__of_find_all_nodes(struct device_node *prev)
>>>  	}
>>>  	return np;
>>>  }
>>> +EXPORT_SYMBOL_GPL(__of_find_all_nodes);
>>>  
>>>  /**
>>>   * of_find_all_nodes - Get next node in global list
>>>
>> Quoting Rob from the last request for this:
>>
>> "What driver needs this? This isn't really a function I'd expect drivers to use."
> 
> This one and the one from previous patch/mail are used in a module which reads DT overlays

If I understand correctly, that was a request to be able to use of_node_init() directly.
Is that correct?

> from pluggable extension boards, eventually performs some sanity checks/corrections and
> applies these overlays. This eventual corrections require low-level access to DT.

Are you saying that you want to modify the device tree data structure after the overlay
is applied?

The idea of sanity checks is one that I am very interested in.  Could the sanity checks
be done statically, either with the overlay source, or with the compiled overlay source?
The idea behind that question is whether the checks could be done while the overlay is
being developed, instead of at run time.

I am also curious about what sort of corrections are made and how it is determined what
corrections to make.


> I cannot judge, how relevant this usecase is for the community, but I was driven by the fact,
> that the functions which require the functions I export are defined statically in .h files
> and therefore are exposed to the modules.
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-01-19 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  9:38 [PATCH] of: Export __of_find_all_nodes() Alexander Sverdlin
     [not found] ` <20170118093849.32204-1-alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2017-01-18 21:33   ` Frank Rowand
     [not found]     ` <587FDF1B.1060206-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-19  9:43       ` Alexander Sverdlin
     [not found]         ` <d9525715-be49-1cfa-f623-084237e44b4c-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2017-01-19 22:42           ` Frank Rowand [this message]
     [not found]             ` <588140D4.1060103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-20  9:59               ` Alexander Sverdlin

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=588140D4.1060103@gmail.com \
    --to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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).