From: Krzysztof Kozlowski <krzk@kernel.org>
To: Georg Gottleuber <g.gottleuber@tuxedocomputers.com>,
Georg Gottleuber <ggo@tuxedocomputers.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
wse@tuxedocomputers.com, cs@tuxedocomputers.com
Subject: Re: [PATCH] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1
Date: Thu, 6 Mar 2025 15:03:32 +0100 [thread overview]
Message-ID: <aa837beb-ef4e-43ec-b8fa-54a21df1202c@kernel.org> (raw)
In-Reply-To: <d98ad83e-6479-4453-bd1d-4f3703b0dad2@tuxedocomputers.com>
On 06/03/2025 14:56, Georg Gottleuber wrote:
>
>> ...
>>
>>> +
>>> + eusb3_repeater: redriver@47 {
>>> + compatible = "nxp,ptn3222";
>>> + reg = <0x47>;
>>> + #phy-cells = <0>;
>>> +
>>> + vdd1v8-supply = <&vreg_l4b_1p8>;
>>> + vdd3v3-supply = <&vreg_l13b_3p0>;
>>> +
>>> + reset-gpios = <&tlmm 124 GPIO_ACTIVE_LOW>;
>>> +
>>> + pinctrl-0 = <&eusb3_reset_n>;
>>> + pinctrl-names = "default";
>>
>> No graph? Isn't it needed?
>
> What do you mean by ‘no graph’?
ports connecting this within USB graph between controller and connector.
Just like other devices with redriver.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-06 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 12:25 [PATCH] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1 Georg Gottleuber
2025-03-06 12:41 ` Krzysztof Kozlowski
2025-03-06 13:56 ` Georg Gottleuber
2025-03-06 14:03 ` Krzysztof Kozlowski [this message]
2025-03-06 16:45 ` Dmitry Baryshkov
2025-03-06 12:50 ` Konrad Dybcio
2025-03-06 15:22 ` Georg Gottleuber
2025-03-06 18:15 ` Konrad Dybcio
2025-03-06 19:30 ` Michael Srba
2025-03-07 6:45 ` Dmitry Baryshkov
2025-03-18 15:24 ` Georg Gottleuber
2025-03-18 15:57 ` Konrad Dybcio
2025-03-18 17:17 ` Rob Clark
2025-03-18 21:36 ` Dmitry Baryshkov
2025-03-21 15:49 ` Ettore Chimenti
2025-03-21 15:51 ` Dmitry Baryshkov
2025-03-28 11:34 ` Georg Gottleuber
2025-03-28 12:42 ` 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=aa837beb-ef4e-43ec-b8fa-54a21df1202c@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cs@tuxedocomputers.com \
--cc=devicetree@vger.kernel.org \
--cc=g.gottleuber@tuxedocomputers.com \
--cc=ggo@tuxedocomputers.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wse@tuxedocomputers.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