From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91: sama5d: add the PWM clock
Date: Wed, 25 Sep 2013 09:18:11 +0200 [thread overview]
Message-ID: <52428E33.6010306@atmel.com> (raw)
In-Reply-To: <1380043832-26600-1-git-send-email-alexandre.belloni@free-electrons.com>
I modify the subject: s/sama5d/sama5d3/ and push it to our
at91-3.13-soc branch on:
https://github.com/at91linux/linux-at91/commits/at91-3.13-soc
With:
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Thanks, bye,
On 24/09/2013 19:30, Alexandre Belloni :
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> arch/arm/mach-at91/sama5d3.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm/mach-at91/sama5d3.c b/arch/arm/mach-at91/sama5d3.c
> index 4012797..8e43e8d 100644
> --- a/arch/arm/mach-at91/sama5d3.c
> +++ b/arch/arm/mach-at91/sama5d3.c
> @@ -241,6 +241,11 @@ static struct clk tdes_clk = {
> .pid = SAMA5D3_ID_TDES,
> .type = CLK_TYPE_PERIPHERAL,
> };
> +static struct clk pwm_clk = {
> + .name = "pwm_clk",
> + .pid = SAMA5D3_ID_PWM,
> + .type = CLK_TYPE_PERIPHERAL,
> +};
>
> static struct clk *periph_clocks[] __initdata = {
> &pioA_clk,
> @@ -281,6 +286,7 @@ static struct clk *periph_clocks[] __initdata = {
> &sha_clk,
> &aes_clk,
> &tdes_clk,
> + &pwm_clk,
> };
>
> static struct clk pck0 = {
> @@ -345,6 +351,7 @@ static struct clk_lookup periph_clocks_lookups[] = {
> CLKDEV_CON_DEV_ID("sha_clk", "f8034000.sha", &sha_clk),
> CLKDEV_CON_DEV_ID("aes_clk", "f8038000.aes", &aes_clk),
> CLKDEV_CON_DEV_ID("tdes_clk", "f803c000.tdes", &tdes_clk),
> + CLKDEV_CON_DEV_ID(NULL, "f002c000.pwm", &pwm_clk),
> };
>
> static void __init sama5d3_register_clocks(void)
>
--
Nicolas Ferre
prev parent reply other threads:[~2013-09-25 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 17:30 [PATCH] ARM: at91: sama5d: add the PWM clock Alexandre Belloni
2013-09-25 7:18 ` Nicolas Ferre [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=52428E33.6010306@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).