From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: jens.glathe@oldschoolsolutions.biz,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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,
Maud Spierings <maud_spierings@hotmail.com>,
"Colin K. Williams" <colin@li-nk.org>
Subject: Re: [PATCH v2 4/4] arm64: dts: qcom: x1-vivobook-s15: add Purwa-compatible device tree
Date: Thu, 12 Feb 2026 11:03:13 +0100 [thread overview]
Message-ID: <478f9622-55e4-40b8-b48c-f5589fa015ca@oss.qualcomm.com> (raw)
In-Reply-To: <20260211-b4-vivobook-v2-4-9f500415d2ed@oldschoolsolutions.biz>
On 2/11/26 9:37 PM, Jens Glathe via B4 Relay wrote:
> From: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
>
> The ASUS Vivobook S15 (S5507) [1] is available with Hamoa and Purwa SoC.
>
> Add the Purwa-based device tree.
>
> [1]: https://www.asus.com/de/laptops/for-home/vivobook/asus-vivobook-s-15-s5507/techspec/
>
> Tested-by: Colin K. Williams <colin@li-nk.org>
> Signed-off-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
> ---
[...]
> +/delete-node/ &pmc8380_6;
> +/delete-node/ &pmc8380_6_thermal;
> +
> +/ {
> + model = "ASUS Vivobook S 15 X1P-42-100";
> + compatible = "asus,vivobook-s15-x1p4", "qcom,x1p42100";
> + chassis-type = "laptop";
> +};
> +
> +&gpu_zap_shader {
> + firmware-name = "qcom/x1p42100/ASUSTeK/vivobook-s15/qcdxkmsucpurwa.mbn";
> +};
> +
> +&iris {
> + firmware-name = "qcom/x1p42100/ASUSTeK/vivobook-s15/qcvss8380.mbn";
> + status = "okay";
nit: Ideally there would be a consistent \n before this status, like near
the ones below
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
> +};
> +
> +&remoteproc_adsp {
> + firmware-name = "qcom/x1p42100/ASUSTeK/vivobook-s15/qcadsp8380.mbn",
> + "qcom/x1p42100/ASUSTeK/vivobook-s15/adsp_dtbs.elf";
> +
> + status = "okay";
> +};
> +
> +&remoteproc_cdsp {
> + firmware-name = "qcom/x1p42100/ASUSTeK/vivobook-s15/qccdsp8380.mbn",
> + "qcom/x1p42100/ASUSTeK/vivobook-s15/cdsp_dtbs.elf";
> +
> + status = "okay";
> +};
> +
>
prev parent reply other threads:[~2026-02-12 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 20:37 [PATCH v2 0/4] arm64: qcom: x1-vivobook-s15: add X1P42100 variant, restructure dts files Jens Glathe via B4 Relay
2026-02-11 20:37 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Add ASUS Vivobook X1P42100 variant Jens Glathe via B4 Relay
2026-02-12 11:15 ` Krzysztof Kozlowski
2026-02-11 20:37 ` [PATCH v2 2/4] firmware: qcom: scm: allow QSEECOM on " Jens Glathe via B4 Relay
2026-02-11 20:37 ` [PATCH v2 3/4] arm64: dts: qcom: x1-vivobook-s15: create a common dtsi for Hamoa and Purwa variants Jens Glathe via B4 Relay
2026-02-12 10:02 ` Konrad Dybcio
2026-02-13 17:05 ` Dmitry Baryshkov
2026-02-11 20:37 ` [PATCH v2 4/4] arm64: dts: qcom: x1-vivobook-s15: add Purwa-compatible device tree Jens Glathe via B4 Relay
2026-02-12 10:03 ` 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=478f9622-55e4-40b8-b48c-f5589fa015ca@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=colin@li-nk.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maud_spierings@hotmail.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
all inboxes | Powered by JetHome®