public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	 linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: qcom: qcs6490-rb3gen2: Enable uPD720201 and GL3590
Date: Wed, 25 Mar 2026 21:40:58 -0500	[thread overview]
Message-ID: <acSZ8AqKC3hdaz2A@baldur> (raw)
In-Reply-To: <hrebrfsc4lcsrpk7thg72f7gdmi3btuiphdwh2ft7algej72xz@cijypbournvw>

On Wed, Mar 25, 2026 at 01:35:46AM +0200, Dmitry Baryshkov wrote:
> On Mon, Mar 23, 2026 at 09:32:39PM -0500, Bjorn Andersson wrote:
> > The QCS6490 Rb3Gen2 has a Renesas μPD720201 XHCI controller hanging off
> > the TC9563 PCIe switch, on this a Genesys Logic GL3590 USB hub provides
> > two USB Type-A ports and an ASIX AX88179 USB 3.0 Gigabit Ethernet
> > interface.
> > 
> > The Renesas chip is powered by two regulators controlled through PM7250B
> > GPIOs 1 and 4, and the power/reset pin is pulled down by PM8350C GPIO 4.
> > The Genesys chip power is always-on, but the reset pin is controlled
> > through TLMM GPIO 162.
> > 
> > Describe the Renesas chip on the PCIe bus, with supplies and reset, to
> > allow it to be brought out of reset and discovered. Then describe the
> > two peers of the USB hub, with its reset GPIO, to allow this to be
> > brought out of reset.
> > 
> > The USB Type-A connectors are not described, as they are in no regard
> > controlled by the operating system.
> > 
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> > ---
> > Dependencies has now landed, so this provides USB Type-A and Ethernet
> > support (when renesas_usb_fw.mem) is present.
> 
> Note, I initially applied the patch to the bit old -next (20260317) and
> I ended up with no PCIe host at all (bare -next would still show the
> PCIe host and the TC9563 bridge).
> 

Applied the patch to next-20260323 and tested again.

> 
> ANyway, does this actually work for you?

Yes, I booted with pcie_aspm=off I have functional ethernet and I can
plug/unplug a USB storage device and access the content on this.

> The hub is detected, but the USB bus is empty.

I've disconnected the USB stick again, so here's the output when only
ethernet is present.

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-pci-renesas/4p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-pci-renesas/4p, 5000M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M
        |__ Port 001: Dev 003, If 0, Class=Vendor Specific Class, Driver=ax88179_178a, 5000M

> I tried plugging in several devices (includin the
> powered USB hub) and they were completely ignored by the hub.
> 

The USB stick above was powered by the device, so that part is tested as
well. (And schematics shows VBUS is always present on the Type-A ports).

Regards,
Bjorn

> FWIW I tried both the the pcie_aspm=off and w/o it.
> 
> > Missing from the RFC/v1 description was the mentioning that unless I
> > pass "pcie_aspm=off" to the kernel, the Renesas controller fails with:
> > 
> >   xhci-pci-renesas 0001:04:00.0: Abort failed to stop command ring: -110
> 
> Interesting, it "worked" in my case, having everythign built in into the
> kernel.
> 
> > ---
> > Changes in v2:
> > - Waited for dependencies to land.
> > - Dropped "RFC".
> > - Link to v1: https://lore.kernel.org/r/20260212-rb3gen2-upd-gl3590-v1-1-18fb04bb32b0@oss.qualcomm.com
> > ---
> >  arch/arm64/boot/dts/qcom/qcs6490-rb3gen2.dts | 93 ++++++++++++++++++++++++++++
> >  1 file changed, 93 insertions(+)
> > 
> 
> -- 
> With best wishes
> Dmitry

  reply	other threads:[~2026-03-26  2:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24  2:32 [PATCH v2] arm64: dts: qcom: qcs6490-rb3gen2: Enable uPD720201 and GL3590 Bjorn Andersson
2026-03-24  9:37 ` Konrad Dybcio
2026-03-24  9:55   ` Krishna Kurapati
2026-03-24  9:38 ` Konrad Dybcio
2026-03-24 23:35 ` Dmitry Baryshkov
2026-03-26  2:40   ` Bjorn Andersson [this message]
2026-03-27 19:00     ` Dmitry Baryshkov

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=acSZ8AqKC3hdaz2A@baldur \
    --to=andersson@kernel.org \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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