From: Johan Hovold <johan+linaro@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mukesh Ojha <quic_mojha@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: [PATCH 0/2] firmware: qcom: scm: suppress download mode error
Date: Wed, 2 Oct 2024 12:01:20 +0200 [thread overview]
Message-ID: <20241002100122.18809-1-johan+linaro@kernel.org> (raw)
When booting 6.12-rc1 on x1e80100 I noticed a new error in the boot log,
which I had previously also seen on reboots.
Turns out the scm driver is incorrectly logging the fact that the
download mode feature is not available as an error on both boot and
shutdown even when the user has not requested the system to enable dump
mode.
The second patch enables the download mode feature on x1e80100, which
from 6.12-rc1 specifically results in a reboot instead of entering crash
dump mode after a hypervisor reset on the x1e80100 CRD by default.
Johan
Johan Hovold (2):
firmware: qcom: scm: suppress download mode error
arm64: dts: qcom: x1e80100: describe tcsr download mode register
arch/arm64/boot/dts/qcom/x1e80100.dtsi | 1 +
drivers/firmware/qcom/qcom_scm.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.45.2
next reply other threads:[~2024-10-02 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 10:01 Johan Hovold [this message]
2024-10-02 10:01 ` [PATCH 1/2] firmware: qcom: scm: suppress download mode error Johan Hovold
2024-10-04 21:49 ` Mukesh Ojha
2024-10-02 10:01 ` [PATCH 2/2] arm64: dts: qcom: x1e80100: describe tcsr download mode register Johan Hovold
2024-10-04 9:49 ` Konrad Dybcio
2024-10-07 14:25 ` (subset) [PATCH 0/2] firmware: qcom: scm: suppress download mode error Bjorn Andersson
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=20241002100122.18809-1-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--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=quic_mojha@quicinc.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;
as well as URLs for NNTP newsgroup(s).