From: Alexander Sverdlin <alexander.sverdlin@gmail•com>
To: Andre Przywara <andre.przywara@arm•com>, linux-sunxi@lists•linux.dev
Cc: Rob Herring <robh@kernel•org>,
Krzysztof Kozlowski <krzk+dt@kernel•org>,
Conor Dooley <conor+dt@kernel•org>,
Chen-Yu Tsai <wens@kernel•org>,
Jernej Skrabec <jernej.skrabec@gmail•com>,
Samuel Holland <samuel@sholland•org>,
devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: allwinner: A133: add support for Baijie Helper A133 board
Date: Mon, 18 May 2026 13:29:51 +0200 [thread overview]
Message-ID: <6d8659f393e0bb4f0805107a17e306422982247c.camel@gmail.com> (raw)
In-Reply-To: <256b1cd8-b143-4f71-91cc-8513be04ce4c@arm.com>
Hi Andre,
On Mon, 2026-05-18 at 13:16 +0200, Andre Przywara wrote:
> > > And anyway, I see a *dual* USB-A socket on the pictures online, in
> > > addition to the USB-OTG port. So where does the third USB come from? The
> > > A133 only supports one host USB port plus the one OTG port. So is there
> > > an USB hub chip on the board?
> >
> > There are two hubs, one on each usbphy. OTG side hub is even bus-powered,
>
> What do you mean with OTG side hub, exactly? Is there a hub on USB0? How
> does this work, then?
the upstream port of this hub is wired to the USB-C connector, one port has
CH340E USB-UART on it for the console, the other port goes to the SoC usbphy 0.
So it would be "peripheral" only, I suppose.
--
Alexander Sverdlin.
next prev parent reply other threads:[~2026-05-18 11:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 20:16 [PATCH v2 0/3] Add support for Baijie Helper A133 board Alexander Sverdlin
2026-05-10 20:16 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Shenzhen Baijie Technology Co., Ltd Alexander Sverdlin
2026-05-18 11:36 ` Paul Kocialkowski
2026-05-10 20:16 ` [PATCH v2 2/3] dt-bindings: arm: sunxi: Add Baijie HelperBoard A133 compatible Alexander Sverdlin
2026-05-11 16:08 ` Conor Dooley
2026-05-11 16:18 ` Alexander Sverdlin
2026-05-11 16:34 ` Conor Dooley
2026-05-18 11:35 ` Paul Kocialkowski
2026-05-10 20:16 ` [PATCH v2 3/3] arm64: dts: allwinner: A133: add support for Baijie Helper A133 board Alexander Sverdlin
2026-05-11 11:44 ` Andre Przywara
2026-05-17 20:38 ` Alexander Sverdlin
2026-05-18 3:30 ` Chen-Yu Tsai
2026-05-18 10:12 ` Alexander Sverdlin
2026-05-18 11:16 ` Andre Przywara
2026-05-18 11:29 ` Alexander Sverdlin [this message]
2026-05-18 11:54 ` Paul Kocialkowski
2026-05-18 12:50 ` Andre Przywara
2026-05-18 14:47 ` Chen-Yu Tsai
2026-05-18 14:51 ` Alexander Sverdlin
2026-05-18 11:52 ` Paul Kocialkowski
2026-05-18 12:09 ` Alexander Sverdlin
2026-05-18 14:14 ` Paul Kocialkowski
2026-05-18 14:40 ` Alexander Sverdlin
2026-05-18 14:56 ` Paul Kocialkowski
2026-05-18 15:04 ` Alexander Sverdlin
2026-05-18 21:23 ` Andre Przywara
2026-05-18 20:05 ` Alexander Sverdlin
2026-05-18 21:46 ` Paul Kocialkowski
2026-05-19 3:33 ` Chen-Yu Tsai
2026-05-18 21:54 ` Andre Przywara
2026-06-04 22:37 ` Alexander Sverdlin
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=6d8659f393e0bb4f0805107a17e306422982247c.camel@gmail.com \
--to=alexander.sverdlin@gmail$(echo .)com \
--cc=andre.przywara@arm$(echo .)com \
--cc=conor+dt@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=jernej.skrabec@gmail$(echo .)com \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-sunxi@lists$(echo .)linux.dev \
--cc=robh@kernel$(echo .)org \
--cc=samuel@sholland$(echo .)org \
--cc=wens@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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