mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amir Hanip <killdeath104@gmail.com>
To: barnabas.czeman@mainlining.org
Cc: a39skl@gmail.com, abelvesa@kernel.org, andersson@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	killdeath104@gmail.com, konrad.dybcio@oss.qualcomm.com,
	konradybcio@kernel.org, krzk+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh@kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: Add Xiaomi Poco M3
Date: Wed,  4 Nov 2026 16:58:06 +0700	[thread overview]
Message-ID: <20261104095806.18945-1-killdeath104@gmail.com> (raw)
In-Reply-To: <3ec43b1b00bca7506c1ca678c118f8c2@mainlining.org>

On Mon, 02 Nov 2026 21:11:33 +0100, Barnabas Czeman wrote:
> I have checked it seems lemon have same adsp region like citrus.
> `pil_adsp_region@53800000`

Thanks for checking, Barnabas. Where did you see it for lemon, in a
downstream DT or in the stock firmware? If lemon's stock layout also
starts at 0x53800000, the 0x53400000/0x2600000 in the lemon DTS may
be worth rechecking.

I will keep the ADSP carve-out per variant in v3, since I cannot test
lemon. Adam, if you can try lemon with 0x53800000/0x2200000, the node
could move to the common dtsi in a follow-up.

Thanks,
Amir

  reply	other threads:[~2026-11-04  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 20:51 [PATCH v2 0/2] arm64: dts: qcom: Add Xiaomi Poco M3 (citrus) Amir Hanip
2026-10-27 20:51 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Document Xiaomi Poco M3 Amir Hanip
2026-10-28 12:52   ` Krzysztof Kozlowski
2026-10-27 20:51 ` [PATCH v2 2/2] arm64: dts: qcom: Add " Amir Hanip
2026-10-28 12:35   ` Konrad Dybcio
2026-10-30 12:30   ` Barnabás Czémán
2026-11-01 16:49     ` Amir Hanip
2026-11-01 19:44       ` Barnabás Czémán
2026-11-02 10:44         ` Konrad Dybcio
2026-11-02 20:11           ` Barnabás Czémán
2026-11-04  9:58             ` Amir Hanip [this message]
2026-11-04 10:25               ` Barnabás Czémán

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=20261104095806.18945-1-killdeath104@gmail.com \
    --to=killdeath104@gmail.com \
    --cc=a39skl@gmail.com \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=barnabas.czeman@mainlining.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --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 \
    /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®