From: Kalle Valo <kvalo@kernel.org>
To: Miaoqing Pan <quic_miaoqing@quicinc.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
<quic_jjohnson@quicinc.com>, <ath11k@lists.infradead.org>,
<linux-wireless@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <quic_zhichen@quicinc.com>
Subject: Re: [PATCH v2 2/2] wifi: ath11k: support board-specific firmware overrides
Date: Thu, 07 Nov 2024 19:31:56 +0200 [thread overview]
Message-ID: <871pzn54s3.fsf@kernel.org> (raw)
In-Reply-To: <3dd897cb-5cc3-409d-a310-66e71847d58f@quicinc.com> (Miaoqing Pan's message of "Fri, 1 Nov 2024 09:32:37 +0800")
Miaoqing Pan <quic_miaoqing@quicinc.com> writes:
>>>>>> Understand your concern, automatic adaptation is always the best
>>>>>> choice. But
>>>>>> it may not work for MSM boards, the PCIe card (non m.2) is
>>>>>> customized, which
>>>>>> has special PMU control. User can't swap cards. And that's why power
>>>>>> sequencing module was introduced.
>>>>>
>>>>> I know. Still, it's better to have less unnecessary data there for
>>>>> autodiscoverable devices.
>>>>
>>>
>>> We discussed internally, we have no other choice to enable NFA765 for non
>>> X86 boards. Could you please approve this 'DT' approach ?
>> If you can't use subdevice approach for some reason, then we have no
>> other choice that I can imagine.
>>
>
> A new patch was submitted:
> https://lore.kernel.org/linux-wireless/20241031000541.3331606-1-quic_miaoqing@quicinc.com/.
> This patch will add QCA6698AQ support, which follows the approach done
> in commit 5dc9d1a55e95 ("wifi: ath11k: add support for QCA2066"),
> enumerates the subversion number to identify the specific card.
>
> But there is still a problem enabling NFA765 m.2 card for IoT
> platforms, which requires ath11k to support board-specific firmware
> overrides.
So there are multiple different hardware you want to support? This is
very confusing and the commit message does not really tell anything
about those. Can you list _all_ the hardware you want to support and
what firmware it needs?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-11-07 17:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 0:25 [PATCH v2 0/2] wifi: ath11k: support board-specific firmware overrides Miaoqing Pan
2024-10-24 0:25 ` [PATCH v2 1/2] dt-bindings: net: wireless: ath11k-pci: add firmware-name property Miaoqing Pan
2024-10-24 6:43 ` Krzysztof Kozlowski
2024-10-24 0:25 ` [PATCH v2 2/2] wifi: ath11k: support board-specific firmware overrides Miaoqing Pan
2024-10-24 19:39 ` Dmitry Baryshkov
2024-10-25 2:56 ` Miaoqing Pan
2024-10-25 6:01 ` Dmitry Baryshkov
2024-10-25 7:22 ` Miaoqing Pan
2024-10-25 10:20 ` Dmitry Baryshkov
2024-10-25 12:03 ` Miaoqing Pan
2024-10-25 12:21 ` Dmitry Baryshkov
2024-10-25 13:43 ` Miaoqing Pan
2024-10-25 14:01 ` Dmitry Baryshkov
2024-10-25 14:23 ` Miaoqing Pan
2024-10-25 15:27 ` Dmitry Baryshkov
2024-10-26 2:31 ` Miaoqing Pan
2024-10-28 10:32 ` Miaoqing Pan
2024-10-28 13:45 ` Dmitry Baryshkov
2024-11-01 1:32 ` Miaoqing Pan
2024-11-07 17:31 ` Kalle Valo [this message]
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=871pzn54s3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_miaoqing@quicinc.com \
--cc=quic_zhichen@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.