From: david@lechnology.com (David Lechner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: davinci: psc-da830: fix USB0 48MHz PHY clock registration
Date: Mon, 7 May 2018 09:25:05 -0500 [thread overview]
Message-ID: <a06ddbc4-e257-ddcd-55c6-3f3a745b91e3@lechnology.com> (raw)
In-Reply-To: <20180507113457.4716-1-nsekhar@ti.com>
On 05/07/2018 06:34 AM, Sekhar Nori wrote:
> USB0 48MHz PHY clock registration fails on DA830 because the
> da8xx-cfgchip clock driver cannot get a reference to USB0
> LPSC clock.
>
> The USB0 LPSC needs to be enabled during PHY clock enable. Setup
> the clock lookup correctly to fix this.
>
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
> ---
> drivers/clk/davinci/psc-da830.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/davinci/psc-da830.c b/drivers/clk/davinci/psc-da830.c
> index f61abf5632ff..081b039fcb02 100644
> --- a/drivers/clk/davinci/psc-da830.c
> +++ b/drivers/clk/davinci/psc-da830.c
> @@ -55,7 +55,8 @@ const struct davinci_psc_init_data da830_psc0_init_data = {
> .psc_init = &da830_psc0_init,
> };
>
> -LPSC_CLKDEV2(usb0_clkdev, NULL, "musb-da8xx",
> +LPSC_CLKDEV3(usb0_clkdev, "fck", "da830-usb-phy-clks",
> + NULL, "musb-da8xx",
> NULL, "cppi41-dmaengine");
> LPSC_CLKDEV1(usb1_clkdev, NULL, "ohci-da8xx");
> /* REVISIT: gpio-davinci.c should be modified to drop con_id */
>
Reviewed-by: David Lechner <david@lechnology.com>
next prev parent reply other threads:[~2018-05-07 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 11:34 [PATCH] clk: davinci: psc-da830: fix USB0 48MHz PHY clock registration Sekhar Nori
2018-05-07 14:25 ` David Lechner [this message]
2018-05-15 22:34 ` Stephen Boyd
2018-05-16 5:14 ` Sekhar Nori
2018-05-18 6:47 ` Sekhar Nori
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=a06ddbc4-e257-ddcd-55c6-3f3a745b91e3@lechnology.com \
--to=david@lechnology.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).