Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: webgeek1234@gmail.com, 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, Teguh Sobirin <teguh@sobir.in>
Subject: Re: [PATCH v4 6/6] arm64: dts: qcom: Add AYN Thor
Date: Wed, 25 Mar 2026 12:09:25 +0100	[thread overview]
Message-ID: <919a157e-84cd-4588-8557-64542fd08e7e@oss.qualcomm.com> (raw)
In-Reply-To: <20260323-ayn-qcs8550-v4-6-33a8ac3d53fa@gmail.com>

On 3/23/26 5:27 PM, Aaron Kling via B4 Relay wrote:
> From: Teguh Sobirin <teguh@sobir.in>
> 
> The AYN Thor is a high-performance Android-based handheld gaming console
> powered by the Qualcomm Snapdragon 8 Gen 2 processor featuring dual
> AMOLED touchscreens.
> 
> Signed-off-by: Teguh Sobirin <teguh@sobir.in>
> Co-developed-by: Aaron Kling <webgeek1234@gmail.com>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---

[...]

> +&{/} {
> +	model = "AYN Thor";
> +	compatible = "ayntec,thor", "qcom,qcs8550", "qcom,sm8550";
> +
> +	gpio-keys {

Please override gpio-keys from common by label reference

[...]

> +&mdss_dsi0_phy {
> +	vdds-supply = <&vreg_l1e_0p88>;
> +	status = "okay";

nit: Please uniformly keep a \n before status

> +};
> +
> +&mdss_dsi1_out {
> +	qcom,te-source = "mdp_vsync_s";
> +};
> +
> +&pm8550_pwm {
> +	multi-led {
> +		status = "disabled";
> +	};

Please override the multi-led node by label directly

Konrad

  reply	other threads:[~2026-03-25 11:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 16:27 [PATCH v4 0/6] arm64: dts: qcom: Support AYN QCS8550 Devices Aaron Kling via B4 Relay
2026-03-23 16:27 ` [PATCH v4 1/6] dt-bindings: vendor-prefixes: Add AYN Technologies Aaron Kling via B4 Relay
2026-03-24  8:50   ` Krzysztof Kozlowski
2026-03-23 16:27 ` [PATCH v4 2/6] dt-bindings: arm: qcom: Add AYN QCS8550 Devices Aaron Kling via B4 Relay
2026-03-24  8:50   ` Krzysztof Kozlowski
2026-03-23 16:27 ` [PATCH v4 3/6] arm64: dts: qcom: Add AYN QCS8550 Common Aaron Kling via B4 Relay
2026-03-24 12:35   ` Konrad Dybcio
2026-03-27 21:26     ` Aaron Kling
2026-03-30 11:00       ` Konrad Dybcio
2026-03-30 11:01         ` Konrad Dybcio
2026-03-30 11:32         ` Dmitry Baryshkov
2026-04-02 22:04           ` Aaron Kling
2026-04-07  9:20             ` Konrad Dybcio
2026-03-23 16:27 ` [PATCH v4 4/6] arm64: dts: qcom: Add AYN Odin 2 Mini Aaron Kling via B4 Relay
2026-03-24 12:36   ` Konrad Dybcio
2026-03-23 16:27 ` [PATCH v4 5/6] arm64: dts: qcom: Add AYN Odin 2 Portal Aaron Kling via B4 Relay
2026-03-24 12:36   ` Konrad Dybcio
2026-03-23 16:27 ` [PATCH v4 6/6] arm64: dts: qcom: Add AYN Thor Aaron Kling via B4 Relay
2026-03-25 11:09   ` Konrad Dybcio [this message]
2026-03-25 16:45     ` Aaron Kling

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=919a157e-84cd-4588-8557-64542fd08e7e@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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=robh@kernel.org \
    --cc=teguh@sobir.in \
    --cc=webgeek1234@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