From: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: robh@kernel.org, srini@kernel.org, amahesh@qti.qualcomm.com,
krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, mathieu.poirier@linaro.org,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH V3 5/5] arm64: dts: qcom: glymur-crd: Enable ADSP and CDSP
Date: Mon, 23 Feb 2026 14:39:06 +0530 [thread overview]
Message-ID: <8d96ebc8-67e2-424d-adbc-0948dd3641a0@oss.qualcomm.com> (raw)
In-Reply-To: <yaunylao3nefmhbdovpfoymy63hjfjtvbwm5quqvdyk3enpno6@7rmpnx7esdhs>
On 2/3/2026 6:09 PM, Dmitry Baryshkov wrote:
> On Mon, Feb 02, 2026 at 11:16:19AM +0100, Konrad Dybcio wrote:
>> On 1/31/26 8:54 AM, Dmitry Baryshkov wrote:
>>> On Fri, Jan 30, 2026 at 10:55:24AM +0100, Konrad Dybcio wrote:
>>>> On 1/29/26 1:13 AM, Sibi Sankar wrote:
>>>>> Enable ADSP and CDSP on Glymur CRD board.
>>>>>
>>>>> Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
>>>>> ---
>>>>> arch/arm64/boot/dts/qcom/glymur-crd.dts | 14 ++++++++++++++
>>>>> 1 file changed, 14 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/qcom/glymur-crd.dts b/arch/arm64/boot/dts/qcom/glymur-crd.dts
>>>>> index 0899214465ac..0eed4faa8b07 100644
>>>>> --- a/arch/arm64/boot/dts/qcom/glymur-crd.dts
>>>>> +++ b/arch/arm64/boot/dts/qcom/glymur-crd.dts
>>>>> @@ -487,6 +487,20 @@ &pon_resin {
>>>>> status = "okay";
>>>>> };
>>>>>
>>>>> +&remoteproc_adsp {
>>>>> + firmware-name = "qcom/glymur/adsp.mbn",
>>>>> + "qcom/glymur/adsp_dtb.mbn";
>>>>> +
>>>>> + status = "okay";
>>>>> +};
>>>>> +
>>>>> +&remoteproc_cdsp {
>>>>> + firmware-name = "qcom/glymur/cdsp.mbn",
>>>>> + "qcom/glymur/cdsp_dtb.mbn";
>>>>> +
>>>>> + status = "okay";
>>>>> +};
>>>> Please make sure it gets to L-F (only Kaanapali is there right now)
>>>>
>>>> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>> Hmm, looking at x1e80100-crd which references qcom/x1e80100/adsp.mbn,
>>> but the firmware in linux-firmware is (now) targeting IoT devices,
>>> should we use WoA-like names for firmware on Glymur CRD instead
>>> (qcadsp-something.mbn). It would match what was done for the SC8280XP
>>> CRD.
>> I think it's simply time to stop pretending the firmware is generic
>> (some fw simply isn't and some fw may come from different/incompatible
>> branchpoints) and include a board name in the path
> Well... CDSP is usually generic, except for WP vs non-WP.
Hey Dmitry/Konrad,
Thanks for taking time to review the series :)
The ADSP/CDSP firmware that got upstreamed to linux-firmware got their
functionality tested on Glymur WP CRD devices. Given that the firmware
has already landed, can I continue to use the same name as the patch and
have a different name for other boards if something specific has to be
pushed
for IOT?
-Sibi
next prev parent reply other threads:[~2026-02-23 9:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 0:13 [PATCH V3 0/5] Enable ADSP and CDSP for Glymur SoC Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: Add Glymur ADSP Sibi Sankar
2026-02-05 10:34 ` Krzysztof Kozlowski
2026-02-23 9:36 ` Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 2/5] dt-bindings: remoteproc: qcom,sm8550-pas: Add Glymur CDSP Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 3/5] dt-bindings: misc: qcom,fastrpc: Add compatible for Glymur Sibi Sankar
2026-02-23 16:31 ` Bjorn Andersson
2026-02-24 5:54 ` Sibi Sankar
2026-01-29 0:13 ` [PATCH V3 4/5] arm64: dts: qcom: glymur: Add ADSP and CDSP for Glymur SoC Sibi Sankar
2026-01-30 9:54 ` Konrad Dybcio
2026-02-17 12:03 ` Abel Vesa
2026-01-29 0:13 ` [PATCH V3 5/5] arm64: dts: qcom: glymur-crd: Enable ADSP and CDSP Sibi Sankar
2026-01-30 9:55 ` Konrad Dybcio
2026-01-31 7:54 ` Dmitry Baryshkov
2026-02-02 10:16 ` Konrad Dybcio
2026-02-03 12:39 ` Dmitry Baryshkov
2026-02-23 9:09 ` Sibi Sankar [this message]
2026-02-23 17:14 ` Dmitry Baryshkov
2026-02-24 6:18 ` Sibi Sankar
2026-02-24 6:30 ` Dmitry Baryshkov
2026-02-24 9:38 ` Sibi Sankar
2026-02-17 12:02 ` Abel Vesa
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=8d96ebc8-67e2-424d-adbc-0948dd3641a0@oss.qualcomm.com \
--to=sibi.sankar@oss.qualcomm.com \
--cc=amahesh@qti.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--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=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=srini@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