All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: SAM9G45 - add a separate clock entry for every single	TC block
Date: Fri, 03 Sep 2010 15:05:43 +0200	[thread overview]
Message-ID: <4C80F2A7.9040007@atmel.com> (raw)
In-Reply-To: <1283517093-12628-1-git-send-email-fg@emlix.com>

Le 03/09/2010 14:31, Fabian Godehardt :
> Without this patch you will not be able to register the first block
> because of the second association call on at91_add_device_tc().

Yes, I noticed that.

> Signed-off-by: Fabian Godehardt <fg@emlix.com>

Tell me if my little modification is ok for you. I will then sign it and
send it to Russell patch tracking system: what do you think about it?

> ---
>  arch/arm/mach-at91/at91sam9g45.c         |   12 +++++++++---
>  arch/arm/mach-at91/at91sam9g45_devices.c |    4 ++--
>  2 files changed, 11 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/arm/mach-at91/at91sam9g45.c b/arch/arm/mach-at91/at91sam9g45.c
> index 753c0d3..52ef2d6 100644
> --- a/arch/arm/mach-at91/at91sam9g45.c
> +++ b/arch/arm/mach-at91/at91sam9g45.c
> @@ -121,8 +121,13 @@ static struct clk ssc1_clk = {
>  	.pmc_mask	= 1 << AT91SAM9G45_ID_SSC1,
>  	.type		= CLK_TYPE_PERIPHERAL,
>  };
> -static struct clk tcb_clk = {
> -	.name		= "tcb_clk",
> +static struct clk tcb0_clk = {
> +	.name		= "tcb0_clk",
> +	.pmc_mask	= 1 << AT91SAM9G45_ID_TCB,
> +	.type		= CLK_TYPE_PERIPHERAL,
> +};
> +static struct clk tcb1_clk = {
> +	.name		= "tcb1_clk",
>  	.pmc_mask	= 1 << AT91SAM9G45_ID_TCB,
>  	.type		= CLK_TYPE_PERIPHERAL,

I prefer to add a "fake" clock that depend on the first one instead of
doubling the definition: like this:

/* One additional fake clock for second TC block */
static struct clk tcb1_clk = {
        .name           = "tcb1_clk",
        .pmc_mask       = 0,
        .type           = CLK_TYPE_PERIPHERAL,
        .parent         = &tcb0_clk,
};

This way we keep the single clock entry but we provide a fake entry for
registering the second TC block.


>  };
> @@ -208,7 +213,8 @@ static struct clk *periph_clocks[] __initdata = {
>  	&spi1_clk,
>  	&ssc0_clk,
>  	&ssc1_clk,
> -	&tcb_clk,
> +	&tcb0_clk,
> +	&tcb1_clk,
>  	&pwm_clk,
>  	&tsc_clk,
>  	&dma_clk,
> diff --git a/arch/arm/mach-at91/at91sam9g45_devices.c b/arch/arm/mach-at91/at91sam9g45_devices.c
> index 809114d..4822019 100644
> --- a/arch/arm/mach-at91/at91sam9g45_devices.c
> +++ b/arch/arm/mach-at91/at91sam9g45_devices.c
> @@ -835,9 +835,9 @@ static struct platform_device at91sam9g45_tcb1_device = {
>  static void __init at91_add_device_tc(void)
>  {
>  	/* this chip has one clock and irq for all six TC channels */
> -	at91_clock_associate("tcb_clk", &at91sam9g45_tcb0_device.dev, "t0_clk");
> +	at91_clock_associate("tcb0_clk", &at91sam9g45_tcb0_device.dev, "t0_clk");
>  	platform_device_register(&at91sam9g45_tcb0_device);
> -	at91_clock_associate("tcb_clk", &at91sam9g45_tcb1_device.dev, "t0_clk");
> +	at91_clock_associate("tcb1_clk", &at91sam9g45_tcb1_device.dev, "t0_clk");
>  	platform_device_register(&at91sam9g45_tcb1_device);
>  }
>  #else

Ok for other modifications,

Best regards,
-- 
Nicolas Ferre

  parent reply	other threads:[~2010-09-03 13:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 12:31 [PATCH] AT91: SAM9G45 - add a separate clock entry for every single TC block Fabian Godehardt
2010-09-03 13:05 ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-03 13:05 ` Nicolas Ferre [this message]
2010-09-03 16:38   ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-06  4:48   ` Fabian Godehardt
2010-09-06 11:23     ` Nicolas Ferre
2010-09-06 11:23       ` Nicolas Ferre
2010-09-06 21:07       ` avictor.za at gmail.com
2010-09-06 21:07         ` avictor.za
2010-09-07 19:42       ` avictor.za at gmail.com
2010-09-07 19:42         ` avictor.za
2010-09-08  9:00         ` Nicolas Ferre
2010-09-08  9:00           ` Nicolas Ferre
2010-09-08  9:50           ` Jean-Christophe PLAGNIOL-VILLARD
2010-09-08  9:50             ` Jean-Christophe PLAGNIOL-VILLARD

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=4C80F2A7.9040007@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 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.