mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Tianyuan Jiang <code_0002@163.com>,
	krzk@kernel.org, andersson@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Tianyuan Jiang <hiez832670@gmail.com>
Subject: Re: [PATCH v6] arm64: dts: qcom: sm8550: add Xiaomi Pad 6S Pro (sheng)
Date: Wed, 21 Oct 2026 12:22:25 +0200	[thread overview]
Message-ID: <b62ed7e7-a9de-4420-97df-5e4f73ccc768@oss.qualcomm.com> (raw)
In-Reply-To: <20260721153444.423-1-code_0002@163.com>

On 7/21/26 5:34 PM, Tianyuan Jiang wrote:
> From: Tianyuan Jiang <hiez832670@gmail.com>
> 
> Add device tree for Xiaomi Pad 6S Pro (sheng) based on SM8550.
> 
> Signed-off-by: Tianyuan Jiang <code_0002@163.com>

[...]

> +		/* Required for libcamera to allocate buffers when cma is used. */
> +		linux,cma {
> +			compatible = "shared-dma-pool";
> +			size = <0x0 0x30000000>;
> +			reusable;
> +			linux,cma-default;
> +		};

If you update libcamera and enable DMABUFS in the kernel, is
this still necessary?


> +&ipa {
> +	qcom,gsi-loader = "self";
> +	memory-region = <&ipa_fw_mem>;
> +	firmware-name = "qcom/sm8550/xiaomi-sheng/ipa_fws.mbn";
> +	status = "okay";

nit: please keep a \n before 'status' consistently, file-wide

[...]

> +	nanosic_mcu@4c {

Node names must not contain underscores

> +		compatible = "nanosic,wn8030-sheng";

This compatible is not documented and I see no references in your message

[...]

> +&spi4 {
> +	status = "okay";
> +
> +	touchscreen@0 {
> +		compatible = "novatek,NVT-ts-spi";

Likewise

[...]


> +&uart14 {
> +	status = "okay";
> +
> +	bluetooth {
> +		compatible = "qcom,wcn7850-bt";
> +
> +		local-bd-address = [ 00 00 00 00 00 00 ];

I assume the bootloader doesn't update this, in which case I don't
think there's a good reason to keep this property here

Konrad

  parent reply	other threads:[~2026-10-21 10:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:21 [PATCH v2] " code_0002
2026-07-21 14:41 ` Konrad Dybcio
2026-07-21 14:41 ` Konrad Dybcio
2026-07-21 15:22 ` Krzysztof Kozlowski
2026-07-21 15:34 ` [PATCH v6] " Tianyuan Jiang
2026-07-21 15:46   ` Krzysztof Kozlowski
2026-10-21 10:22   ` Konrad Dybcio [this message]
2026-07-21 16:00 ` [PATCH v2] arm64: dts: qcom: sm8550: add xiaomi pad 6s pro (sheng) dts Tianyuan Jiang

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=b62ed7e7-a9de-4420-97df-5e4f73ccc768@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=code_0002@163.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hiez832670@gmail.com \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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®