LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
An?bal Lim?n <anibal.limon@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: db410c: Update firmware-name for wcnss and mpss
Date: Tue, 24 Aug 2021 07:46:04 -0700 [thread overview]
Message-ID: <YSUGLFx2QST9vgIU@ripper> (raw)
In-Reply-To: <CAA8EJpqXyQCFGgTRk+dqxD6TdJycLeGx4EQ0OBov5_3hVogM1g@mail.gmail.com>
On Tue 24 Aug 05:39 PDT 2021, Dmitry Baryshkov wrote:
> On Thu, 18 Feb 2021 at 01:38, Aníbal Limón <anibal.limon@linaro.org> wrote:
> >
> > From: Bjorn Andersson <bjorn.andersson@linaro.org>
> >
> > Enable the mpss remoteproc node and specify the firmware-name for this
> > and the wcnss remoteproc on the Dragonboard 410c.
> >
> > Link: https://lore.kernel.org/r/20200108055735.660475-1-bjorn.andersson@linaro.org
> > Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> > [rebased and moved to use pronto label]
> > Signed-off-by: Vinod Koul <vkoul@kernel.org>
> > Tested-by: Aníbal Limón <anibal.limon@linaro.org>
>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>
Thanks Dmitry, not sure why this hasn't been merged yet.
Taking a further look at this I noticed that we never pushed the
firmware to linux-firmware either, which I think was because we where
uncertain of the directory structure at the time - a discussion which
has been settled since.
> > ---
> > arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi b/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi
> > index 3c7f97539390..8f1ada75d3ed 100644
> > --- a/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi
> > @@ -301,6 +301,11 @@ &lpass {
> > status = "okay";
> > };
> >
> > +&mpss {
> > + status = "okay";
> > + firmware-name = "qcom/msm8916/mba.mbn", "qcom/msm8916/modem.mdt";
But if we're pushing things to linux-firmware, does anyone object
against following the existing style and squashing the mdt+bNN files
into .mbn (and thereby making this modem.mbn and below wcnss.mbn)?
Regards,
Bjorn
> > +};
> > +
> > &pm8916_resin {
> > status = "okay";
> > linux,code = <KEY_VOLUMEDOWN>;
> > @@ -308,6 +313,7 @@ &pm8916_resin {
> >
> > &pronto {
> > status = "okay";
> > + firmware-name = "qcom/msm8916/wcnss.mdt";
> > };
> >
> > &sdhc_1 {
> > --
> > 2.30.0
> >
>
>
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2021-08-24 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 5:57 Bjorn Andersson
2021-02-17 22:34 ` Aníbal Limón
2021-02-18 4:19 ` Vinod Koul
2021-08-24 12:38 ` Dmitry Baryshkov
2021-08-24 12:39 ` Dmitry Baryshkov
2021-08-24 14:46 ` Bjorn Andersson [this message]
2021-08-24 15:49 ` Stephan Gerhold
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=YSUGLFx2QST9vgIU@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=anibal.limon@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--subject='Re: [PATCH] arm64: dts: qcom: db410c: Update firmware-name for wcnss and mpss' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).