From: gwen@trabucayre.com (gwenhael.goavec)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] usb issue on imx27: 3 clocks are needed
Date: Tue, 19 Aug 2014 10:47:46 +0200 [thread overview]
Message-ID: <20140819104746.4a8f323c@x230> (raw)
In-Reply-To: <20140819001816.GC2928@peterchendt>
On Tue, 19 Aug 2014 08:18:17 +0800
Peter Chen <peter.chen@freescale.com> wrote:
> On Mon, Aug 18, 2014 at 01:49:03PM +0200, gwenhael.goavec wrote:
> > On Mon, 18 Aug 2014 10:35:53 +0000
> > Peter Chen <Peter.Chen@freescale.com> wrote:
> >
> > >
> > > > On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
> > > > > On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and
> > > > > > usb_div) but the current chipidea driver implementation, and
> > > > > > devicetree, provides only ipg and ahb. Consequently, if the
> > > > > > bootloader don't enable the last one, the kernel will crash.
> > > > > >
> > > > > > Our approach/idea is to add a second, optionnal, clock in
> > > > > > ci_hdrc_imx.c with 'per' name in devicetree and to add clock name
> > > > 'main_clk' for mandatory clock.
> > > > > > This approach it correct? Or an other approach seems better?
> > > > > > Thank you very much for your point of view.
> > > > > >
> > > > >
> > > > > It is ok for me to have ipg, ahb and per clocks at driver, but how can
> > > > > you maintain DT consistent?
> > > >
> > > > Adding new clock as optional one will just maintain the DT compatibility.
> > > >
> > >
> > > How to handle node_usb_soc1's clock which is without clk name to consistent with three
> > > clocks for node_usb_soc2 at driver? Except for adding some platform judge code at
> > > driver, do you have other solutions?
> > >
> > > node_usb_soc1: {
> > > clocks = <&clks IMX6_CLK_USBOH3>;
> > > };
> > >
> > > node_usb_soc2: {
> > > clocks = <&clks IMX27_CLK_USBIPG>, <&clks IMX27_CLK_USBOH3>, <&clks IMX27_CLK_USBPER>;
> > > clock-names = "ipg", "ahb", "per";
> > > };
> > >
> > > Peter
> > > --
> >
> > Our idea is something like this :
> > node_usb_soc: {
> > clocks = <&clks IMX27_CLK_USBxxx>;
> > clock-names = "main_clk";
> > };
> > for all CPUs
> >
> > and
> > node_usb_imx27: {
> > clocks = <&clks IMX27_CLK_USB_IPG_GATE>,
> > <&clks IMX27_CLK_USB_DIV>;
> > clock-names = "main_clk", "per";
> > };
> >
> > For imx27 and CPUs with the need of more than one clock.
> >
>
> Just like Shawn said, it breaks DT compatibility, how the old dtb works
> with newer version kernel after you change.
>
New dtsi must be updated according to the clock name and to avoid breaking old
dtb, i think the best way is to to do something like :
data->clk = devm_clk_get(&pdev->dev, "main_clk");
if (IS_ERR(data->clk)) {
/* DT compatibility */
data->clk = devm_clk_get(&pdev->dev, NULL);
if (IS_ERR(data->clk)) {
dev_err(&pdev->dev,
"Failed to get main clock, err=%ld\n",
PTR_ERR(data->clk));
return PTR_ERR(data->clk);
}
}
Gwenhael
>
> > The last clock (ie ahb) is handled by usbmisc.c and if "per" clock is not
> > present in the dtsi chipidea will not fails, just setting data->per_clk = NULL
> > for prepare/unprepare.
> >
> > Gwenhael
>
> --
> Best Regards,
> Peter Chen
WARNING: multiple messages have this Message-ID (diff)
From: "gwenhael.goavec" <gwen@trabucayre.com>
To: Peter Chen <peter.chen@freescale.com>
Cc: Shawn Guo <Shawn.Guo@freescale.com>,
Philippe Reynes <tremyfr@gmail.com>,
"Linux-kernel@vger.kernel.org" <Linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] usb issue on imx27: 3 clocks are needed
Date: Tue, 19 Aug 2014 10:47:46 +0200 [thread overview]
Message-ID: <20140819104746.4a8f323c@x230> (raw)
In-Reply-To: <20140819001816.GC2928@peterchendt>
On Tue, 19 Aug 2014 08:18:17 +0800
Peter Chen <peter.chen@freescale.com> wrote:
> On Mon, Aug 18, 2014 at 01:49:03PM +0200, gwenhael.goavec wrote:
> > On Mon, 18 Aug 2014 10:35:53 +0000
> > Peter Chen <Peter.Chen@freescale.com> wrote:
> >
> > >
> > > > On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
> > > > > On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and
> > > > > > usb_div) but the current chipidea driver implementation, and
> > > > > > devicetree, provides only ipg and ahb. Consequently, if the
> > > > > > bootloader don't enable the last one, the kernel will crash.
> > > > > >
> > > > > > Our approach/idea is to add a second, optionnal, clock in
> > > > > > ci_hdrc_imx.c with 'per' name in devicetree and to add clock name
> > > > 'main_clk' for mandatory clock.
> > > > > > This approach it correct? Or an other approach seems better?
> > > > > > Thank you very much for your point of view.
> > > > > >
> > > > >
> > > > > It is ok for me to have ipg, ahb and per clocks at driver, but how can
> > > > > you maintain DT consistent?
> > > >
> > > > Adding new clock as optional one will just maintain the DT compatibility.
> > > >
> > >
> > > How to handle node_usb_soc1's clock which is without clk name to consistent with three
> > > clocks for node_usb_soc2 at driver? Except for adding some platform judge code at
> > > driver, do you have other solutions?
> > >
> > > node_usb_soc1: {
> > > clocks = <&clks IMX6_CLK_USBOH3>;
> > > };
> > >
> > > node_usb_soc2: {
> > > clocks = <&clks IMX27_CLK_USBIPG>, <&clks IMX27_CLK_USBOH3>, <&clks IMX27_CLK_USBPER>;
> > > clock-names = "ipg", "ahb", "per";
> > > };
> > >
> > > Peter
> > > --
> >
> > Our idea is something like this :
> > node_usb_soc: {
> > clocks = <&clks IMX27_CLK_USBxxx>;
> > clock-names = "main_clk";
> > };
> > for all CPUs
> >
> > and
> > node_usb_imx27: {
> > clocks = <&clks IMX27_CLK_USB_IPG_GATE>,
> > <&clks IMX27_CLK_USB_DIV>;
> > clock-names = "main_clk", "per";
> > };
> >
> > For imx27 and CPUs with the need of more than one clock.
> >
>
> Just like Shawn said, it breaks DT compatibility, how the old dtb works
> with newer version kernel after you change.
>
New dtsi must be updated according to the clock name and to avoid breaking old
dtb, i think the best way is to to do something like :
data->clk = devm_clk_get(&pdev->dev, "main_clk");
if (IS_ERR(data->clk)) {
/* DT compatibility */
data->clk = devm_clk_get(&pdev->dev, NULL);
if (IS_ERR(data->clk)) {
dev_err(&pdev->dev,
"Failed to get main clock, err=%ld\n",
PTR_ERR(data->clk));
return PTR_ERR(data->clk);
}
}
Gwenhael
>
> > The last clock (ie ahb) is handled by usbmisc.c and if "per" clock is not
> > present in the dtsi chipidea will not fails, just setting data->per_clk = NULL
> > for prepare/unprepare.
> >
> > Gwenhael
>
> --
> Best Regards,
> Peter Chen
next prev parent reply other threads:[~2014-08-19 8:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 15:38 [RFC] usb issue on imx27: 3 clocks are needed Philippe Reynes
2014-08-16 15:38 ` Philippe Reynes
2014-08-16 16:01 ` Fabio Estevam
2014-08-16 16:01 ` Fabio Estevam
2014-08-16 16:22 ` Philippe Reynes
2014-08-16 16:22 ` Philippe Reynes
2014-08-18 9:00 ` Peter Chen
2014-08-18 9:00 ` Peter Chen
2014-08-18 9:26 ` Shawn Guo
2014-08-18 9:26 ` Shawn Guo
2014-08-18 10:35 ` Peter Chen
2014-08-18 10:35 ` Peter Chen
2014-08-18 11:48 ` Shawn Guo
2014-08-18 11:48 ` Shawn Guo
2014-08-18 11:49 ` gwenhael.goavec
2014-08-18 11:49 ` gwenhael.goavec
2014-08-19 0:18 ` Peter Chen
2014-08-19 8:47 ` gwenhael.goavec [this message]
2014-08-19 8:47 ` gwenhael.goavec
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=20140819104746.4a8f323c@x230 \
--to=gwen@trabucayre.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.