From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Robert Marko <robimarko@gmail.com>,
Guru Das Srinagesh <linux@gurudas.dev>,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v4 00/19] firmware: qcom: scm: Add minidump SRAM destination support
Date: Sun, 2 Aug 2026 22:24:01 -0500 [thread overview]
Message-ID: <178572744558.408250.13232612151478495014.b4-ty@kernel.org> (raw)
In-Reply-To: <20260624190830.3131112-1-mukesh.ojha@oss.qualcomm.com>
On Thu, 25 Jun 2026 00:38:11 +0530, Mukesh Ojha wrote:
> On most Qualcomm SoCs where minidump is supported, a word in
> always-on SRAM is shared between the operating system (OS) and
> boot firmware. Before DDR is initialised on the warm reset
> following a crash, firmware reads this word to decide if minidump
> is enabled and collect a minidump and where to deliver it:
> destination (USB upload to a host, or save to local storage) and
> OS is expected to select one destination.
>
> [...]
Applied, thanks!
[06/19] arm64: dts: qcom: kaanapali: Add minidump SRAM config to SCM node
commit: d01693e992b8faebe61612208096e5937684aaf2
[07/19] arm64: dts: qcom: sm8450: Add minidump SRAM config to SCM node
commit: 90a6f902c8de56a2e32f8c458c10e42b29a4394a
[08/19] arm64: dts: qcom: sa8775p: Add minidump SRAM config to SCM node
commit: 1243108ae31de2de25ba08d08debad4bf8afe3ad
[09/19] arm64: dts: qcom: qcs8300: Add minidump SRAM config to SCM node
commit: 8106cb30725baca6568cc8f54dffdbef792d52bf
[10/19] arm64: dts: qcom: qdu1000: Add minidump SRAM config to SCM node
commit: 27ba11afe4aeeed7d9aa31179fdc46656d6f335d
[11/19] arm64: dts: qcom: sm8550: Add minidump SRAM config to SCM node
commit: a1db65c7980a5567396a74ce94272d26f0bcb86a
[12/19] arm64: dts: qcom: sm8650: Add minidump SRAM config to SCM node
(no commit info)
[13/19] arm64: dts: qcom: sc7280: Add minidump SRAM config to SCM node
commit: f0259f721e1870177a949d56fc6970454c452d23
[14/19] arm64: dts: qcom: sm8350: Add minidump SRAM config to SCM node
commit: e030c56e38fcd5d30fb57f0db3388d13e29872b4
[15/19] arm64: dts: qcom: sc7180: Add minidump SRAM config to SCM node
commit: 9d2f33d8ceacde93631319f06243bfc5ed41e2d7
[16/19] arm64: dts: qcom: sm6350: Add minidump SRAM config to SCM node
commit: 4e9b6041bbdddde93369df47ba44c759e29c0972
[17/19] arm64: dts: qcom: sm6375: Add minidump SRAM config to SCM node
commit: aadae3dbd5ae8c98ee1e6c8b6636f18b006cb905
[18/19] arm64: dts: qcom: qcs615: Add minidump SRAM config to SCM node
commit: 32df14ece3e5c92bd2ddf1eebb3f193df3b7a701
[19/19] arm64: dts: qcom: sdm845: Add minidump SRAM config to SCM node
commit: 6fb55156f44ae3fd8e2a308167ed8dad1249492a
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-08-03 3:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 19:08 Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 01/19] dt-bindings: firmware: qcom,scm: Add minidump SRAM property Mukesh Ojha
2026-06-30 16:19 ` Rob Herring (Arm)
2026-06-24 19:08 ` [PATCH v4 02/19] dt-bindings: sram: qcom,imem: Add minidump-sram pattern property Mukesh Ojha
2026-06-30 16:20 ` Rob Herring (Arm)
2026-06-24 19:08 ` [PATCH v4 03/19] firmware: qcom: scm: Fix missing smp_load_acquire() Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 04/19] firmware: qcom: scm: use dev_err_probe() for dload address failure Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 05/19] firmware: qcom: scm: Add minidump SRAM support Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 06/19] arm64: dts: qcom: kaanapali: Add minidump SRAM config to SCM node Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 07/19] arm64: dts: qcom: sm8450: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 08/19] arm64: dts: qcom: sa8775p: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 09/19] arm64: dts: qcom: qcs8300: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 10/19] arm64: dts: qcom: qdu1000: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 11/19] arm64: dts: qcom: sm8550: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 12/19] arm64: dts: qcom: sm8650: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 13/19] arm64: dts: qcom: sc7280: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 14/19] arm64: dts: qcom: sm8350: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 15/19] arm64: dts: qcom: sc7180: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 16/19] arm64: dts: qcom: sm6350: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 17/19] arm64: dts: qcom: sm6375: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 18/19] arm64: dts: qcom: qcs615: " Mukesh Ojha
2026-06-24 19:08 ` [PATCH v4 19/19] arm64: dts: qcom: sdm845: " Mukesh Ojha
2026-06-26 12:44 ` Konrad Dybcio
2026-07-13 15:06 ` (subset) [PATCH v4 00/19] firmware: qcom: scm: Add minidump SRAM destination support Bjorn Andersson
2026-07-31 3:23 ` Bjorn Andersson
2026-08-03 3:24 ` Bjorn Andersson [this message]
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=178572744558.408250.13232612151478495014.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.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=linux@gurudas.dev \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=robimarko@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
all inboxes | Powered by JetHome®