From: Alan Tull <atull-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org>
To: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Cc: Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Subject: dynamic device tree char driver
Date: Thu, 16 Aug 2012 14:43:45 -0500 [thread overview]
Message-ID: <1345146226-32675-1-git-send-email-atull@altera.com> (raw)
Hello,
I'm Alan Tull, interested in dynamic features of device trees.
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.
Alan Tull
Altera
next reply other threads:[~2012-08-16 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 19:43 Alan Tull [this message]
[not found] ` <1345146226-32675-1-git-send-email-atull-EIB2kfCEclfQT0dZR+AlfA@public.gmane.org>
2012-08-16 19:43 ` [PATCH 1/1] dynamic device tree char driver 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
[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=1345146226-32675-1-git-send-email-atull@altera.com \
--to=atull-eib2kfceclfqt0dzr+alfa@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@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).