From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mukesh Ojha <mukesh.ojha@oss.qualcomm.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
Subject: Re: [PATCH v11 1/2] arm64: dts: qcom: qcm6490-idp/qcs6490-rb3gen2: Keep wlan_ce_mem and drop redundant wifi memory-region
Date: Tue, 25 Aug 2026 11:32:49 +0200 [thread overview]
Message-ID: <23370124-adb0-4b9f-a818-0a864a291099@oss.qualcomm.com> (raw)
In-Reply-To: <20260803121042.3313824-2-mukesh.ojha@oss.qualcomm.com>
On 8/3/26 2:10 PM, Mukesh Ojha wrote:
> The reserved region wlan_ce_mem is device memory used by the WCN6750
> firmware. Deleting it in qcm6490-idp.dts and qcs6490-rb3gen2.dts is
> erroneous — the region must remain present regardless of whether the
> underlying OS uses it — so drop the /delete-node/ &wlan_ce_mem; from
> both board files.
But it starts below 0x8000_0000 where RAM starts, so it shouldn't really
matter, no?
Konrad
next prev parent reply other threads:[~2026-08-25 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 12:10 [PATCH v11 0/2] arm64: dts: qcom: kodiak: EL2 overlay for qcm6490-idp / qcs6490-rb3gen2 Mukesh Ojha
2026-08-03 12:10 ` [PATCH v11 1/2] arm64: dts: qcom: qcm6490-idp/qcs6490-rb3gen2: Keep wlan_ce_mem and drop redundant wifi memory-region Mukesh Ojha
2026-08-25 9:32 ` Konrad Dybcio [this message]
2026-09-20 7:54 ` Mukesh Ojha
2026-10-26 15:23 ` Konrad Dybcio
2026-08-03 12:10 ` [PATCH v11 2/2] arm64: dts: qcom: kodiak: Add EL2 overlay Mukesh Ojha
2026-10-26 16:18 ` [PATCH v11 0/2] arm64: dts: qcom: kodiak: EL2 overlay for qcm6490-idp / qcs6490-rb3gen2 Abel Vesa
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=23370124-adb0-4b9f-a818-0a864a291099@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=mukesh.ojha@oss.qualcomm.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®