From: "Rob Herring (Arm)" <robh@kernel.org>
To: Marcus Glocker <marcus@nazgul.ch>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Johan Hovold <johan@kernel.org>,
linux-arm-msm@vger.kernel.org,
Marijn Suijten <marijn.suijten@somainline.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abel.vesa@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH v3 0/6] Add initial DTS for Samsung Galaxy Book4 Edge
Date: Thu, 15 Aug 2024 12:28:18 -0600 [thread overview]
Message-ID: <172374583455.2827038.7584455596512370219.robh@kernel.org> (raw)
In-Reply-To: <v2iah5yrne4u6uzrnzg36tvtxzqrpiez6io2gyyfrht2x42umw@5ribqndiavxv>
On Thu, 15 Aug 2024 12:36:40 +0200, Marcus Glocker wrote:
> This DTS adds initial support for the Samsung Galaxy Book4 Edge laptop.
> Keyboard, Touch-pad, and UFS are working. The Touch-screen needs further
> investigation, and is therefore disabled for now.
>
> Changed from v2:
> - Squash Makefile patch to new DTS file patch.
>
> Changed from v1:
> - Provide the patch in the expected format.
> - Added missing bindings.
> - Removed sound node.
> - Changed regulator syntax to be consistent.
> - Changed touchscreen node comment, and removed false pin definition.
> - Rename ufshc@ to ufs@.
>
> Marcus Glocker (6):
> dt-bindings: crypto: Add X1E80100 Crypto Engine
> dt-bindings: phy: Add X1E80100 UFS
> dt-bindings: ufs: Add X1E80100 UFS
> arm64: dts: qcom: Add UFS node
> dt-bindings: arm: Add Samsung Galaxy Book4 Edge
> arm64: dts: qcom: Add Samsung Galaxy Book4 Edge DTS
>
> .../devicetree/bindings/arm/qcom.yaml | 1 +
> .../crypto/qcom,inline-crypto-engine.yaml | 1 +
> .../phy/qcom,sc8280xp-qmp-ufs-phy.yaml | 2 +
> .../devicetree/bindings/ufs/qcom,ufs.yaml | 2 +
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> .../x1e80100-samsung-galaxy-book4-edge.dts | 959 ++++++++++++++++++
> arch/arm64/boot/dts/qcom/x1e80100.dtsi | 71 ++
> 7 files changed, 1037 insertions(+)
> create mode 100644 arch/arm64/boot/dts/qcom/x1e80100-samsung-galaxy-book4-edge.dts
>
> --
> 2.39.2
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.
If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:
pip3 install dtschema --upgrade
New warnings running 'make CHECK_DTBS=y qcom/x1e80100-samsung-galaxy-book4-edge.dtb' for v2iah5yrne4u6uzrnzg36tvtxzqrpiez6io2gyyfrht2x42umw@5ribqndiavxv:
arch/arm64/boot/dts/qcom/x1e80100-samsung-galaxy-book4-edge.dtb: domain-idle-states: cluster-sleep-0: 'idle-state-name' does not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
arch/arm64/boot/dts/qcom/x1e80100-samsung-galaxy-book4-edge.dtb: domain-idle-states: cluster-sleep-1: 'idle-state-name' does not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
arch/arm64/boot/dts/qcom/x1e80100-samsung-galaxy-book4-edge.dtb: phy@1d87000: clocks: [[2, 0], [52, 242]] is too short
from schema $id: http://devicetree.org/schemas/phy/qcom,sc8280xp-qmp-ufs-phy.yaml#
arch/arm64/boot/dts/qcom/x1e80100-samsung-galaxy-book4-edge.dtb: phy@1d87000: 'vdda-phy-max-microamp', 'vdda-pll-max-microamp' do not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/phy/qcom,sc8280xp-qmp-ufs-phy.yaml#
arch/arm64/boot/dts/qcom/x1e80100-samsung-galaxy-book4-edge.dtb: usb@a2f8800: interrupt-names: ['pwr_event', 'dp_hs_phy_irq', 'dm_hs_phy_irq'] is too short
from schema $id: http://devicetree.org/schemas/usb/qcom,dwc3.yaml#
prev parent reply other threads:[~2024-08-15 18:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 10:36 [PATCH v3 0/6] Add initial DTS for Samsung Galaxy Book4 Edge Marcus Glocker
2024-08-15 10:38 ` [PATCH v3 1/6] dt-bindings: crypto: Add X1E80100 Crypto Engine Marcus Glocker
2024-08-16 7:13 ` Krzysztof Kozlowski
2024-08-15 10:39 ` [PATCH v3 2/6] dt-bindings: phy: Add X1E80100 UFS Marcus Glocker
2024-08-16 7:14 ` Krzysztof Kozlowski
2024-08-15 10:41 ` [PATCH v3 3/6] dt-bindings: ufs: " Marcus Glocker
2024-08-16 7:15 ` Krzysztof Kozlowski
2024-08-15 10:42 ` [PATCH v3 4/6] arm64: dts: qcom: Add UFS node Marcus Glocker
2024-08-15 10:47 ` Abel Vesa
2024-08-15 11:54 ` Marcus Glocker
2024-08-15 13:18 ` Abel Vesa
2024-08-15 16:59 ` Marcus Glocker
2024-08-16 7:16 ` Krzysztof Kozlowski
2024-08-16 7:21 ` Krzysztof Kozlowski
2024-08-15 10:43 ` [PATCH v3 5/6] dt-bindings: arm: Add Samsung Galaxy Book4 Edge Marcus Glocker
2024-08-16 7:17 ` Krzysztof Kozlowski
2024-08-15 10:45 ` [PATCH v3 6/6] arm64: dts: qcom: Add Samsung Galaxy Book4 Edge DTS Marcus Glocker
2024-08-16 7:19 ` Krzysztof Kozlowski
2024-08-16 7:21 ` Krzysztof Kozlowski
2024-08-15 18:28 ` Rob Herring (Arm) [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=172374583455.2827038.7584455596512370219.robh@kernel.org \
--to=robh@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus@nazgul.ch \
--cc=marijn.suijten@somainline.org \
/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