From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Komal Bajaj <quic_kbajaj@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: dts: qcom: qcm6490-idp: Enable various remoteprocs
Date: Wed, 20 Dec 2023 13:27:54 +0100 [thread overview]
Message-ID: <5266f13f-7dfb-4fc4-b9e2-50680dab4c84@linaro.org> (raw)
In-Reply-To: <CAA8EJppYuXpqKpTcUda1LBFfBmm40-VpC+3heJqoL82kS=+erA@mail.gmail.com>
On 20/12/2023 13:18, Dmitry Baryshkov wrote:
>> I don't see these files in linux-firmware and your cover letter did not
>> explain anything around their submission. What's the status on that part?
>
> This isn't usually required, is it? I mean, the firmware can come from
> linux-firmware, from the device partition or in any other way. With
> the FW_LOADER_USER_HELPER this becomes just the key string used to
> identify firmware to be loaded.
No, it is not required, but anyway it is a good time to ask that question.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-20 12:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 11:42 [PATCH 0/2] Enable various remoteprocs for qcm6490-idp and qcs6490-rb3gen2 Komal Bajaj
2023-12-20 11:42 ` [PATCH 1/2] arm64: dts: qcom: qcm6490-idp: Enable various remoteprocs Komal Bajaj
2023-12-20 11:45 ` Krzysztof Kozlowski
2023-12-20 12:18 ` Dmitry Baryshkov
2023-12-20 12:27 ` Krzysztof Kozlowski [this message]
2023-12-20 12:29 ` Konrad Dybcio
2023-12-20 12:34 ` Dmitry Baryshkov
2023-12-22 13:24 ` Komal Bajaj
2023-12-22 14:26 ` Dmitry Baryshkov
2023-12-20 11:42 ` [PATCH 2/2] arm64: dts: qcom: qcs6490-rb3gen2: " Komal Bajaj
2023-12-20 12:14 ` Dmitry Baryshkov
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=5266f13f-7dfb-4fc4-b9e2-50680dab4c84@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®