From: "Ville Syrjälä" <syrjala@sci.fi>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Andrew Victor <linux@maxim.org.za>,
David Brownell <david-b@pacbell.net>,
Patrice VILCHEZ <patrice.vilchez@atmel.com>,
Sedji GAOUAOU <sedji.gaouaou@atmel.com>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] AT91: manage clock by functionality instead of CPUs
Date: Sun, 22 Mar 2009 13:57:10 +0200 [thread overview]
Message-ID: <20090322115710.GV10127@sci.fi> (raw)
In-Reply-To: <49C37677.8090508@atmel.com>
On Fri, Mar 20, 2009 at 11:56:55AM +0100, Nicolas Ferre wrote:
> --- a/arch/arm/mach-at91/clock.c
> +++ b/arch/arm/mach-at91/clock.c
> @@ -45,6 +45,25 @@
> #define clk_is_sys(x) ((x)->type & CLK_TYPE_SYSTEM)
>
>
> +/*
> + * Chips have some kind of clocks : group them by functionality
> + */
> +#define cpu_has_utmi() ( cpu_is_at91cap9() \
> + || cpu_is_at91sam9rl())
> +
> +#define cpu_has_800M_plla() (cpu_is_at91sam9g20())
> +
> +#define cpu_has_pllb() (!(cpu_is_at91sam9rl()))
Useless parentheses.
> +
> +#define cpu_has_upll() (0)
Is this for some future chip?
> +
> +/* USB host HS & FS */
> +#define cpu_has_uhp() (!cpu_is_at91sam9rl())
> +
> +/* USB device FS only */
> +#define cpu_has_udpfs() (!(cpu_is_at91sam9rl()))
Useless parentheses.
> +
> +
> static LIST_HEAD(clocks);
> static DEFINE_SPINLOCK(clk_lock);
>
> @@ -142,7 +161,7 @@ static struct clk utmi_clk = {
> };
> static struct clk uhpck = {
> .name = "uhpck",
> - .parent = &pllb,
> + /*.parent = ... we choose parent at runtime */
> .mode = pmc_sys_mode,
> };
>
> @@ -175,7 +194,12 @@ static struct clk __init *at91_css_to_cl
> case AT91_PMC_CSS_PLLA:
> return &plla;
> case AT91_PMC_CSS_PLLB:
> - return &pllb;
> + if (cpu_has_upll())
> + /* CSS_PLLB == CSS_UPLL */
> + return &utmi_clk;
> + else
> + if (cpu_has_pllb())
> + return &pllb;
Put "else if" on one line?
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2009-03-22 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 10:56 [RFC PATCH] AT91: manage clock by functionality instead of CPUs Nicolas Ferre
2009-03-22 11:57 ` Ville Syrjälä [this message]
2009-03-23 8:40 ` Nicolas Ferre
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=20090322115710.GV10127@sci.fi \
--to=syrjala@sci.fi \
--cc=david-b@pacbell.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=patrice.vilchez@atmel.com \
--cc=sedji.gaouaou@atmel.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