public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Igor Stoppa <igor.stoppa@nokia.com>
Cc: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] Implement powerdomain off on state counters
Date: Tue, 5 Aug 2008 18:30:20 +0300	[thread overview]
Message-ID: <20080805153018.GT7193@atomide.com> (raw)
In-Reply-To: <1217946503.16579.205.camel@localhost>

* Igor Stoppa <igor.stoppa@nokia.com> [080805 17:38]:
> Hi Tony,
> On Tue, 2008-08-05 at 17:20 +0300, ext Tony Lindgren wrote:
> > * Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> [080724 16:00]:
> > > This patchset implement counters to count the number of off to on state transitions in a powerdomain. These counters will be made available to
> > > drivers in a later patchset to allow them to make a better informed decision wether to restore the hardware registers or not.
> > > 
> > > Peter 'p2' De Schrijver (3):
> > >   Power off on state counter debugging
> > >   Power off on state counter infrastructure
> > >   Add hooks for counting off on power transitions
> > 
> > We should merge these into Paul's powerdomain patches against mainline
> > tree and post them again for more comments to LKML, linux-arm-kernel
> > and linux-pm.
> 
> Dave Brownell commented already that this stuff, albeit apparently
> generic enough to be interesting to other archs, would probably be
> better off being merged in the omap tree, since in the end other SOCs
> tend to be far simpler than OMAP.

Yeah.

> Considering that we are not 100% sure about the usefulness of certain sw
> features - example: the granularity for the bandwidth requirements might
> be too fine - I'd rather avoid bringing in whishlists from other
> architectures, unless they are proven to be really needed.
> 
> And AFAIK so far nobody has come forward with such claim.
> 
> Can't we first get it working in a reliable way on OMAP?

We should first get ack (even if it means no comments) from other
mailing lists before we go ahead implementing this as it affects the
drivers too.

> Whatever survives this process has probably better chances to result
> interesting to other people.

Yeh, but we need to keep them informed throughout the process. Many of
the people that could be commenting the code are not reading linux-omap
list.

Also, we want to get these patches integrated to mainline tree, and
Russell wants to have more review before integrating.

Regards,

Tony

      reply	other threads:[~2008-08-05 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 13:00 [PATCH 0/3] Implement powerdomain off on state counters Peter 'p2' De Schrijver
2008-07-24 13:00 ` [PATCH 1/3] Power off on state counter debugging Peter 'p2' De Schrijver
2008-07-24 13:00   ` [PATCH 2/3] power off on state counter infrastructure Peter 'p2' De Schrijver
2008-07-24 13:00     ` [PATCH 3/3] Add hooks for counting off on power transitions Peter 'p2' De Schrijver
2008-09-04 16:54     ` [PATCH 2/3] power off on state counter infrastructure Paul Walmsley
2008-09-04 19:20   ` [PATCH 1/3] Power off on state counter debugging Kevin Hilman
2008-07-24 13:04 ` [PATCH 0/3] Implement powerdomain off on state counters Peter 'p2' De Schrijver
2008-08-05 14:20 ` Tony Lindgren
2008-08-05 14:28   ` Igor Stoppa
2008-08-05 15:30     ` Tony Lindgren [this message]

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=20080805153018.GT7193@atomide.com \
    --to=tony@atomide.com \
    --cc=igor.stoppa@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.de-schrijver@nokia.com \
    /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