From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2][ 6/8] ARM: dts: i.MX35: Add USB support.
Date: Tue, 11 Mar 2014 23:13:15 +0300 [thread overview]
Message-ID: <531F6E5B.7070802@cogentembedded.com> (raw)
In-Reply-To: <1394535304-10240-6-git-send-email-denis@eukrea.com>
Hello.
On 03/11/2014 01:55 PM, Denis Carikli wrote:
> Signed-off-by: Denis Carikli <denis@eukrea.com>
> ---
> Changelog v1->v2:
> - The usbphy nodes were made to look like the ones in imx53.dtsi
> - The patch was rebased on top of the clock fixes commits.
> ---
> arch/arm/boot/dts/imx35.dtsi | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
> diff --git a/arch/arm/boot/dts/imx35.dtsi b/arch/arm/boot/dts/imx35.dtsi
> index 474a73d..b943123 100644
> --- a/arch/arm/boot/dts/imx35.dtsi
> +++ b/arch/arm/boot/dts/imx35.dtsi
> @@ -298,6 +298,7 @@
> interrupts = <37>;
> clocks = <&clks 73>;
> fsl,usbmisc = <&usbmisc 0>;
> + fsl,usbphy = <&usbphy0>;
Why use Freescale specific prop here, when there's de-facto standard
"usb-phy" already?
> @@ -307,6 +308,7 @@
> interrupts = <35>;
> clocks = <&clks 73>;
> fsl,usbmisc = <&usbmisc 1>;
> + fsl,usbphy = <&usbphy1>;
Likewise.
> @@ -355,4 +357,18 @@
> };
> };
> };
> +
> + usbphy {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "simple-bus";
> +
> + usbphy0: usbphy at 0 {
Why use the node name with the address part when you don't have "reg" prop?
Moreover, I suggest "usb-phy" instead to be more in line with ePAPR [1]
specified "ethernet-phy" device nodes.
[1] http://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.0.pdf
WBR, Sergei
next prev parent reply other threads:[~2014-03-11 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 10:54 [PATCH v2][ 1/8] ARM: dts: mx25: USB block requires only one clock Denis Carikli
2014-03-11 10:54 ` [PATCH v2][ 2/8] ARM: dts: mx35: " Denis Carikli
2014-03-11 10:54 ` [PATCH v2][ 3/8] usb: chipidea: usbmisc: Add USB Host support for i.MX25/i.MX35 CPUs Denis Carikli
2014-03-12 6:08 ` Peter Chen
2014-03-11 10:55 ` [PATCH v2][ 4/8] ARM: dts: imx25.dtsi: Fix USB support Denis Carikli
2014-03-11 11:58 ` Fabio Estevam
2014-03-11 20:14 ` Sergei Shtylyov
2014-03-11 10:55 ` [PATCH v2][ 5/8] ARM: dts: mbimxsd25 baseboard: Add " Denis Carikli
2014-03-11 10:55 ` [PATCH v2][ 6/8] ARM: dts: i.MX35: " Denis Carikli
2014-03-11 20:13 ` Sergei Shtylyov [this message]
2014-03-11 10:55 ` [PATCH v2][ 7/8] ARM: dts: mbimxsd35 baseboard: " Denis Carikli
2014-03-11 10:55 ` [PATCH v2][ 8/8] ARM: imx_v4_v5_defconfig: Enable drivers for i.MX25/i.MX35 " Denis Carikli
2014-03-11 11:37 ` Fabio Estevam
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=531F6E5B.7070802@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.