From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Cc: devicetree <devicetree@vger.kernel.org>,
Joel Stanley <joel.stanley@au1.ibm.com>,
linux-aspeed@lists.ozlabs.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dts: ARM: Add Aspeed virtual hub to SoC templates
Date: Wed, 28 Mar 2018 12:03:51 +1100 [thread overview]
Message-ID: <1522199031.7364.82.camel@kernel.crashing.org> (raw)
In-Reply-To: <CACPK8XdgoNLr3m_bp_Y+Cu6pNx5f0xJ5BwWL8svZPgM-YNQA8w@mail.gmail.com>
On Wed, 2018-03-28 at 11:00 +1030, Joel Stanley wrote:
> Hi Ben,
>
> On 12 January 2018 at 17:21, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > We don't yet enable it in any of the boards
> >
> > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>
> This one slipped through the cracks. Is it still the latest version?
I was going to re-submit it after the driver itself is in.
>
> Cheers,
>
> Joel
>
> > ---
> > arch/arm/boot/dts/aspeed-g4.dtsi | 8 ++++++++
> > arch/arm/boot/dts/aspeed-g5.dtsi | 13 +++++++++++++
> > 2 files changed, 21 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/aspeed-g4.dtsi b/arch/arm/boot/dts/aspeed-g4.dtsi
> > index e55f2ad5de59..743b79014d3d 100644
> > --- a/arch/arm/boot/dts/aspeed-g4.dtsi
> > +++ b/arch/arm/boot/dts/aspeed-g4.dtsi
> > @@ -120,6 +120,14 @@
> > status = "disabled";
> > };
> >
> > + vhub: usb-vhub@1e6a0000 {
> > + compatible = "aspeed,ast2400-usb-vhub";
> > + reg = <0x1e6a0000 0x300>;
> > + interrupts = <5>;
> > + clocks = <&syscon ASPEED_CLK_GATE_USBPORT1CLK>;
> > + status = "disabled";
> > + };
> > +
> > apb {
> > compatible = "simple-bus";
> > #address-cells = <1>;
> > diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
> > index 655258edee24..e50d7f3e18a0 100644
> > --- a/arch/arm/boot/dts/aspeed-g5.dtsi
> > +++ b/arch/arm/boot/dts/aspeed-g5.dtsi
> > @@ -163,6 +163,14 @@
> > status = "disabled";
> > };
> >
> > + vhub: usb-vhub@1e6a0000 {
> > + compatible = "aspeed,ast2500-usb-vhub";
> > + reg = <0x1e6a0000 0x300>;
> > + interrupts = <5>;
> > + clocks = <&syscon ASPEED_CLK_GATE_USBPORT1CLK>;
> > + status = "disabled";
> > + };
> > +
> > apb {
> > compatible = "simple-bus";
> > #address-cells = <1>;
> > @@ -1388,6 +1396,11 @@
> > groups = "USB2AH";
> > };
> >
> > + pinctrl_usb2ad_default: usb2ad_default {
> > + function = "USB2AD";
> > + groups = "USB2AD";
> > + };
> > +
> > pinctrl_usb11bhid_default: usb11bhid_default {
> > function = "USB11BHID";
> > groups = "USB11BHID";
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-03-28 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 6:51 [PATCH] dts: ARM: Add Aspeed virtual hub to SoC templates Benjamin Herrenschmidt
2018-03-28 0:30 ` Joel Stanley
2018-03-28 1:03 ` Benjamin Herrenschmidt [this message]
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=1522199031.7364.82.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=joel.stanley@au1.ibm.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.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).