From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alan Tull <atull-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: dynamic device tree char driver
Date: Tue, 21 Aug 2012 11:51:58 -0500 [thread overview]
Message-ID: <5033BCAE.6080902@gmail.com> (raw)
In-Reply-To: <1345559902.4616.157.camel@atc-linux-1>
On 08/21/2012 09:38 AM, Alan Tull wrote:
> On Sat, 2012-08-18 at 10:45 -0500, Rob Herring wrote:
>> On 08/16/2012 02:43 PM, Alan Tull wrote:
>>>
>>> Hello,
>>>
>>> I'm Alan Tull, interested in dynamic features of device trees.
>>
>> Hey Alan. How are you doing?
> Doing good! Nice to hear from you.
>
>>
>>> The following patch adds a char driver to add or remove device tree
>>> nodes dynamically. Its ioctl passes a struct with:
>>> - size of the blob
>>> - pointer to the blob
>>>
>>> The path to add the nodes under is coded in the blob with dummy nodes.
>>> For example the following can be compiled into a blob and sent to this
>>> driver adding a single node under /soc/apb_periphs:
>>>
>>> /dts-v1/;
>>> / {
>>> soc {
>>> apb_periphs {
>>> i2c1: i2c@ffc05000 {
>>> compatible = "snps,designware-i2c";
>>> reg = <0xffc05000 0x1000>;
>>> interrupts = <0 159 4>;
>>> emptyfifo_hold_master = <1>;
>>> };
>>> };
>>> };
>>> };
>>>
>>> I wanted to get feeback early before I went too far down this particular
>>> path. As such, this code doesn't do any notification for drivers yet.
>>> Also it won't properly add nested nodes yet. It can add/remove a single
>>> node and see it show up properly under /proc/device-tree.
>>
>> Have you looked at arch/powerpc/platforms/pseries/reconfig.c?
> Yes. In fact I borrowed a three functions from it and gave credit in
> the patch. I'm trying to do something that is architecture independent
> and that uses the same type of device tree files (blobs) as are used
> during bootup. In my case it will run on an ARM which will have soft
> peripherals instantiated in a FPGA. So after bootup we want to be able
> to reconfigure the IP in the FPGA dynamically, then reconfigure the
> device tree and load some drivers. Pretty cool stuff.That's why I'm
> interested in doing this dynamically without a reboot.
>
>
>> There was also a recent discussion titled "OF_DYNAMIC usage" that you
>> should look at.
>>
>> I don't think a char driver and ioctls will fly...
> Doh! Yes, I know the thread. For some reason, I thought it would be
> better to post a patch as a new thread rather than posting a patch to
> the "OF_DYNAMIC usage" thread but perhaps not. Sorry for forking the
> discussion.
The fork is fine. Just making sure you were aware of it.
> That is where I got the idea of doing ioctls. I am assuming that
> there's only going to be one proper place in the tree for each blob to
> get inserted, so I leave that path information in the blob rather than
> storing it passing it as a separate parameter of the ioctl.
ioctls simply won't fly. So I would start by extending the current
interface to do blobs. From a user standpoint, something like this is
certainly easier to use than an ioctl:
echo "add blob" > /proc/devicetree/ofdt
cat blob.dtb > /proc/devicetree/ofdt
> reconfig.c's interface is pretty bad. It uses /proc as the place for
> the user to write commands. The commands are broken up such that the
> userspace has to 'add _node', then do 'add_property' a few times. Also
> it had to introduce a flag "OF_DYNAMIC" (not to be confused with
> "CONFIG_OF_DYNAMIC") to keep of_node_release from releasing the nodes
> that are allocated in reconfig.c. Seems messy.
>
> With an ioctl, the userspace can just send a single command to add a
> blob. The blob can contain one node or many nodes as long as they all
> end up under the same path. Removing nodes is just as straightforward
> and clean.
Whether paths are part of the blob are debatable. I'm sure you and your
competitors can put your heads together and come up with something. :)
Rob
>>
>> Another option could be kexecing with a new DTB if you can live with a
>> reboot.
> We are looking at reconfiguring soft peripheral in a FPGA on the fly.
> So a reboot won't work here.
>
>>
>> Rob
>>
>>>
>>> Alan Tull
>>> Altera
>>>
>>> _______________________________________________
>>> devicetree-discuss mailing list
>>> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
>>> https://lists.ozlabs.org/listinfo/devicetree-discuss
>>>
>>
>>
>
>
>
next prev parent reply other threads:[~2012-08-21 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 19:43 dynamic device tree char driver Alan Tull
[not found] ` <1345146226-32675-1-git-send-email-atull-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org>
2012-08-16 19:43 ` [PATCH 1/1] " Alan Tull
2012-08-18 15:45 ` Rob Herring
[not found] ` <502FB8A9.4030907-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-21 14:38 ` Alan Tull
2012-08-21 16:51 ` Rob Herring [this message]
[not found] ` <5033BCAE.6080902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-08-21 18:55 ` Alan Tull
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=5033BCAE.6080902@gmail.com \
--to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=atull-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.