[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aa837beb-ef4e-43ec-b8fa-54a21df1202c@kernel.org>
Date: Thu, 6 Mar 2025 15:03:32 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Georg Gottleuber <g.gottleuber@...edocomputers.com>,
Georg Gottleuber <ggo@...edocomputers.com>,
Bjorn Andersson <andersson@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Konrad Dybcio
<konrad.dybcio@....qualcomm.com>, wse@...edocomputers.com,
cs@...edocomputers.com
Subject: Re: [PATCH] arm64: dts: qcom: Add device tree for TUXEDO Elite 14
Gen1
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
Powered by blists - more mailing lists