From: Miaoqing Pan <quic_miaoqing@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <kvalo@kernel.org>, <quic_jjohnson@quicinc.com>,
<ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] wifi: ath11k: add firmware-name device tree property
Date: Tue, 22 Oct 2024 18:20:50 +0800 [thread overview]
Message-ID: <1c5f5c93-db06-4490-af2e-bbce2d184c94@quicinc.com> (raw)
In-Reply-To: <smgbishqbin4kcpshqvue3ivvfko2l6rj2w4ikwydosbkq6kde@pdbzhklj7znm>
On 10/22/2024 5:57 PM, Dmitry Baryshkov wrote:
> On Tue, Oct 01, 2024 at 11:30:52AM +0800, Miaoqing Pan wrote:
>> QCA6698AQ uses different firmware/bdf/regdb with existing WCN6855
>> firmware, which is customized for IoE platforms. And the 'pci-device-id +
>> soc-hw-version + soc-hw-sub-version' may not be enough to identify the
>> correct firmware directory path.
>
> Why is it so? What makes it so different from the existing platforms
> that you can not use WCN6855 firmware?
Just as I said, a new customized firmware for IoE devices.
>
>>
>> The device tree allows "firmware-name" to define the firmware path,
>> wifi@c000000 {
>
> You are describing platform node, while the commit message talks about
> the PCIe devices. Could you please clarify, whether it is a PCIe device
> or an AHB device?
PCIe device. The change is for sa8775p/qcs8300 those non-AHB boards.
>
>> firmware-name = "QCA6698AQ";
>
> Could we please follow the approach that has been defined in the commit
> 5abf259772df ("wifi: ath10k: support board-specific firmware
> overrides")? In other words, instead of creating another directory under
> ath11k, create a subdir under the WCN6855/hwN.M/ which contains your
> device-specific data.
Sure, thanks, will update.
>
>> status = "okay";
>> };
>>
>> Tested-on: QCA6698AQ hw2.1 PCI WLAN.HSP.1.1-04402-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
>>
>> Signed-off-by: Miaoqing Pan <quic_miaoqing@quicinc.com>
>
> P.S. please CC linux-arm-msm for future respins of this series or for
> all other submissions that concern board-specific DT data on MSM
> platforms.
ok.
>
>> ---
>> drivers/net/wireless/ath/ath11k/core.c | 12 ++++++++++++
>> drivers/net/wireless/ath/ath11k/core.h | 11 +++--------
>> 2 files changed, 15 insertions(+), 8 deletions(-)
>>
>
next prev parent reply other threads:[~2024-10-22 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 3:30 [PATCH 0/2] add firmware-name device tree property for ath11k Miaoqing Pan
2024-10-01 3:30 ` [PATCH 1/2] dt-bindings: net: wireless: ath11k: add firmware-name property Miaoqing Pan
2024-10-01 16:30 ` Conor Dooley
2024-10-01 3:30 ` [PATCH 2/2] wifi: ath11k: add firmware-name device tree property Miaoqing Pan
2024-10-22 9:57 ` Dmitry Baryshkov
2024-10-22 10:20 ` Miaoqing Pan [this message]
2024-10-22 13:55 ` Dmitry Baryshkov
2024-10-22 15:58 ` 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=1c5f5c93-db06-4490-af2e-bbce2d184c94@quicinc.com \
--to=quic_miaoqing@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@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 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®