From: andrew@aj.id.au (Andrew Jeffery)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] arm: dts: aspeed: Add Aspeed G4 USB Virtual Hub
Date: Mon, 16 Jul 2018 16:13:52 +0930 [thread overview]
Message-ID: <1531723432.1140807.1441877376.5CC2AA4C@webmail.messagingengine.com> (raw)
In-Reply-To: <de7411c67c0cd31e16de49642e78a5a3d5f3bedc.camel@kernel.crashing.org>
On Mon, 16 Jul 2018, at 16:10, Benjamin Herrenschmidt wrote:
> On Mon, 2018-07-16 at 15:04 +0930, Andrew Jeffery wrote:
> > On Fri, 29 Jun 2018, at 13:21, Benjamin Herrenschmidt wrote:
> > > This adds the (disabled by default) device node for the
> > > Aspeed virtual hub,a long with clocks and pinmux.
> > >
> > > Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > > ---
> > > arch/arm/boot/dts/aspeed-g4.dtsi | 10 ++++++++++
> > > 1 file changed, 10 insertions(+)
> > >
> > > diff --git a/arch/arm/boot/dts/aspeed-g4.dtsi b/arch/arm/boot/dts/aspeed-g4.dtsi
> > > index 1d7ffa9fdb11..54524564037c 100644
> > > --- a/arch/arm/boot/dts/aspeed-g4.dtsi
> > > +++ b/arch/arm/boot/dts/aspeed-g4.dtsi
> > > @@ -131,6 +131,16 @@
> > > */
> > > };
> > >
> > > + vhub: usb-vhub at 1e6a0000 {
> > > + compatible = "aspeed,ast2400-usb-vhub";
> > > + reg = <0x1e6a0000 0x300>;
> > > + interrupts = <5>;
> > > + clocks = <&syscon ASPEED_CLK_GATE_USBPORT1CLK>;
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&pinctrl_usb2d_default>;
> > > + status = "disabled";
> > > + };
> > > +
> >
> > These are all generic properties, so it's pretty clear what's going
> > on, but it seems there's no bindings document capturing the
> > compatible string? Not wanting to be a pain, but shouldn't we have
> > documented it?
>
> The driver went in at a time when I hadn't realized we documented
> bindings for devices using only standard properties these days. We can
> send a binding to Rob later.
Yep, I can't see it being controversial.
Acked-by: Andrew Jeffery <andrew@aj.id.au>
>
> Cheers,
> Ben.
>
> >
> > > apb {
> > > compatible = "simple-bus";
> > > #address-cells = <1>;
> > > --
> > > 2.17.1
> > >
next prev parent reply other threads:[~2018-07-16 6:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 3:50 [PATCH 0/7] arm: Aspeed DT & config updates for USB Benjamin Herrenschmidt
2018-06-29 3:51 ` [PATCH 1/7] arm: dts: aspeed: Add aspeed G4 USB pinmux Benjamin Herrenschmidt
2018-07-16 5:17 ` Andrew Jeffery
2018-06-29 3:51 ` [PATCH 2/7] arm: dts: aspeed: Add aspeed G5 USB host pinmux Benjamin Herrenschmidt
2018-07-16 5:23 ` Andrew Jeffery
2018-06-29 3:51 ` [PATCH 3/7] arm: dts: aspeed: Add Aspeed G4 USB Virtual Hub Benjamin Herrenschmidt
2018-07-16 5:34 ` Andrew Jeffery
2018-07-16 6:40 ` Benjamin Herrenschmidt
2018-07-16 6:43 ` Andrew Jeffery [this message]
2018-06-29 3:51 ` [PATCH 4/7] arm: dts: aspeed: Add Aspeed 54 " Benjamin Herrenschmidt
2018-07-16 5:36 ` Andrew Jeffery
2018-06-29 3:51 ` [PATCH 5/7] arm: configs: Add USB gadget to Aspeed G4 defconfig Benjamin Herrenschmidt
2018-07-16 5:37 ` Andrew Jeffery
2018-06-29 3:51 ` [PATCH 6/7] arm: configs: Add USB gadget to Aspeed G5 defconfig Benjamin Herrenschmidt
2018-07-16 5:38 ` Andrew Jeffery
2018-06-29 3:51 ` [PATCH 7/7] arm: dts: aspeed: Enable vhub on port A of AST2500 EVB Benjamin Herrenschmidt
2018-07-16 5:39 ` Andrew Jeffery
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=1531723432.1140807.1441877376.5CC2AA4C@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--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 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).