From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] wifi: ath11k: add support for QCA2066
Date: Tue, 09 Jan 2024 14:21:50 +0200 [thread overview]
Message-ID: <87frz6ely9.fsf@kernel.org> (raw)
In-Reply-To: <20240109021336.4143-1-quic_bqiang@quicinc.com> (Baochen Qiang's message of "Tue, 9 Jan 2024 10:13:34 +0800")
Baochen Qiang <quic_bqiang@quicinc.com> writes:
> QCA2066 is a PCI based DBS device. It is very similar to WCN6855
> overall: they share the same PCI device ID, the same major and
> minor version numbers, the same register address, and same HAL
> descriptors etc. The most significant difference is that QCA2066
> supports 3-antenna configuration while WCN6855 doesn't. To
> differentiate them, subversion numbers are used. Currently four
> numbers are used by QCA2066: 0x1019A0E1, 0x1019B0E1, 0x1019C0E1
> and 0x1019D0E1.
>
> In order to read subversion register, pci.ops needs to be ready
> at that time, this change is done in the first patch.
>
> The second patch enables support for QCA2066.
>
> v2:
> - Rebased on ToT.
And the firmware is now available here:
https://github.com/kvalo/ath11k-firmware/tree/master/QCA2066/hw2.1
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-01-09 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 2:13 [PATCH v2 0/2] wifi: ath11k: add support for QCA2066 Baochen Qiang
2024-01-09 2:13 ` [PATCH v2 1/2] wifi: ath11k: move pci.ops registration ahead Baochen Qiang
2024-02-15 11:24 ` Kalle Valo
2024-01-09 2:13 ` [PATCH v2 2/2] wifi: ath11k: add support for QCA2066 Baochen Qiang
2024-01-09 17:41 ` Jeff Johnson
2024-01-10 2:16 ` Baochen Qiang
2024-01-10 16:20 ` Jeff Johnson
2024-01-11 17:04 ` Kalle Valo
2024-01-12 14:38 ` Konstantin Ryabitsev
2024-01-12 15:46 ` Kalle Valo
2024-01-09 12:21 ` 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=87frz6ely9.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@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