mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: david@ixit.cz, 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>,
	Amit Pundir <amit.pundir@linaro.org>,
	Molly Sophia <mollysophia379@gmail.com>,
	Petr Hodina <petr.hodina@protonmail.com>
Cc: Konrad Dybcio <konradybcio@gmail.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: sdm845-xiaomi-beryllium: Extend the xbl_mem region
Date: Wed, 23 Sep 2026 14:46:10 +0200	[thread overview]
Message-ID: <7431ceec-62dc-4dcb-baa4-9ec41392e72c@oss.qualcomm.com> (raw)
In-Reply-To: <20260916-sdm845-xbl-mem-v1-1-6e3c88507997@ixit.cz>

On 9/16/26 12:25 AM, David Heidelberg via B4 Relay wrote:
> From: David Heidelberg <david@ixit.cz>
> 
> Xiaomi's Oreo-era tree still had the CAF 1 MiB region, the 2 MiB version
> arrived with the Pie import. This isn't a board-layout quirk, it tracks
> the firmware. The later XBL wants one extra MiB below the old region.

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

  reply	other threads:[~2026-09-23 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 22:25 [PATCH 0/2] arm64: dts: qcom: sdm845-xiaomi: Recent firmware needs bigger XBL David Heidelberg via B4 Relay
2026-09-15 22:25 ` [PATCH 1/2] arm64: dts: qcom: sdm845-xiaomi-beryllium: Extend the xbl_mem region David Heidelberg via B4 Relay
2026-09-23 12:46   ` Konrad Dybcio [this message]
2026-09-15 22:25 ` [PATCH 2/2] arm64: dts: qcom: sdm845-xiaomi-polaris: " David Heidelberg via B4 Relay

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=7431ceec-62dc-4dcb-baa4-9ec41392e72c@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mollysophia379@gmail.com \
    --cc=petr.hodina@protonmail.com \
    --cc=robh@kernel.org \
    --cc=stable@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®