From: tremyfr@gmail.com (Philippe Reynes)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] usb issue on imx27: 3 clocks are needed
Date: Sat, 16 Aug 2014 17:38:30 +0200 [thread overview]
Message-ID: <53EF7AF6.2000405@gmail.com> (raw)
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.
Regards,
Philippe and Gwenhael
WARNING: multiple messages have this Message-ID (diff)
From: Philippe Reynes <tremyfr@gmail.com>
To: Linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
shawn.guo@freescale.com, Peter.Chen@freescale.com
Cc: gwenhael.goavec-merou@trabucayre.com
Subject: [RFC] usb issue on imx27: 3 clocks are needed
Date: Sat, 16 Aug 2014 17:38:30 +0200 [thread overview]
Message-ID: <53EF7AF6.2000405@gmail.com> (raw)
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.
Regards,
Philippe and Gwenhael
next reply other threads:[~2014-08-16 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 15:38 Philippe Reynes [this message]
2014-08-16 15:38 ` [RFC] usb issue on imx27: 3 clocks are needed 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
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=53EF7AF6.2000405@gmail.com \
--to=tremyfr@gmail.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.