[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22c32283-768d-441e-b392-bd59a102f000@oss.qualcomm.com>
Date: Tue, 20 May 2025 17:45:31 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Johan Hovold <johan@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>
Cc: Bjorn Andersson <andersson@...nel.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Marijn Suijten <marijn.suijten@...ainline.org>,
linux-arm-msm@...r.kernel.org, linux-remoteproc@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] SC8280XP SLPI
On 20/05/2025 17:29, 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:
>
>>
>>> 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? ;)
Non-developers without Windows can extract the firmware from the
corresponding cabinet file.
--
With best wishes
Dmitry
Powered by blists - more mailing lists