From: Johan Hovold <johan@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/5] SC8280XP SLPI
Date: Wed, 21 May 2025 09:11:31 +0200 [thread overview]
Message-ID: <aC18owkQSMfNwKUC@hovoldconsulting.com> (raw)
In-Reply-To: <a49df292-dcc6-457c-a565-984887687341@oss.qualcomm.com>
On Tue, May 20, 2025 at 04:29:18PM +0200, Konrad Dybcio wrote:
> On 5/19/25 11:35 AM, Johan Hovold wrote:
> > On Sat, May 17, 2025 at 07:27:49PM +0200, Konrad Dybcio wrote:
> >> Dmitry Baryshkov (1):
> >> arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s: enable sensors DSP
> >
> > At first I was worried that missing firmware could cause issues here
> > (e.g. drivers not reaching sync state as with venus), but Lenovo has
> > indeed released the SLPI firmware already.
> >> Konrad Dybcio (4):
> >> dt-bindings: remoteproc: qcom,sm8350-pas: Add SC8280XP
> >> arm64: dts: qcom: sc8280xp: Fix node order
> >> arm64: dts: qcom: sc8280xp: Add SLPI
> >
> >> arm64: dts: qcom: sc8280xp-crd: Enable SLPI
> >
> > Without firmware this results in errors like:
> >
> > remoteproc remoteproc0: slpi is available
> > remoteproc remoteproc0: Direct firmware load for qcom/sc8280xp/qcslpi8280.mbn failed with error -2
> > remoteproc remoteproc0: powering up slpi
> > remoteproc remoteproc0: Direct firmware load for qcom/sc8280xp/qcslpi8280.mbn failed with error -2
> > remoteproc remoteproc0: request_firmware failed: -2
> >
> > but enabling for the CRD reference design and requiring users (read:
> > developers) to copy it from Windows should be OK.
>
> We shouldn't expect non-developers to have the CRD on hand, right? ;)
That was my point: requiring user of the CRD to install firmware
manually is fine (e.g. as they would all be developers and currently all
firmware for the CRD needs to be copied from Windows anyway).
But we should not enable things like venus (that can prevent the
interconnect driver from reaching the sync state) on the X13s which has
lots of regular users until the corresponding firmware has been
released and is in linux-firmware.
Johan
next prev parent reply other threads:[~2025-05-21 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 17:27 [PATCH v2 0/5] SC8280XP SLPI Konrad Dybcio
2025-05-17 17:27 ` [PATCH v2 1/5] dt-bindings: remoteproc: qcom,sm8350-pas: Add SC8280XP Konrad Dybcio
2025-05-17 17:27 ` [PATCH v2 2/5] arm64: dts: qcom: sc8280xp: Fix node order Konrad Dybcio
2025-05-18 10:58 ` Dmitry Baryshkov
2025-05-17 17:27 ` [PATCH v2 3/5] arm64: dts: qcom: sc8280xp: Add SLPI Konrad Dybcio
2025-05-18 10:58 ` Dmitry Baryshkov
2025-05-17 17:27 ` [PATCH v2 4/5] arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s: enable sensors DSP Konrad Dybcio
2025-05-17 17:27 ` [PATCH v2 5/5] arm64: dts: qcom: sc8280xp-crd: Enable SLPI Konrad Dybcio
2025-05-18 10:58 ` Dmitry Baryshkov
2025-05-19 9:35 ` [PATCH v2 0/5] SC8280XP SLPI Johan Hovold
2025-05-20 14:29 ` Konrad Dybcio
2025-05-20 14:45 ` Dmitry Baryshkov
2025-05-21 7:11 ` Johan Hovold [this message]
2025-05-20 2:14 ` (subset) " 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=aC18owkQSMfNwKUC@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marijn.suijten@somainline.org \
--cc=mathieu.poirier@linaro.org \
--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