From: Kevin Hilman <khilman@deeprootsystems.com>
To: Sanjeev Premi <premi@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP35x: Add support for 720MHz part
Date: Tue, 13 Oct 2009 12:14:20 -0700 [thread overview]
Message-ID: <874oq3ksxf.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1255351453-9023-1-git-send-email-premi@ti.com> (Sanjeev Premi's message of "Mon\, 12 Oct 2009 18\:14\:09 +0530")
Sanjeev Premi <premi@ti.com> writes:
> This patch adds support for ARM running at 720MHz part.
>
> The 720MHz capability can be probed run-time by reading the
> PRODID.SKUID[3:0] at 0x4830A20C.
>
> [1] http://focus.ti.com/lit/ug/spruff1d/spruff1d.pdf
>
> Signed-off-by: Sanjeev Premi <premi@ti.com>
>
> ---
> arch/arm/mach-omap2/clock34xx.c | 6 ++++++
> arch/arm/mach-omap2/id.c | 11 +++++++++++
> arch/arm/plat-omap/include/mach/control.h | 7 +++++++
> arch/arm/plat-omap/include/mach/cpu.h | 2 ++
> 4 files changed, 26 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/clock34xx.c b/arch/arm/mach-omap2/clock34xx.c
> index 489556e..9b56af3 100644
> --- a/arch/arm/mach-omap2/clock34xx.c
> +++ b/arch/arm/mach-omap2/clock34xx.c
> @@ -1096,6 +1096,12 @@ static int __init omap2_clk_arch_init(void)
> if (!mpurate)
> return -EINVAL;
>
> + if ((mpurate == 720000000) && !omap3_has_720mhz()) {
> + printk(KERN_ERR "*** Silicon doesn't support 720MHz\n");
> +
> + mpurate = 600000000; /* Set to highest supported */
> + }
> +
This is very platform specific check here. We're not checking for any
other valid mpurate values here. I think we should leave it to the
(forthcoming) OPP layer to to validate the frequency etc.
I recommend just dropping the clock34xx.c changes and posting a patch
which just adds the new speed as a feature.
> /* REVISIT: not yet ready for 343x */
> if (clk_set_rate(&dpll1_ck, mpurate))
> printk(KERN_ERR "*** Unable to set MPU rate\n");
> diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
> index d4d563b..e0b427a 100644
> --- a/arch/arm/mach-omap2/id.c
> +++ b/arch/arm/mach-omap2/id.c
> @@ -79,6 +79,7 @@ EXPORT_SYMBOL(omap_type);
> #define OMAP_TAP_DIE_ID_2 0x0220
> #define OMAP_TAP_DIE_ID_3 0x0224
>
> +
stray whitespace change
> #define read_tap_reg(reg) __raw_readl(tap_base + (reg))
>
> struct omap_id {
> @@ -180,6 +181,15 @@ void __init omap3_check_features(void)
> * TODO: Get additional info (where applicable)
> * e.g. Size of L2 cache.
> */
> +
> + /*
> + * Does it support 720MHz?
> + */
> + status = (OMAP3_SKUID_MASK & read_tap_reg(OMAP3_PRODID));
> +
Some comment here that the runtime detection of this feature is only
available on 35xx parts would be useful too.
Kevin
prev parent reply other threads:[~2009-10-13 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 12:44 [PATCH] OMAP35x: Add support for 720MHz part Sanjeev Premi
2009-10-13 15:51 ` Tony Lindgren
2009-10-13 19:14 ` Kevin Hilman [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=874oq3ksxf.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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