From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kevin Hilman <khilman@ti.com>
Subject: Re: [PATCH] ARM: OMAP4: clock: Add CPU local timer clock node
Date: Fri, 16 Dec 2011 11:46:48 -0800 [thread overview]
Message-ID: <20111216194648.GF32251@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112160456380.12660@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [111216 03:31]:
>
> From: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> Local timer clock is sourced from the CPU clock and hence changes
> along with CPU clock. These per CPU local timers are used as
> clock-events, so they need to be reconfigured on CPU frequency
> change as part of CPUfreq governor.
>
> Newly introduced clockevents_reconfigure() needs to know the
> twd clock-rate. Provide a clock-node to make clk_get_rate() work
> for TWD.
>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
> Cc: Kevin Hilman <khilman@ti.com>
> [paul@pwsan.com: renamed clock node to 'mpu_periphclk' to indicate that this
> is the Cortex-A9 MPCore subsystem clock PERIPHCLK (DDI 0407G); moved
> clock and clkdev entries to match the autogenerated script output]
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
>
> ---
> This version 3 has been updated by Santosh to use "smp_twd" as the dev_id
> and a NULL con_id, to match Linus Walleij's code.
Thanks applying into fixes-non-critical-part2.
Regards,
Tony
prev parent reply other threads:[~2011-12-16 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 12:03 [PATCH] ARM: OMAP4: clock: Add CPU local timer clock node Paul Walmsley
2011-12-16 19:46 ` 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=20111216194648.GF32251@atomide.com \
--to=tony@atomide.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 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).