From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, Keerthy <j-keerthy@ti.com>,
linux-omap@vger.kernel.org, rnayak@ti.com, b-cousson@ti.com,
Vishwanath BS <vishwanath.bs@ti.com>
Subject: Re: [PATCH 6/6] OMAP4460: Clock: Adding support for 4460 specific clocks
Date: Thu, 6 Oct 2011 11:24:49 -0700 [thread overview]
Message-ID: <20111006182448.GJ6324@atomide.com> (raw)
In-Reply-To: <CAMQu2gyXUER6CQBvp7ccTMSWdWpTuoGoOkAhTgX96Tdeuj0cLw@mail.gmail.com>
* Shilimkar, Santosh <santosh.shilimkar@ti.com> [111003 22:50]:
> On Tue, Oct 4, 2011 at 9:21 AM, Paul Walmsley <paul@pwsan.com> wrote:
> > + Rajendra, Santosh, Benoît
> >
> > Hi
> >
> > On Mon, 3 Oct 2011, Tony Lindgren wrote:
> >
> >> * Paul Walmsley <paul@pwsan.com> [110929 17:40]:
> >> > On Thu, 22 Sep 2011, Keerthy wrote:
> >> >
> >> > > From: Vishwanath BS <vishwanath.bs@ti.com>
> >> > >
> >> > > OMAP4460 specific clocks are not getting added as the
> >> > > cpu_is_omap44xx is choosing only OMAP4430 specific clock nodes.
> >> > > Changing it to add to OMAP4460 specific clocks also.
> >> > > This is clocks are required of temperature sensor.
> >> > >
> >> > > Signed-off-by: Vishwanath BS <vishwanath.bs@ti.com>
> >> > > Signed-off-by: Keerthy <j-keerthy@ti.com>
> >> > > Cc: paul@pwsan.com
> >> >
> >> > Thanks, this patch has been queued for 3.2.
> >>
> >> Should this be a fix for the -rc cycle instead?
> >
> > I don't think it's needed for the -rc series, since we don't have any
> > in-tree users of the 4460 temperature sensor. The only impact I can see
> > is if the bootloader enables the 4460 temperature sensor clock, and
> > doesn't disable it. I assume that would probably prevent the L4 WKUP
> > clockdomain from entering clock stop, which would consume a little more
> > power.
> >
> You are correct Paul. It would have also gated the low power states
> but at this point of time on mainline, we aren't supporting CORE/PER
> low power states for OMAP44XX.
>
> IIRC, boot-loader isn't enabling the temperature
> sensor clock so this patch can wait for next merge window.
OK thanks, sounds like v3.2 merge window is safe for this then.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-06 18:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:29 [PATCH 0/6] system control module device and support for temperature sensor Keerthy
2011-09-22 15:29 ` [PATCH 1/6] OMAP4: Adding the temperature sensor register set bit fields Keerthy
2011-09-23 5:16 ` Paul Walmsley
2011-09-23 5:56 ` J, KEERTHY
2011-09-22 15:29 ` [PATCH 2/6] OMAP4: Clock: Associate clocks for OMAP temperature sensor Keerthy
2011-09-23 5:18 ` Paul Walmsley
2011-09-23 5:53 ` J, KEERTHY
2011-09-23 5:58 ` Paul Walmsley
2011-09-23 13:22 ` J, KEERTHY
2011-09-24 7:38 ` Paul Walmsley
2011-09-22 15:29 ` [PATCH 3/6] OMAP4460: Temperature sensor data Keerthy
2011-09-23 6:03 ` Paul Walmsley
2011-09-23 13:47 ` J, KEERTHY
2011-09-24 7:48 ` Paul Walmsley
2011-09-26 4:25 ` J, KEERTHY
2011-09-24 7:59 ` Paul Walmsley
2011-09-24 9:02 ` J, KEERTHY
2011-09-22 15:29 ` [PATCH 4/6] OMAP4: Hwmod: system control module hwmod Keerthy
2011-09-23 6:15 ` Paul Walmsley
2011-09-23 13:49 ` J, KEERTHY
2011-09-22 15:29 ` [PATCH 5/6] OMAP4: System control module device support Keerthy
2011-09-22 15:29 ` [PATCH 6/6] OMAP4460: Clock: Adding support for 4460 specific clocks Keerthy
2011-09-23 5:49 ` Paul Walmsley
2011-09-23 19:45 ` Paul Walmsley
2011-09-30 1:12 ` Paul Walmsley
2011-10-04 0:43 ` Tony Lindgren
2011-10-04 3:51 ` Paul Walmsley
2011-10-04 6:24 ` Shilimkar, Santosh
2011-10-06 18:24 ` Tony Lindgren [this message]
2011-09-23 5:15 ` [PATCH 0/6] system control module device and support for temperature sensor Paul Walmsley
2011-09-23 5:54 ` J, KEERTHY
2011-09-23 6:35 ` 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=20111006182448.GJ6324@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=vishwanath.bs@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.