All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajendra Nayak <rnayak@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
	linux-omap@vger.kernel.org, Kevin Hilman <khilman@ti.com>,
	Benoit Cousson <b-cousson@ti.com>,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH v2 6/9] omap: dpll: Add allow_idle/deny_idle support for all DPLL's
Date: Tue, 8 Feb 2011 09:47:54 +0530	[thread overview]
Message-ID: <972f3f2e6c362ecdd1f00b412e79ad5d@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102072037530.21991@utopia.booyaka.com>

> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Tuesday, February 08, 2011 9:11 AM
> To: Rajendra Nayak
> Cc: Santosh Shilimkar; linux-omap@vger.kernel.org; Kevin Hilman; Benoit
Cousson; linux-arm-
> kernel@lists.infradead.org
> Subject: RE: [PATCH v2 6/9] omap: dpll: Add allow_idle/deny_idle support
for all DPLL's
>
> On Tue, 8 Feb 2011, Rajendra Nayak wrote:
>
> > > -----Original Message-----
> > > From: Paul Walmsley [mailto:paul@pwsan.com]
> > > Sent: Tuesday, February 08, 2011 8:27 AM
> > >
> > > >  arch/arm/mach-omap2/clock.c          |    8 +++++++-
> > > >  arch/arm/mach-omap2/clock.h          |    1 +
> > > >  arch/arm/mach-omap2/clock3xxx_data.c |    2 +-
> > > >  arch/arm/mach-omap2/clock44xx_data.c |    2 +-
> > > >  arch/arm/mach-omap2/pm44xx.c         |    4 ++++
> > >
> > > Looks like you add the allow_idle/deny_idle functions for the OMAP3
CORE
> > > DPLL, but you don't change mach-omap2/pm34xx.c.  Any reason for
this?
> >
> > Nothing specifically. My initial patchset was enabling these only for
> > OMAP4, So I thought will keep it that way.
>
> That's fine with me, but you might want to drop the OMAP3 part of the
> changes, or put them into a separate patch.

Ok, will add a separate patch for OMAP3 and remove the register
writes from mach-omap2/pm34xx.c.

>
> Also, when you resend the autoidle patches, could you put them into a
> separate series?  There's an autoidle series that I've been working on
> here, and I will add those into that series, and keep the other patch
> series separate.

Ok, will repost these patches as a separate series.

Regards,
Rajendra

>
>
> thanks,
>
> - Paul

WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/9] omap: dpll: Add allow_idle/deny_idle support for all DPLL's
Date: Tue, 8 Feb 2011 09:47:54 +0530	[thread overview]
Message-ID: <972f3f2e6c362ecdd1f00b412e79ad5d@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1102072037530.21991@utopia.booyaka.com>

> -----Original Message-----
> From: Paul Walmsley [mailto:paul at pwsan.com]
> Sent: Tuesday, February 08, 2011 9:11 AM
> To: Rajendra Nayak
> Cc: Santosh Shilimkar; linux-omap at vger.kernel.org; Kevin Hilman; Benoit
Cousson; linux-arm-
> kernel at lists.infradead.org
> Subject: RE: [PATCH v2 6/9] omap: dpll: Add allow_idle/deny_idle support
for all DPLL's
>
> On Tue, 8 Feb 2011, Rajendra Nayak wrote:
>
> > > -----Original Message-----
> > > From: Paul Walmsley [mailto:paul at pwsan.com]
> > > Sent: Tuesday, February 08, 2011 8:27 AM
> > >
> > > >  arch/arm/mach-omap2/clock.c          |    8 +++++++-
> > > >  arch/arm/mach-omap2/clock.h          |    1 +
> > > >  arch/arm/mach-omap2/clock3xxx_data.c |    2 +-
> > > >  arch/arm/mach-omap2/clock44xx_data.c |    2 +-
> > > >  arch/arm/mach-omap2/pm44xx.c         |    4 ++++
> > >
> > > Looks like you add the allow_idle/deny_idle functions for the OMAP3
CORE
> > > DPLL, but you don't change mach-omap2/pm34xx.c.  Any reason for
this?
> >
> > Nothing specifically. My initial patchset was enabling these only for
> > OMAP4, So I thought will keep it that way.
>
> That's fine with me, but you might want to drop the OMAP3 part of the
> changes, or put them into a separate patch.

Ok, will add a separate patch for OMAP3 and remove the register
writes from mach-omap2/pm34xx.c.

