mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Georg Gottleuber <g.gottleuber@tuxedocomputers.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	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 14:56:09 +0100	[thread overview]
Message-ID: <d98ad83e-6479-4453-bd1d-4f3703b0dad2@tuxedocomputers.com> (raw)
In-Reply-To: <75c17309-3072-4321-ab15-69d60190f2f7@kernel.org>



Am 06.03.25 um 13:41 schrieb Krzysztof Kozlowski:
...
> 
> Please run scripts/checkpatch.pl and fix reported warnings. After that,
> run also `scripts/checkpatch.pl --strict` and (probably) fix more
> warnings. Some warnings can be ignored, especially from --strict run,
> but the code here looks like it needs a fix. Feel free to get in touch
> if the warning is not clear.
> 
> It does not look like you tested the DTS against bindings. Please run
> `make dtbs_check W=1` (see
> Documentation/devicetree/bindings/writing-schema.rst or
> https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
> for instructions).
> Maybe you need to update your dtschema and yamllint. Don't rely on
> distro packages for dtschema and be sure you are using the latest
> released dtschema.

Thank you for the advice and the offer to answer further questions.
Didn't know that dtb_check exists.

> ...
> 
>> +
>> +       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’?

>> +       };
>> +
>> +       eusb5_repeater: redriver@43 {
>> +               compatible = "nxp,ptn3222";
>> +               reg = <0x43>;
>> +               #phy-cells = <0>;
>> +
>> +               vdd1v8-supply = <&vreg_l4b_1p8>;
>> +               vdd3v3-supply = <&vreg_l13b_3p0>;
>> +
>> +               reset-gpios = <&tlmm 184 GPIO_ACTIVE_LOW>;
>> +
>> +               pinctrl-0 = <&eusb6_reset_n>;
>> +               pinctrl-names = "default";
>> +       };
>> +
>> +       eusb6_repeater: redriver@4f {
>> +               compatible = "nxp,ptn3222";
>> +               reg = <0x4f>;
>> +               #phy-cells = <0>;
>> +
>> +               vdd1v8-supply = <&vreg_l4b_1p8>;
>> +               vdd3v3-supply = <&vreg_l13b_3p0>;
>> +
>> +               reset-gpios = <&tlmm 111 GPIO_ACTIVE_LOW>;
>> +
>> +               pinctrl-0 = <&eusb6_reset_n>;
>> +               pinctrl-names = "default";
>> +       };
>> +
> 
> Stray blank line

Sorry. Will fix this.

>> +};
>> +
>> +&mdss {
>> +       status = "okay";
>> +};
>> +
> 
> 
>> +
>> +&usb_1_ss0_dwc3_hs {
>> +       remote-endpoint = <&pmic_glink_ss0_hs_in>;
>> +};
>> +
>> +&usb_1_ss0_qmpphy_out {
>> +       remote-endpoint = <&pmic_glink_ss0_ss_in>;
>> +};
>> +
> 
> Here as well

Same here.

Regards,
Georg

  reply	other threads:[~2025-03-06 13:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 12:25 Georg Gottleuber
2025-03-06 12:41 ` Krzysztof Kozlowski
2025-03-06 13:56   ` Georg Gottleuber [this message]
2025-03-06 14:03     ` Krzysztof Kozlowski
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=d98ad83e-6479-4453-bd1d-4f3703b0dad2@tuxedocomputers.com \
    --to=g.gottleuber@tuxedocomputers.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cs@tuxedocomputers.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ggo@tuxedocomputers.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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

all inboxes | Powered by JetHome®