From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: horms@verge.net.au, linux-sh@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org
Cc: magnus.damm@gmail.com, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: shmobile: r8a7794: add USB PHY DT support
Date: Thu, 17 Sep 2015 02:15:58 +0300 [thread overview]
Message-ID: <55F9F82E.4000809@cogentembedded.com> (raw)
In-Reply-To: <1590842.9hQm6l1zli@wasted.cogentembedded.com>
Hello.
On 09/13/2015 01:50 AM, Sergei Shtylyov wrote:
> Define the R8A7794 generic part of the USB PHY device node. It is up to the
> board file to enable the device.
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> arch/arm/boot/dts/r8a7794.dtsi | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> Index: renesas/arch/arm/boot/dts/r8a7794.dtsi
> ===================================================================
> --- renesas.orig/arch/arm/boot/dts/r8a7794.dtsi
> +++ renesas/arch/arm/boot/dts/r8a7794.dtsi
> @@ -690,6 +690,25 @@
> 0x1000 0 0 2 &gic 0 113 IRQ_TYPE_LEVEL_HIGH>;
> };
>
> + usbphy: usb-phy@e6590100 {
> + compatible = "renesas,usb-phy-r8a7794";
> + reg = <0 0xe6590100 0 0x100>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + clocks = <&mstp7_clks R8A7794_CLK_HSUSB>;
> + clock-names = "usbhs";
Forgot to add "power-domains" prop here. :-(
MBR, Sergei
next prev parent reply other threads:[~2015-09-16 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 22:48 [PATCH 0/2] Add USB PHY device tree support for R8A7794/SILK board Sergei Shtylyov
2015-09-12 22:50 ` [PATCH 1/2] ARM: shmobile: r8a7794: add USB PHY DT support Sergei Shtylyov
2015-09-16 23:15 ` Sergei Shtylyov [this message]
2015-09-30 8:33 ` Simon Horman
2015-09-30 11:11 ` Sergei Shtylyov
2015-09-12 22:53 ` [PATCH 2/2] ARM: shmobile: silk: enable USB PHY Sergei Shtylyov
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=55F9F82E.4000809@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=horms@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).