From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 03/10] ARM: shmobile: r8a7779: add USB EHCI clock support
Date: Wed, 13 Mar 2013 23:09:17 +0000 [thread overview]
Message-ID: <5141156C.4010909@cogentembedded.com> (raw)
In-Reply-To: <1352446165-19298-4-git-send-email-horms@verge.net.au>
Hello.
On 11/09/2012 10:29 AM, Simon Horman wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> ehci-platform driver require these clocks
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Signed-off-by: Simon Horman <horms@verge.net.au>
> ---
> arch/arm/mach-shmobile/clock-r8a7779.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/mach-shmobile/clock-r8a7779.c b/arch/arm/mach-shmobile/clock-r8a7779.c
> index 24f5a84..4ba4e3c 100644
> --- a/arch/arm/mach-shmobile/clock-r8a7779.c
> +++ b/arch/arm/mach-shmobile/clock-r8a7779.c
[...]
> @@ -153,6 +156,8 @@ static struct clk_lookup lookups[] = {
> CLKDEV_CON_ID("peripheral_clk", &div4_clks[DIV4_P]),
>
> /* MSTP32 clocks */
> + CLKDEV_DEV_ID("ehci-platform.1", &mstp_clks[MSTP101]), /* USB EHCI port2 */
> + CLKDEV_DEV_ID("ehci-platform.0", &mstp_clks[MSTP100]), /* USB EHCI port0/1 */
But how are those used? I don't see clk API support in ehci-platform.c.
Are they used via runtime PM? I'm just not familiar enough with it...
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/10] ARM: shmobile: r8a7779: add USB EHCI clock support
Date: Thu, 14 Mar 2013 03:10:20 +0300 [thread overview]
Message-ID: <5141156C.4010909@cogentembedded.com> (raw)
In-Reply-To: <1352446165-19298-4-git-send-email-horms@verge.net.au>
Hello.
On 11/09/2012 10:29 AM, Simon Horman wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> ehci-platform driver require these clocks
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Signed-off-by: Simon Horman <horms@verge.net.au>
> ---
> arch/arm/mach-shmobile/clock-r8a7779.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm/mach-shmobile/clock-r8a7779.c b/arch/arm/mach-shmobile/clock-r8a7779.c
> index 24f5a84..4ba4e3c 100644
> --- a/arch/arm/mach-shmobile/clock-r8a7779.c
> +++ b/arch/arm/mach-shmobile/clock-r8a7779.c
[...]
> @@ -153,6 +156,8 @@ static struct clk_lookup lookups[] = {
> CLKDEV_CON_ID("peripheral_clk", &div4_clks[DIV4_P]),
>
> /* MSTP32 clocks */
> + CLKDEV_DEV_ID("ehci-platform.1", &mstp_clks[MSTP101]), /* USB EHCI port2 */
> + CLKDEV_DEV_ID("ehci-platform.0", &mstp_clks[MSTP100]), /* USB EHCI port0/1 */
But how are those used? I don't see clk API support in ehci-platform.c.
Are they used via runtime PM? I'm just not familiar enough with it...
WBR, Sergei
next prev parent reply other threads:[~2013-03-13 23:09 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 7:29 [GIT PULL v2] Renesas ARM-based SoC for v3.8 #2 Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 01/10] ARM: shmobile: r8a7779: PFC rename PENCx -> USB_PENCx Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 02/10] ARM: shmobile: r8a7740: add USB24 clock explain Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 03/10] ARM: shmobile: r8a7779: add USB EHCI clock support Simon Horman
2012-11-09 7:29 ` Simon Horman
2013-03-13 23:09 ` Sergei Shtylyov [this message]
2013-03-14 0:10 ` Sergei Shtylyov
2013-03-14 0:57 ` Kuninori Morimoto
2013-03-14 0:57 ` Kuninori Morimoto
2012-11-09 7:29 ` [PATCH 04/10] ARM: shmobile: r8a7779: add USB OHCI " Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 05/10] sh: clkfwk: add sh_clk_fsidiv_register() Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-12 22:43 ` Arnd Bergmann
2012-11-12 22:43 ` Arnd Bergmann
2012-11-13 0:33 ` [PATCH] sh: clkfwk: fixup unsed variable warning Kuninori Morimoto
2012-11-13 0:33 ` Kuninori Morimoto
2012-11-09 7:29 ` [PATCH 06/10] ARM: shmobile: sh7372: sh7372_fsidivX_clk become non-global Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 07/10] ARM: shmobile: sh7372: use sh_clk_fsidiv_register() for FSI-DIV clocks Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 08/10] ARM: shmobile: r8a7740: add FSI-DVI clocks Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 09/10] ARM: shmobile: add fsi external clock on r8a7740 Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-09 7:29 ` [PATCH 10/10] ARM: shmobile: add fsi external clock sh7372 Simon Horman
2012-11-09 7:29 ` Simon Horman
2012-11-12 20:49 ` [GIT PULL v2] Renesas ARM-based SoC for v3.8 #2 Arnd Bergmann
2012-11-12 20:49 ` Arnd Bergmann
2013-01-25 3:55 ` [GIT PULL v2] Renesas ARM-based SoC for v3.9 Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 01/15] ARM: shmobile: Remove duplicate inclusion of dma-mapping.h in setup-r8a7740.c Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 02/15] ARM: shmobile: r8a7740: add TMU timer support Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 03/15] ARM: shmobile: sh73a0: fixup div4_clks bitmap Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 04/15] ARM: mach-shmobile: sh73a0 external IRQ wake update Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 05/15] ARM: sh7372: add clock lookup entries for DT-based devices Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 06/15] ARM: sh7372: fix cache clean / invalidate order Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 07/15] ARM: shmobile: add function declarations for sh7372 DT helper functions Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 08/15] ARM: shmobile: sh73a0: Add CPU sleep suspend Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 09/15] ARM: shmobile: r8a7740: " Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 10/15] ARM: SH-Mobile: sh73a0: Secondary CPUs handle own SCU flags Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 11/15] ARM: SH-Mobile: sh73a0: Add CPU Hotplug Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 12/15] ARM: mach-shmobile: sh73a0: Allow initialisation of GIC by DT Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 10:22 ` Mark Rutland
2013-01-25 10:22 ` Mark Rutland
2013-01-28 0:48 ` Simon Horman
2013-01-28 0:48 ` Simon Horman
2013-01-28 10:59 ` Mark Rutland
2013-01-28 10:59 ` Mark Rutland
2013-01-29 0:22 ` Simon Horman
2013-01-29 0:22 ` Simon Horman
2013-01-25 3:55 ` [PATCH 13/15] ARM: mach-shmobile: sh73a0: Minimal setup using DT Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 14/15] ARM: mach-shmobile: sh73a0: Initialise MMCIF " Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-25 3:55 ` [PATCH 15/15] ARM: shmobile: r8a7779: scif .irqs used SCIx_IRQ_MUXED() Simon Horman
2013-01-25 3:55 ` Simon Horman
2013-01-29 17:11 ` [GIT PULL v2] Renesas ARM-based SoC for v3.9 Olof Johansson
2013-01-29 17:11 ` Olof Johansson
2013-01-30 2:18 ` Simon Horman
2013-01-30 2:18 ` Simon Horman
2013-01-31 6:39 ` Simon Horman
2013-01-31 6:39 ` Simon Horman
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=5141156C.4010909@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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.