From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: "compatible" and "model" properties in .dts for ARC boards
Date: Thu, 5 Nov 2015 18:50:22 +0000 [thread overview]
Message-ID: <1446749422.3151.29.camel@synopsys.com> (raw)
Hi Vineet,
During OpenWRT upsreaming process one interesting topic was raised.
See in the middle of https://lists.openwrt.org/pipermail/openwrt-devel/2015-November/036959.html
In Device Tree descriptions for our boards we don't use "model" property
even though it is a required one as specified by ePAPR, see
http://free-electrons.com/~thomas/pub/Power_ePAPR_APPROVED_v1.0.pdf,
page 39 "Table 3-1 Root node properties".
Instead we put 2 items in "compatible" property.
For example:
------------------->8----------------
compatible = "snps,axs101", "snps,arc-sdp";
------------------->8----------------
here: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arc/boot/dts/axs101.dts#n16
And from ePAPR standpoint it makes sense to split contents of that "compatible"
property in 2:
------------------->8----------------
compatible = "snps,arc-sdp";
model = "snps,axs101";
------------------->8----------------
But I do see problems with implementation of that thing.
Today we have a luxury of selection of AXS init functionality
based on that compatible value and if "snps,axs101" goes in
"model" then we'll need to add some more code in
arch/arc/plat-axs10x/axs10x.c that reads "model" value with
of_get_property() and then compare to "axs10{1|3}".
Any thoughts?
-Alexey
next reply other threads:[~2015-11-05 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 18:50 Alexey Brodkin [this message]
2015-11-06 4:45 ` "compatible" and "model" properties in .dts for ARC boards Vineet Gupta
2015-11-06 4:45 ` Vineet Gupta
2015-11-06 8:59 ` Arnd Bergmann
2015-11-06 8:59 ` Arnd Bergmann
2015-11-06 10:57 ` Jonas Gorski
2015-11-06 10:57 ` Jonas Gorski
2015-11-17 12:18 ` Vineet Gupta
2015-11-17 12:18 ` Vineet Gupta
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=1446749422.3151.29.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@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 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.