>
> Also, when you resend the autoidle patches, could you put them into a
> separate series?  There's an autoidle series that I've been working on
> here, and I will add those into that series, and keep the other patch
> series separate.

Ok, will repost these patches as a separate series.

Regards,
Rajendra

>
>
> thanks,
>
> - Paul

  reply	other threads:[~2011-02-08  4:17 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  9:58 [PATCH v2 0/9] omap4: prcm: Few dpll, clockdomain and powerdomain updates Santosh Shilimkar
2011-02-04  9:58 ` Santosh Shilimkar
2011-02-04  9:58 ` [PATCH v2 1/9] omap4: powerdomain: Add supported INACTIVE power state Santosh Shilimkar
2011-02-04  9:58   ` Santosh Shilimkar
2011-02-06 20:42   ` Paul Walmsley
2011-02-06 20:42     ` Paul Walmsley
2011-02-07  7:03     ` Santosh Shilimkar
2011-02-07  7:03       ` Santosh Shilimkar
2011-02-08  1:32       ` Paul Walmsley
2011-02-08  1:32         ` Paul Walmsley
2011-02-08  6:41         ` Santosh Shilimkar
2011-02-08  6:41           ` Santosh Shilimkar
2011-02-04  9:58 ` [PATCH v2 2/9] omap4: prcm: Fix the CPUx clockdomain offsets Santosh Shilimkar
2011-02-04  9:58   ` Santosh Shilimkar
2011-02-08  4:55   ` Paul Walmsley
2011-02-08  4:55     ` Paul Walmsley
2011-02-25 20:07   ` Paul Walmsley
2011-02-25 20:07     ` Paul Walmsley
2011-02-04  9:58 ` [PATCH v2 3/9] omap4: powerdomain: Use intended PWRSTS_* flags instead of values Santosh Shilimkar
2011-02-04  9:58   ` Santosh Shilimkar
2011-02-08  1:45   ` Paul Walmsley
2011-02-08  1:45     ` Paul Walmsley
2011-02-08  6:37     ` Santosh Shilimkar
2011-02-08  6:37       ` Santosh Shilimkar
2011-02-25 20:10       ` Paul Walmsley
2011-02-25 20:10         ` Paul Walmsley
2011-02-04  9:58 ` [PATCH v2 4/9] omap: clocks: Add checks to see if enable/disable ops are supported Santosh Shilimkar
2011-02-04  9:58   ` Santosh Shilimkar
2011-02-08  1:48   ` Paul Walmsley
2011-02-08  1:48     ` Paul Walmsley
2011-02-08  3:25     ` Rajendra Nayak
2011-02-08  3:25       ` Rajendra Nayak
2011-02-04  9:59 ` [PATCH v2 5/9] omap: clocks: Add allow_idle/deny_idle support in clkops Santosh Shilimkar
2011-02-04  9:59   ` Santosh Shilimkar
2011-02-04  9:59 ` [PATCH v2 6/9] omap: dpll: Add allow_idle/deny_idle support for all DPLL's Santosh Shilimkar
2011-02-04  9:59   ` Santosh Shilimkar
2011-02-08  2:57   ` Paul Walmsley
2011-02-08  2:57     ` Paul Walmsley
2011-02-08  3:28     ` Rajendra Nayak
2011-02-08  3:28       ` Rajendra Nayak
2011-02-08  3:40       ` Paul Walmsley
2011-02-08  3:40         ` Paul Walmsley
2011-02-08  4:17         ` Rajendra Nayak [this message]
2011-02-08  4:17           ` Rajendra Nayak
2011-02-08  4:16     ` Paul Walmsley
2011-02-08  4:16       ` Paul Walmsley
2011-02-04  9:59 ` [PATCH v2 7/9] omap4: dpll: Add dpll api to control GATE_CTRL Santosh Shilimkar
2011-02-04  9:59   ` Santosh Shilimkar
2011-02-04  9:59 ` [PATCH v2 8/9] omap4: dpll: Enable auto gate control for all MX postdividers Santosh Shilimkar
2011-02-04  9:59   ` Santosh Shilimkar
2011-02-04  9:59 ` [PATCH v2 9/9] omap4: clockdomain: Fix the CPUx domain name Santosh Shilimkar
2011-02-04  9:59   ` Santosh Shilimkar
2011-02-08  4:58   ` Paul Walmsley
2011-02-08  4:58     ` Paul Walmsley

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=972f3f2e6c362ecdd1f00b412e79ad5d@mail.gmail.com \
    --to=rnayak@ti.com \
    --cc=b-cousson@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=santosh.shilimkar@ti.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 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.