From: Xilin Wu <wuxilin123@gmail.com>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
Elliot Berman <quic_eberman@quicinc.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: qcom: Add device tree for ASUS Vivobook S 15
Date: Mon, 1 Jul 2024 10:55:47 +0800 [thread overview]
Message-ID: <acff166f-9ebb-456e-9bea-61c3dafe7ebd@gmail.com> (raw)
In-Reply-To: <ZoGMaOdyDFjoyqww@linaro.org>
On 2024/7/1 0:48, Abel Vesa wrote:
> On 24-06-30 16:59:27, 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>
>> ---
>> arch/arm64/boot/dts/qcom/Makefile | 1 +
>> .../boot/dts/qcom/x1e80100-asus-vivobook-s15.dts | 616 +++++++++++++++++++++
>> 2 files changed, 617 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile
>> index 5576c7d6ea06..fe08b6be565d 100644
>> --- a/arch/arm64/boot/dts/qcom/Makefile
>> +++ b/arch/arm64/boot/dts/qcom/Makefile
>> @@ -258,5 +258,6 @@ dtb-$(CONFIG_ARCH_QCOM) += sm8650-hdk-display-card.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += sm8650-hdk.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += sm8650-mtp.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += sm8650-qrd.dtb
>> +dtb-$(CONFIG_ARCH_QCOM) += x1e80100-asus-vivobook-s15.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += x1e80100-crd.dtb
>> dtb-$(CONFIG_ARCH_QCOM) += x1e80100-qcp.dtb
>> diff --git a/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts b/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts
>> new file mode 100644
>> index 000000000000..34f90e45a5d7
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts
>> @@ -0,0 +1,616 @@
>> +// SPDX-License-Identifier: BSD-3-Clause
>> +/*
>> + * Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights reserved.
>> + * Copyright (c) 2024, Xilin Wu <wuxilin123@gmail.com>
>> + */
>> +
>> +/dts-v1/;
>> +
>> +#include <dt-bindings/gpio/gpio.h>
>> +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
>> +
>> +#include "x1e80100.dtsi"
>> +#include "x1e80100-pmics.dtsi"
>> +
>> +/ {
>> + model = "ASUS Vivobook S 15";
>> + compatible = "asus,vivobook-s15", "qcom,x1e80100";
>> + chassis-type = "laptop";
>> +
>
> [ ... ]
>
>> +
>> + tpad_default: tpad-default-state {
>> + pins = "gpio3";
>> + function = "gpio";
>> + bias-disable;
>> + };
>> +};
>> +
>> +&usb_1_ss0_hsphy {
>> + vdd-supply = <&vreg_l2e_0p8>;
>
> I think you will probably want to use vreg_l3j_0p8 here. See following
> fix for CRD and QCP:
>
> https://lore.kernel.org/linux-kernel/20240629-x1e80100-dts-fix-hsphy-0-8v-supplies-v1-1-de99ee030b27@linaro.org/T/
>
Indeed, I checked ACPI just now and I think the design follows CRD and QCP.
>> + vdda12-supply = <&vreg_l2j_1p2>;
>> +
>> + phys = <&smb2360_0_eusb2_repeater>;
>> +
>> + status = "okay";
>> +};
>> +
>> +&usb_1_ss0_qmpphy {
>> + vdda-phy-supply = <&vreg_l3e_1p2>;
>> + vdda-pll-supply = <&vreg_l1j_0p8>;
>> +
>> + orientation-switch;
>> +
>> + status = "okay";
>> +};
>> +
>> +&usb_1_ss0 {
>> + status = "okay";
>> +};
>> +
>> +&usb_1_ss0_dwc3 {
>> + dr_mode = "host";
>> +};
>> +
>> +&usb_1_ss0_dwc3_hs {
>> + remote-endpoint = <&pmic_glink_ss0_hs_in>;
>> +};
>> +
>> +&usb_1_ss0_qmpphy_out {
>> + remote-endpoint = <&pmic_glink_ss0_ss_in>;
>> +};
>> +
>> +&usb_1_ss1_hsphy {
>> + vdd-supply = <&vreg_l2e_0p8>;
>
> Same here.
>
>> + vdda12-supply = <&vreg_l2j_1p2>;
>> +
>> + phys = <&smb2360_1_eusb2_repeater>;
>> +
>> + status = "okay";
>> +};
>> +
>> +&usb_1_ss1_qmpphy {
>> + vdda-phy-supply = <&vreg_l3e_1p2>;
>> + vdda-pll-supply = <&vreg_l2d_0p9>;
>> +
>> + orientation-switch;
>> +
>> + status = "okay";
>> +};
>> +
>> +&usb_1_ss1 {
>> + status = "okay";
>> +};
>> +
>> +&usb_1_ss1_dwc3 {
>> + dr_mode = "host";
>> +};
>> +
>> +&usb_1_ss1_dwc3_hs {
>> + remote-endpoint = <&pmic_glink_ss1_hs_in>;
>> +};
>> +
>> +&usb_1_ss1_qmpphy_out {
>> + remote-endpoint = <&pmic_glink_ss1_ss_in>;
>> +};
>>
>> --
>> 2.45.2
>>
>>
--
Thanks,
Xilin Wu
prev parent reply other threads:[~2024-07-01 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 8:59 [PATCH v3 0/2] Introduce ASUS Vivobook S 15 Xilin Wu via B4 Relay
2024-06-30 8:59 ` [PATCH v3 1/2] dt-bindings: arm: qcom: Add " Xilin Wu via B4 Relay
2024-06-30 8:59 ` [PATCH v3 2/2] arm64: dts: qcom: Add device tree for " Xilin Wu via B4 Relay
2024-06-30 16:48 ` Abel Vesa
2024-07-01 2:55 ` Xilin Wu [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=acff166f-9ebb-456e-9bea-61c3dafe7ebd@gmail.com \
--to=wuxilin123@gmail.com \
--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=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_eberman@quicinc.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).