From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pritam Manohar Sutar <pritam.sutar@samsung.com>,
'Rob Herring' <robh@kernel.org>
Cc: alim.akhtar@samsung.com, conor+dt@kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, rosa.pila@samsung.com,
selvarasu.g@samsung.com, linux-samsung-soc@vger.kernel.org,
muhammed.ali@samsung.com, faraz.ata@samsung.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
dev.tailor@samsung.com
Subject: Re: [PATCH v2 0/3] Add and enable USB nodes for ExynosAutov920 SoC
Date: Wed, 28 Jan 2026 08:38:26 +0100 [thread overview]
Message-ID: <5d3a2dac-ef86-4855-9978-79f0815e2c01@kernel.org> (raw)
In-Reply-To: <000001dc8c30$d83ce2e0$88b6a8a0$@samsung.com>
On 23/01/2026 07:23, Pritam Manohar Sutar wrote:
>
> Apologize for any inconvenience caused by the issues you’ve identified.
> Below, Have outlined the changes, will implement to address the warnings
> and ensure the patch set aligns with the required standards.
>
> Proposed Changes:
> 1. Will include #phy-cells = <0>; in the USB PHY nodes
> (usb_phy0, usb_phy1, usb_phy2, and usb_phy3)
> This is a crucial addition to avoid compilation warnings and ensure compatibility.
>
> Example:
> usb_phy0: usb-phy0 {
> compatible = "usb-nop-xceiv";
> #phy-cells = <0>;
> vbus-supply = <&usbdrd31_dwc3_vbus>;
> };
>
> 2. The errors were not caught by the make dt_binding_check and make dtbs_check
> commands
> make -j ARCH=arm64 dt_binding_check dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/phy/samsung,usb3-drd-phy.yaml
> make -j ARCH=arm64 dt_binding_check dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/usb/samsung,exynos-dwc3.yaml
>
> 3. Once the above changes are verified and tested, I will incorporate them into the
> next version of the patch set (v3).
>
> Questions:
> 1. Are the Proposed Changes Correct?
> Please confirm if the inclusion of #phy-cells = <0>; in the USB PHY nodes is the correct
> fix for the issue. If there are additional changes required, kindly let me know.
>
> 2. Why Warnings Were Not Captured During Initial Checks?
> The make dt_binding_check and make dtbs_check commands did not flag the warnings,
> which suggests the schema or bindings might not be comprehensive enough. Could you
> provide insights or recommendations on how to improve the schema to catch such issues
> in the future?
Please explain, why are we talking through microslop ChatGPT?
Best regards,
Krzysztof
prev parent reply other threads:[~2026-01-28 7:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260122125130epcas5p4ac37f540c609f3016ff02f5708e897a2@epcas5p4.samsung.com>
2026-01-22 13:07 ` [PATCH v2 0/3] Add and enable USB nodes for ExynosAutov920 SoC Pritam Manohar Sutar
2026-01-22 13:07 ` [PATCH v2 1/3] arm64: dts: exynos: ExynosAutov920: Add USB and USB-phy nodes Pritam Manohar Sutar
2026-01-22 13:07 ` [PATCH v2 2/3] arm64: dts: exynos: ExynosAutov920: Add regulators for the USB Pritam Manohar Sutar
2026-01-22 13:34 ` Krzysztof Kozlowski
2026-02-12 11:37 ` pritam.sutar
2026-02-15 8:57 ` Krzysztof Kozlowski
2026-02-18 9:28 ` pritam.sutar
2026-02-18 19:54 ` Krzysztof Kozlowski
2026-03-04 7:46 ` pritam.sutar
2026-03-04 8:08 ` Krzysztof Kozlowski
2026-01-22 13:07 ` [PATCH v2 3/3] arm64: dts: exynos: ExynosAutov920: Enable USB nodes Pritam Manohar Sutar
2026-01-22 13:35 ` Krzysztof Kozlowski
2026-01-23 7:29 ` Pritam Manohar Sutar
2026-01-23 7:59 ` Pritam Manohar Sutar
2026-01-23 8:05 ` Krzysztof Kozlowski
2026-02-12 11:40 ` pritam.sutar
2026-01-28 7:36 ` Krzysztof Kozlowski
2026-02-12 11:42 ` pritam.sutar
2026-01-22 17:15 ` [PATCH v2 0/3] Add and enable USB nodes for ExynosAutov920 SoC Rob Herring
2026-01-23 6:23 ` Pritam Manohar Sutar
2026-01-23 7:31 ` Krzysztof Kozlowski
2026-02-12 11:48 ` pritam.sutar
2026-01-28 7:38 ` Krzysztof Kozlowski [this message]
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=5d3a2dac-ef86-4855-9978-79f0815e2c01@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=dev.tailor@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=faraz.ata@samsung.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=muhammed.ali@samsung.com \
--cc=pritam.sutar@samsung.com \
--cc=robh@kernel.org \
--cc=rosa.pila@samsung.com \
--cc=selvarasu.g@samsung.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