From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Royyan Zahir <royzah@gmail.com>,
linux-arm-msm@vger.kernel.org,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, aesteve@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: qcom: scm: clear download mode and SDI before a restart
Date: Fri, 16 Oct 2026 12:37:14 +0200 [thread overview]
Message-ID: <15a6f557-12a7-4dc6-8faa-fe96f9ed5d0a@oss.qualcomm.com> (raw)
In-Reply-To: <20260921073231.3254159-1-royzah@gmail.com>
On 9/21/26 9:32 AM, Royyan Zahir wrote:
> With qcom_scm.download_mode=1 an IQ-9075 never completes a warm reboot.
> XBL stops in download mode and only a cold power cycle recovers the board:
>
> B - 857233 - TCSR reg value 0x10
> B - 865071 - RamDump - Image Load, Start
> B - 884317 - boot_dload_entry
> B - 6774477 - USB DUMP failed, because USB cable disconnect
>
> 0x10 is FIELD_PREP(QCOM_DLOAD_MASK, QCOM_DLOAD_FULLDUMP), so the cookie
> written at probe is still set when XBL reads it, even though systemd
> stopped every unit in order and nothing panicked.
>
> Two latches have to come down and neither reliably does.
> qcom_scm_shutdown() clears the cookie from .shutdown, which
> device_shutdown() calls after the SCM device's own dependencies may
> already be torn down, so the write can fail with nothing left to report
> it to.
Ouch. Indeed there's no devlink or similar between the SCM producer
and its consumers. It just so happened not to surface any issues for
N years..
> SDI is disabled only from probe, and only when download_mode was> zero at that moment, so a board booted with download mode on keeps
> watchdog debug armed for the life of the boot. Writing "off" to the
> module parameter later clears the cookie but never reaches SDI, which is
> why that runtime workaround does not restore warm reboot.
+Mukesh are dump_mode and SDI supposed to be disabled together (i.e.
do we need if (off) { disable_sdi() } in the .store path), or are they
orthogonal?
Konrad
prev parent reply other threads:[~2026-10-16 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:32 Royyan Zahir
2026-10-16 10:37 ` Konrad Dybcio [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=15a6f557-12a7-4dc6-8faa-fe96f9ed5d0a@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=aesteve@redhat.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.com \
--cc=royzah@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®