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>,
Robert Marko <robimarko@gmail.com>,
Guru Das Srinagesh <linux@gurudas.dev>
Cc: cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 04/18] firmware: qcom: scm: Add minidump SRAM support
Date: Thu, 11 Jun 2026 13:45:53 +0200 [thread overview]
Message-ID: <004d6bd1-2800-42d5-a6be-1fa69a06194c@oss.qualcomm.com> (raw)
In-Reply-To: <20260522195009.2961022-5-mukesh.ojha@oss.qualcomm.com>
On 5/22/26 9:49 PM, Mukesh Ojha wrote:
> On most Qualcomm SoCs where minidump is supported, a word in always-on
> SRAM is shared between the kernel 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 (USB upload to a host, or save to local storage).
>
> The SRAM region is described by a 'sram' phandle on the SCM DT node.
> If the property is absent the feature is silently disabled, keeping
> existing SoCs unaffected.
>
> Expose a 'minidump_dest' module parameter (default: usb) so the user can
> select the destination. Only the string names "usb" or "storage" are
> acceptable values.
>
> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
> ---
[...]
> + for (i = 0; i < ARRAY_SIZE(minidump_dest_map); i++)
> + if (sysfs_streq(val, minidump_dest_map[i].name))
I'm not sure about sysfs_streq() specifically, but otherwise this lgtm
Konrad
next prev parent reply other threads:[~2026-06-11 11:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 19:49 [PATCH v3 00/18] firmware: qcom: scm: Add minidump SRAM destination support Mukesh Ojha
2026-05-22 19:49 ` [PATCH v3 01/18] dt-bindings: firmware: qcom,scm: Add minidump SRAM property Mukesh Ojha
2026-05-30 8:24 ` Krzysztof Kozlowski
2026-06-01 8:41 ` Mukesh Ojha
2026-05-22 19:49 ` [PATCH v3 02/18] dt-bindings: sram: qcom,imem: Add minidump-sram pattern property Mukesh Ojha
2026-05-22 19:49 ` [PATCH v3 03/18] firmware: qcom: scm: use dev_err_probe() for dload address failure Mukesh Ojha
2026-05-22 19:49 ` [PATCH v3 04/18] firmware: qcom: scm: Add minidump SRAM support Mukesh Ojha
2026-05-22 20:21 ` sashiko-bot
2026-06-11 17:22 ` Mukesh Ojha
2026-06-11 11:45 ` Konrad Dybcio [this message]
2026-06-11 17:24 ` Mukesh Ojha
2026-06-17 10:27 ` Konrad Dybcio
2026-05-22 19:49 ` [PATCH v3 05/18] arm64: dts: qcom: kaanapali: Add minidump SRAM config to SCM node Mukesh Ojha
2026-05-22 19:49 ` [PATCH v3 06/18] arm64: dts: qcom: sm8450: " Mukesh Ojha
2026-06-11 11:34 ` Konrad Dybcio
2026-05-22 19:49 ` [PATCH v3 07/18] arm64: dts: qcom: sa8775p: " Mukesh Ojha
2026-06-11 11:37 ` Konrad Dybcio
2026-05-22 19:49 ` [PATCH v3 08/18] arm64: dts: qcom: qcs8300: " Mukesh Ojha
2026-06-11 11:37 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 09/18] arm64: dts: qcom: qdu1000: " Mukesh Ojha
2026-06-11 11:37 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 10/18] arm64: dts: qcom: sm8550: " Mukesh Ojha
2026-06-11 11:37 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 11/18] arm64: dts: qcom: sm8650: " Mukesh Ojha
2026-06-11 11:36 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 12/18] arm64: dts: qcom: sc7280: " Mukesh Ojha
2026-06-11 11:36 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 13/18] arm64: dts: qcom: sm8350: " Mukesh Ojha
2026-06-11 11:34 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 14/18] arm64: dts: qcom: sc7180: " Mukesh Ojha
2026-06-11 11:36 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 15/18] arm64: dts: qcom: sm6350: " Mukesh Ojha
2026-06-11 11:35 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 16/18] arm64: dts: qcom: sm6375: " Mukesh Ojha
2026-06-11 11:35 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 17/18] arm64: dts: qcom: qcs615: " Mukesh Ojha
2026-06-11 11:37 ` Konrad Dybcio
2026-05-22 19:50 ` [PATCH v3 18/18] arm64: dts: qcom: sdm845: " Mukesh Ojha
2026-06-11 11:34 ` Konrad Dybcio
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=004d6bd1-2800-42d5-a6be-1fa69a06194c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=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