devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Feng Kan <fkan@apm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>, patches <patches@apm.com>
Cc: Feng Kan <fkan@apm.com>, Bao Truong <btruong@apm.com>
Subject: Re: [PATCH 1/7] arm64: dts: Add APM X-Gene USB 2.0 DTS node
Date: Thu, 23 Oct 2014 18:26:20 -0700	[thread overview]
Message-ID: <CAL85gmBQ9CsSwu0LbbCMtCuiEqFGAy4F-VfPxQMBqDdNwFFABg@mail.gmail.com> (raw)
In-Reply-To: <1414113862-15067-2-git-send-email-fkan@apm.com>

Sorry, messed up the title will resend

On Thu, Oct 23, 2014 at 6:24 PM, Feng Kan <fkan@apm.com> wrote:
> This parch adds the device tree nodes for APM X-Gnene USB host controller.
> Since X-Gene SOC supports maximum 2 USB ports, 2 dts node are added.
>
> Signed-off-by: Bao Truong <btruong@apm.com>
> Signed-off-by: Feng Kan <fkan@apm.com>
> ---
>  arch/arm64/boot/dts/apm-storm.dtsi | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/apm-storm.dtsi b/arch/arm64/boot/dts/apm-storm.dtsi
> index 3eef74b..a80f2fa 100644
> --- a/arch/arm64/boot/dts/apm-storm.dtsi
> +++ b/arch/arm64/boot/dts/apm-storm.dtsi
> @@ -587,6 +587,20 @@
>                         phy-names = "sata-phy";
>                 };
>
> +               usb0: dwusb@19000000 {
> +                       status = "disabled";
> +                       compatible = "xhci-platform";
> +                       reg =  <0x0 0x19000000 0x0 0x100000>;
> +                       interrupts = <0x0 0x89 0x4>;
> +               };
> +
> +               usb1: dwusb@19800000 {
> +                       status = "disabled";
> +                       compatible = "xhci-platform";
> +                       reg =  <0x0 0x19800000 0x0 0x100000>;
> +                       interrupts = <0x0 0x8a 0x4>;
> +               };
> +
>                 rtc: rtc@10510000 {
>                         compatible = "apm,xgene-rtc";
>                         reg = <0x0 0x10510000 0x0 0x400>;
> --
> 1.9.1
>

  reply	other threads:[~2014-10-24  1:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  1:24 [PATCH 0/7] APM X-Gene SoC platform device tree cleanup Feng Kan
2014-10-24  1:24 ` [PATCH 1/7] arm64: dts: Add APM X-Gene USB 2.0 DTS node Feng Kan
2014-10-24  1:26   ` Feng Kan [this message]
2014-10-24  1:24 ` [PATCH 2/7] Documentation: arm64: add SCU dts binding documentation to linux kernel Feng Kan
2014-10-24  1:24 ` [PATCH 3/7] arm64: dts: Add X-Gene reboot driver dts node Feng Kan
2014-10-24  1:24 ` [PATCH 4/7] arm64: dts: Add Designware GPIO dts binding to APM X-Gene platform Feng Kan
2014-10-24  1:24 ` [PATCH 5/7] arm64: dts: Add APM X-Gene SoC GFC GPIO controller DTS entries Feng Kan
2014-10-24  1:24 ` [PATCH 6/7] Documentation: arm: pmu: Add Potenza PMU binding Feng Kan
2014-10-24  1:24 ` [PATCH 7/7] arm64: dts: Add PMU node for APM X-Gene Storm SOC Feng Kan

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=CAL85gmBQ9CsSwu0LbbCMtCuiEqFGAy4F-VfPxQMBqDdNwFFABg@mail.gmail.com \
    --to=fkan@apm.com \
    --cc=btruong@apm.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@apm.com \
    /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).