From: "Sireesh Kodali" <sireeshkodali1@gmail.com>
To: "Loic Poulain" <loic.poulain@linaro.org>
Cc: <wcn36xx@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<netdev@vger.kernel.org>, <~postmarketos/upstreaming@lists.sr.ht>,
<linux-kernel@vger.kernel.org>,
"Vladimir Lypak" <vladimir.lypak@gmail.com>,
"Kalle Valo" <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>
Subject: Re: [PATCH 1/1] net: wireless: ath: wcn36xx: add support for pronto-v3
Date: Tue, 14 Mar 2023 23:34:37 +0530 [thread overview]
Message-ID: <CR6AZI7T6X51.AX26VA80VSUW@skynet-linux> (raw)
In-Reply-To: <CAMZdPi_uBLutBejSV1fz5p9GYqHYd75VTAePtndUnsu=JypdTQ@mail.gmail.com>
On Tue Mar 14, 2023 at 2:19 PM IST, Loic Poulain wrote:
> On Sat, 11 Mar 2023 at 16:07, Sireesh Kodali <sireeshkodali1@gmail.com> wrote:
> >
> > From: Vladimir Lypak <vladimir.lypak@gmail.com>
> >
> > Pronto v3 has a different DXE address than prior Pronto versions. This
> > patch changes the macro to return the correct register address based on
> > the pronto version.
> >
> > Signed-off-by: Vladimir Lypak <vladimir.lypak@gmail.com>
> > Signed-off-by: Sireesh Kodali <sireeshkodali1@gmail.com>
>
> Acked-by: Loic Poulain <loic.poulain@linaro.org>
>
> Could you also submit a change for the new 'qcom,pronto-v3-pil'
> compatible in the related devicetree documentation ?
> (bindings/remoteproc/qcom,wcnss-pil.txt)
The changes to the device tree were only recently merged
LKML link: https://lkml.org/lkml/2022/9/30/1502
next prev parent reply other threads:[~2023-03-14 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 15:06 [PATCH 0/1] net: wireless: wcn36xx: Add support for pronto-v3 Sireesh Kodali
2023-03-11 15:06 ` [PATCH 1/1] net: wireless: ath: wcn36xx: add " Sireesh Kodali
2023-03-13 5:52 ` Kalle Valo
2023-03-14 3:55 ` Sireesh Kodali
2023-03-14 8:49 ` Loic Poulain
2023-03-14 18:04 ` Sireesh Kodali [this message]
2023-03-14 18:42 ` Loic Poulain
2023-03-15 10:15 ` Kalle Valo
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=CR6AZI7T6X51.AX26VA80VSUW@skynet-linux \
--to=sireeshkodali1@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.lypak@gmail.com \
--cc=wcn36xx@lists.infradead.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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