All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH V2 0/9] ARM: tegra: add platform suspend support
Date: Wed, 13 Mar 2013 22:43:52 -0600	[thread overview]
Message-ID: <51415588.7080403@wwwdotorg.org> (raw)
In-Reply-To: <1363224385.3308.8.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>

On 03/13/2013 07:26 PM, Joseph Lo wrote:
> On Thu, 2013-03-14 at 01:34 +0800, Stephen Warren wrote:
>> 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?
>>
> There are still two main features for PMC that we need to define
> bindings/properties in DT. One is power main the other wake up source.
> But we are not there yet. Because I don't have drivers to verify them is
> enough or not. If I add all the bindings right now, I believe it will be
> modify later.

Since the DT is supposed to be a representation of the HW, and not a
representation of what a particular driver needs, I'm not sue why you'd
need to be able to test a driver before you could design a DT binding.

WARNING: multiple messages have this Message-ID (diff)
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 22:43:52 -0600	[thread overview]
Message-ID: <51415588.7080403@wwwdotorg.org> (raw)
In-Reply-To: <1363224385.3308.8.camel@jlo-ubuntu-64.nvidia.com>

On 03/13/2013 07:26 PM, Joseph Lo wrote:
> On Thu, 2013-03-14 at 01:34 +0800, Stephen Warren wrote:
>> 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?
>>
> There are still two main features for PMC that we need to define
> bindings/properties in DT. One is power main the other wake up source.
> But we are not there yet. Because I don't have drivers to verify them is
> enough or not. If I add all the bindings right now, I believe it will be
> modify later.

Since the DT is supposed to be a representation of the HW, and not a
representation of what a particular driver needs, I'm not sue why you'd
need to be able to test a driver before you could design a DT binding.

  parent reply	other threads:[~2013-03-14  4:43 UTC|newest]

Thread overview: 14+ 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  4:01 ` Joseph Lo
     [not found] ` <1363060916-8897-1-git-send-email-josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-12 19:32   ` Stephen Warren
2013-03-12 19:32     ` Stephen Warren
     [not found]     ` <513F82EB.1030407-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-13  6:04       ` Joseph Lo
2013-03-13  6:04         ` Joseph Lo
     [not found]         ` <1363154644.3998.140.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-03-13 17:34           ` Stephen Warren
2013-03-13 17:34             ` Stephen Warren
     [not found]             ` <5140B893.9010704-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-14  1:26               ` Joseph Lo
2013-03-14  1:26                 ` Joseph Lo
     [not found]                 ` <1363224385.3308.8.camel-yx3yKKdKkHfc7b1ADBJPm0n48jw8i0AO@public.gmane.org>
2013-03-14  4:43                   ` Stephen Warren [this message]
2013-03-14  4:43                     ` Stephen Warren
     [not found]                     ` <51415588.7080403-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-14 10:05                       ` Joseph Lo
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=51415588.7080403@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-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.