From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/9] ARM: tegra: add platform suspend support
Date: Wed, 13 Mar 2013 11:34:11 -0600 [thread overview]
Message-ID: <5140B893.9010704@wwwdotorg.org> (raw)
In-Reply-To: <1363154644.3998.140.camel@jlo-ubuntu-64.nvidia.com>
On 03/13/2013 12:04 AM, Joseph Lo wrote:
...
> BTW, I want to mention one thing about PMC DT bindings. Because I can't
> add all of the PMC DT bindings in one time, the PMC is related to too
> many devices to work for runtime PM and power domain control. And some
> wake up sources control for deep sleep mode (LP0). They are still under
> developing for upstream. May I add more bindings for PMC later?
With DT you are supposed to define the complete DT binding for the HW up
front. There have been some hints that incrementally defining bindings
will start to get push-back. How hard is it in this case to simply
define the entire binding right now?
That said, in practice, you can certainly incrementally define bindings
at the moment. The main issue here is to ensure that when you add the
new properties/..., then:
a) You don't change anything that's already there. The old properties
and content must continue to work without modification.
b) For all nodes/properties that are newly required, either there is a
suitable default if they are missing from the DT (as they would be for
DTs written to the old specification), /or/ the new nodes/properties
only enable new features, so that any old DT continues to work fine with
at least as many features as it always did.
If you satisfy those conditions, I believe we can still get away with
incrementally defining bindings. I don't know how long that will last
though.
next prev parent reply other threads:[~2013-03-13 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 4:01 [PATCH V2 0/9] ARM: tegra: add platform suspend support Joseph Lo
2013-03-12 19:32 ` Stephen Warren
2013-03-13 6:04 ` Joseph Lo
2013-03-13 17:34 ` Stephen Warren [this message]
2013-03-14 1:26 ` Joseph Lo
2013-03-14 4:43 ` Stephen Warren
2013-03-14 10:05 ` Joseph Lo
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=5140B893.9010704@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@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 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).