From: Stephen Warren <swarren@wwwdotorg.org>
To: Graeme Gregory <gg@slimlogic.co.uk>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
J Keerthy <j-keerthy@ti.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"rob@landley.net" <rob@landley.net>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"b-cousson@ti.com" <b-cousson@ti.com>
Subject: Re: [PATCH 1/4] documentation: add palmas dts definition
Date: Thu, 28 Feb 2013 12:01:53 -0700 [thread overview]
Message-ID: <512FA9A1.7070701@wwwdotorg.org> (raw)
In-Reply-To: <512F3810.30109@slimlogic.co.uk>
On 02/28/2013 03:57 AM, Graeme Gregory wrote:
...
> The final but of information that would be needed is some method to pass
> down product_id/design_rev and for a lot of the IP blocks they could be
> made independent of the actual parent.
That should probably be represented in DT itself as differing compatible
values.
I could see the argument that this is SW-probe-able since there's a
register that defines the value. However, any global ID register would
apply to the top-level device, and not the version of any child IP
blocks if there's the possibility of mixing/matching IP blocks. If
there's a dedicated version register for a child IP block, then
presumably it's already part of the child IP block's register space, and
so the driver can read it, and then there perhaps wouldn't be a need to
represent this using different compatible values.
next prev parent reply other threads:[~2013-02-28 19:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 5:11 [PATCH 1/4] documentation: add palmas dts definition J Keerthy
2013-02-27 18:32 ` Stephen Warren
2013-02-28 8:52 ` Laxman Dewangan
2013-02-28 9:58 ` Graeme Gregory
2013-02-28 10:27 ` Laxman Dewangan
2013-02-28 10:57 ` Graeme Gregory
2013-02-28 11:21 ` Graeme Gregory
2013-02-28 19:01 ` Stephen Warren [this message]
2013-02-28 18:58 ` Stephen Warren
[not found] ` <512F1ADF.90906-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-28 18:51 ` Stephen Warren
2013-02-28 12:09 ` J, KEERTHY
2013-02-28 19:07 ` Stephen Warren
2013-03-01 2:24 ` J, KEERTHY
-- strict thread matches above, loose matches on Subject: below --
2013-02-20 4:00 J Keerthy
2013-02-20 11:26 ` Mark Brown
2013-02-20 13:49 ` J, KEERTHY
2013-02-27 18:16 ` Stephen Warren
2013-03-02 4:07 ` Mark Brown
2013-02-25 8:55 ` J, KEERTHY
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=512FA9A1.7070701@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=j-keerthy@ti.com \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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).