From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
konradybcio@kernel.org, quic_mmanikan@quicinc.com,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: George Moussalem <george.moussalem@outlook.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v10 4/6] arm64: dts: qcom: ipq5018: add nodes to bring up q6
Date: Thu, 19 Feb 2026 11:42:43 -0800 [thread overview]
Message-ID: <62d53cdd-b71b-48f8-88d5-65407d3a80c7@oss.qualcomm.com> (raw)
In-Reply-To: <20260113092021.1887980-5-varadarajan.narayanan@oss.qualcomm.com>
On 1/13/2026 1:20 AM, Varadarajan Narayanan wrote:
> From: George Moussalem <george.moussalem@outlook.com>
>
> Enable nodes required for q6 remoteproc bring up.
I just recently became aware of this series, and have some questions...
> + q6v5_wcss: remoteproc@cd00000 {
> + compatible = "qcom,ipq5018-wcss-sec-pil";
> + reg = <0x0cd00000 0x10000>;
> + firmware-name = "ath11k/IPQ5018/hw1.0/q6_fw.mbn";
This file does not currently exist in linux-firmware.
Instead there is q6_fw.mdt with associated .b* files.
How do we transition from .mdt to .mbn given that distros update their version
of linux-firmware independently from kernel updates? Will we need to have both
the .mdt and .mbn files present for some period of time? Are there associated
changes which no longer attempt to load the .mdt files?
I ask because I've been told the ath11k/ath12k drivers will also need to
transition their firmware loading from m3_fw.mdt to m3_fw.mbn, and I'm not
sure how to make that transition.
/jeff
next prev parent reply other threads:[~2026-02-19 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 9:20 [PATCH v10 0/6] Add new driver for WCSS secure PIL loading Varadarajan Narayanan
2026-01-13 9:20 ` [PATCH v10 1/6] firmware: qcom_scm: ipq5332: add support to pass metadata size Varadarajan Narayanan
2026-01-13 9:20 ` [PATCH v10 2/6] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Varadarajan Narayanan
2026-01-13 9:20 ` [PATCH v10 3/6] remoteproc: qcom: add hexagon based WCSS secure PIL driver Varadarajan Narayanan
2026-02-12 9:37 ` Varadarajan Narayanan
2026-02-13 17:26 ` Dmitry Baryshkov
2026-01-13 9:20 ` [PATCH v10 4/6] arm64: dts: qcom: ipq5018: add nodes to bring up q6 Varadarajan Narayanan
2026-01-30 10:22 ` Konrad Dybcio
2026-02-19 19:42 ` Jeff Johnson [this message]
2026-02-20 10:36 ` Konrad Dybcio
2026-02-20 13:53 ` George Moussalem
2026-02-20 14:02 ` Konrad Dybcio
2026-02-20 18:36 ` Dmitry Baryshkov
2026-01-13 9:20 ` [PATCH v10 5/6] arm64: dts: qcom: ipq5332: " Varadarajan Narayanan
2026-01-13 9:20 ` [PATCH v10 6/6] arm64: dts: qcom: ipq9574: " Varadarajan Narayanan
2026-03-03 18:50 ` [PATCH v10 0/6] Add new driver for WCSS secure PIL loading Vignesh Viswanathan
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=62d53cdd-b71b-48f8-88d5-65407d3a80c7@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=george.moussalem@outlook.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=quic_mmanikan@quicinc.com \
--cc=robh@kernel.org \
--cc=varadarajan.narayanan@oss.qualcomm.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®