From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: wuxilin123@gmail.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, Abel Vesa <abel.vesa@linaro.org>,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Add device tree for ASUS Vivobook S 15
Date: Sat, 29 Jun 2024 14:56:40 +0200 [thread overview]
Message-ID: <0c47c5fa-5fe2-4675-8eb9-9707f044ce90@linaro.org> (raw)
In-Reply-To: <20240628-asus-vivobook-s15-v1-2-2a1e4571b8ab@gmail.com>
On 28.06.2024 1:30 PM, Xilin Wu via B4 Relay wrote:
> From: Xilin Wu <wuxilin123@gmail.com>
>
> ASUS Vivobook S 15 is a laptop based on the Qualcomm Snapdragon X Elite
> SoC (X1E78100).
>
> Add the device tree for the laptop with support for the following features:
>
> - CPU frequency scaling up to 3.4GHz
> - NVMe storage on PCIe 6a (capable of Gen4x4, currently limited to Gen4x2)
> - Keyboard and touchpad
> - WCN7850 Wi-Fi
> - Two Type-C ports on the left side (USB3 only in one orientation)
> - internal eDP display
> - ADSP and CDSP remoteprocs
>
> Further details could be found in the cover letter.
>
> Signed-off-by: Xilin Wu <wuxilin123@gmail.com>
> ---
[...]
> + pmic-glink {
> + compatible = "qcom,x1e80100-pmic-glink",
> + "qcom,sm8550-pmic-glink",
> + "qcom,pmic-glink";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + orientation-gpios = <&tlmm 121 GPIO_ACTIVE_HIGH>,
> + <&tlmm 123 GPIO_ACTIVE_HIGH>;
#address-/size-cells usually go at the end
> +
> + connector@0 {
Could you add a comment detailing which port is which (like in x1e80100-crd.dts)?
> + pinctrl-names = "default";
> + pinctrl-0 = <&nvme_reg_en>;
property-n
property-names
[...]
> +
> + ports {
> + port@1 {
> + reg = <1>;
Please separate properties with subnodes with a newline
[...]
> +
> + pinctrl-names = "default";
> + pinctrl-0 = <&pcie6a_default>;
property-n
property-names
Looks good otherwise!
Konrad
prev parent reply other threads:[~2024-06-29 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 11:30 [PATCH 0/2] Introduce ASUS Vivobook S 15 Xilin Wu via B4 Relay
2024-06-28 11:30 ` [PATCH 1/2] dt-bindings: arm: qcom: Add " Xilin Wu via B4 Relay
2024-06-28 11:30 ` [PATCH 2/2] arm64: dts: qcom: Add device tree for " Xilin Wu via B4 Relay
2024-06-28 11:39 ` Xilin Wu
2024-06-29 12:56 ` Konrad Dybcio [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=0c47c5fa-5fe2-4675-8eb9-9707f044ce90@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wuxilin123@gmail.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;
as well as URLs for NNTP newsgroup(s).