From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Yongqin Liu <yongqin.liu@linaro.org>
Subject: Re: [PATCH 0/3] wifi: ath10k: fix board file loading for wcn3990 devices
Date: Fri, 5 Apr 2024 16:06:48 +0300 [thread overview]
Message-ID: <CAA8EJprZTdDZZ=NSzn9xEBGB0kp0s1HHLffF0X7YSLyVxy7ZSw@mail.gmail.com> (raw)
In-Reply-To: <875xww3tv8.fsf@kernel.org>
On Fri, 5 Apr 2024 at 14:57, Kalle Valo <kvalo@kernel.org> wrote:
>
> Dmitry Baryshkov <dmitry.baryshkov@linaro.org> writes:
>
> > On Tue, 30 Jan 2024 at 08:47, Dmitry Baryshkov
> > <dmitry.baryshkov@linaro.org> wrote:
> >
> >>
> >> The ath10k driver fails to properly handle fallback from board-2.bin to
> >> board.bin for WCN3990 cards. This happens because the
> >> ath10k_hw_params_list doesn't include .fw.board* parameters for the
> >> WCN3990 platform.
> >>
> >> Add board data configuration for WCN3990. While we are at it, merge
> >> common pieces of BDF support: drop .board and .eboard names from struct
> >> ath10k_hw_params_fw and use the common name instead.
> >>
> >> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> >> ---
> >> Dmitry Baryshkov (3):
> >> wifi: ath10k: populate board data for WCN3990
> >> wifi: ath10k: drop chip-specific board data file name
> >> wifi: ath10k: drop fw.eboard file name
> >>
> >> drivers/net/wireless/ath/ath10k/core.c | 32 ++++-------------------------
> >> drivers/net/wireless/ath/ath10k/hw.h | 14 ++-----------
> >> drivers/net/wireless/ath/ath10k/pci.c | 10 ++++-----
> >> drivers/net/wireless/ath/ath10k/targaddrs.h | 3 +++
> >> 4 files changed, 14 insertions(+), 45 deletions(-)
> >> ---
> >> base-commit: 596764183be8ebb13352b281a442a1f1151c9b06
> >> change-id: 20240129-wcn3990-board-fw-a2d97507a712
> >
> > Kalle, Jeff, is there anything pending on me on this series?
>
> This is in my queue (Deferred state):
>
> https://patchwork.kernel.org/project/linux-wireless/list/?series=821157&state=*&order=date
>
> Unfortunately there is not really much time for ath10k nowadays so there
> will be delays.
No problems, each maintainer treats PW states slightly differently, so
I was trying to understand if there is anything left on my side.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2024-04-05 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 6:47 [PATCH 0/3] wifi: ath10k: fix board file loading for wcn3990 devices Dmitry Baryshkov
2024-01-30 6:47 ` [PATCH 1/3] wifi: ath10k: populate board data for WCN3990 Dmitry Baryshkov
2024-04-25 10:22 ` Kalle Valo
2024-01-30 6:47 ` [PATCH 2/3] wifi: ath10k: drop chip-specific board data file name Dmitry Baryshkov
2024-01-30 6:47 ` [PATCH 3/3] wifi: ath10k: drop fw.eboard " Dmitry Baryshkov
2024-02-12 20:55 ` [PATCH 0/3] wifi: ath10k: fix board file loading for wcn3990 devices Jeff Johnson
2024-03-30 4:48 ` Dmitry Baryshkov
2024-04-02 23:41 ` Jeff Johnson
2024-04-05 11:56 ` Kalle Valo
2024-04-05 13:06 ` Dmitry Baryshkov [this message]
2024-04-05 13:11 ` Kalle Valo
2024-04-24 13:33 ` 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='CAA8EJprZTdDZZ=NSzn9xEBGB0kp0s1HHLffF0X7YSLyVxy7ZSw@mail.gmail.com' \
--to=dmitry.baryshkov@linaro.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=yongqin.liu@linaro.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;
as well as URLs for NNTP newsgroup(s).