From: Neil Armstrong <narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Node names and properties names collision
Date: Thu, 12 May 2016 09:40:21 +0200 [thread overview]
Message-ID: <57343365.6080000@baylibre.com> (raw)
Hi,
I'm working on a full python device tree library to load blobs and manipulate the tree in-memory as an object tree (http://github.com/superna9999/pyfdt).
My testsuite strategy was to run the DTC testsuite and load every DTC generated dtbs, re-generate a DTS and compare the DTC dtb-to-dts output.
But I have a strange case using the Amlogic out-of-tree BSP dts where they use the same name for a sub-node and a property :
efusekey:efusekey{
keynum = <4>;
key0 = <&key0>;
key1 = <&key1>;
key2 = <&key2>;
key3 = <&key3>;
key0:key0{
keyname = "mac";
offset = <0>;
size = <6>;
};
key1:key1{
keyname = "mac_bt";
offset = <6>;
size = <6>;
};
key2:key2{
keyname = "mac_wifi";
offset = <12>;
size = <6>;
};
key3:key3{
keyname = "usid";
offset = <18>;
size = <16>;
};
};
While reading the original ePAPR and the new linaro specifications, I was not able to find an answer....
Is it authorized ? Could this be clarified in the new specifications ?
Neil
next reply other threads:[~2016-05-12 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 7:40 Neil Armstrong [this message]
[not found] ` <57343365.6080000-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-05-12 16:22 ` Node names and properties names collision Stuart Yoder
[not found] ` <HE1PR04MB1641C4DB11CDF2618E27BEF18D730-6LN7OEpIatU5tNmRkpaxD89NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2016-05-13 21:17 ` David Gibson
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=57343365.6080000@baylibre.com \
--to=narmstrong-rdvid1duhrbwk0htik3j/w@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@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.