public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Wesley Cheng <quic_wcheng@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Wesley Cheng <wesley.cheng@oss.qualcomm.com>
Subject: Re: [PATCH RFT 3/3] arm64: dts: qcom: glymur-crd: Enable USB support
Date: Tue, 20 Jan 2026 13:31:35 +0100	[thread overview]
Message-ID: <8f3ea845-2f5a-42e1-b8c9-4e183c463e58@kernel.org> (raw)
In-Reply-To: <1299cddb-8205-47bc-89c4-98b4ddcd688c@oss.qualcomm.com>

On 20/01/2026 13:07, Pankaj Patil wrote:
> On 1/13/2026 6:03 PM, Abel Vesa wrote:
>> From: Wesley Cheng <wesley.cheng@oss.qualcomm.com>
>>
>> The Qualcomm Glymur Compute Reference Device comes with 3 Type-C ports,
>> one USB Type-A, and a fingerprint reader connected over USB. Each of these
>> 3 Type-C ports are connected to one of the USB combo PHYs and one of the
>> M31 eUSB2 PHYs. The Type-A is connected to the USB Multi-port controller
>> via one of the M31 eUSB2 PHYs and one combo PHY. The fingerprint reader
>> is connected to the USB_2 controller. All M31 eUSB2 PHYs have associated
>> eUSB2 to USB 2.0 repeaters, which are either part of SMB2360 PMICs or
>> dedicated NXP PTN3222.
>>
>> So enable all needed controllers, PHYs and repeaters, while describing
>> their supplies. Also describe the PMIC glink graph for Type-C connectors.
>>
>> Signed-off-by: Wesley Cheng <wesley.cheng@oss.qualcomm.com>
>> Co-developed-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
>> ---


Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content.

I went through entire pages of quoted text and found no relevant
answer... probably because it was deep hidden in these pages of
irrelevant quote.

Best regards,
Krzysztof

  reply	other threads:[~2026-01-20 12:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 12:33 [PATCH RFT 0/3] arm64: dts: qcom: glymur: Add USB support Abel Vesa
2026-01-13 12:33 ` [PATCH RFT 1/3] dt-bindings: usb: qcom,dwc3: Allow high-speed interrupt on Glymur, Hamoa and Milos Abel Vesa
2026-01-13 13:05   ` Konrad Dybcio
2026-01-15 18:51   ` Rob Herring (Arm)
2026-01-13 12:33 ` [PATCH RFT 2/3] arm64: dts: qcom: glymur: Add USB related nodes Abel Vesa
2026-01-13 13:13   ` Konrad Dybcio
2026-01-26 14:31     ` Abel Vesa
2026-01-26 14:44       ` Konrad Dybcio
2026-01-26 15:03         ` Abel Vesa
2026-01-27 11:41     ` Abel Vesa
2026-01-27 11:46       ` Konrad Dybcio
2026-01-27 22:26         ` Wesley Cheng
2026-01-28  9:38           ` Abel Vesa
2026-01-30 18:17             ` Wesley Cheng
2026-01-28  9:53           ` Konrad Dybcio
2026-01-31  0:11             ` Wesley Cheng
2026-02-02 12:35               ` Konrad Dybcio
2026-01-13 17:58   ` Dmitry Baryshkov
2026-01-13 12:33 ` [PATCH RFT 3/3] arm64: dts: qcom: glymur-crd: Enable USB support Abel Vesa
2026-01-13 18:02   ` Dmitry Baryshkov
2026-01-26 14:24     ` Abel Vesa
2026-01-26 17:52       ` Dmitry Baryshkov
2026-02-10 10:03         ` Abel Vesa
2026-01-20 12:07   ` Pankaj Patil
2026-01-20 12:31     ` Krzysztof Kozlowski [this message]
2026-01-20 12:35     ` Abel Vesa
2026-01-30 22:38   ` Jack Pham

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=8f3ea845-2f5a-42e1-b8c9-4e183c463e58@kernel.org \
    --to=krzk@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pankaj.patil@oss.qualcomm.com \
    --cc=quic_wcheng@quicinc.com \
    --cc=robh@kernel.org \
    --cc=wesley.cheng@oss.qualcomm.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