devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 00/49] ath11k: driver for Qualcomm IEEE 802.11ax devices
Date: Sat, 23 Nov 2019 08:26:41 +0000	[thread overview]
Message-ID: <0101016e975ec74d-5c7043cf-f7c1-4301-939a-783203f9c80d-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <1573810153-29623-1-git-send-email-kvalo@codeaurora.org> (Kalle Valo's message of "Fri, 15 Nov 2019 11:28:24 +0200")

Kalle Valo <kvalo@codeaurora.org> writes:

> ath11k is a new driver for Qualcomm IEEE 802.11ax devices, first
> supporting only IPQ8074 SoC using the shared memory AHB bus. ath11k
> uses mac80211 and supports AP, Station and Mesh modes.
>
> Even though ath11k has some similar code as with ath10k (especially
> the WMI layer) it was concluded to be simpler to have a "clean start"
> for ath11k code base and not try to share the code with ath10k. This
> makes maintenance easier and avoids major changes in ath10k, which
> would have significantly increased the risk of regressions in existing
> setups.
>
> Even though the driver is very similar with ath10k but there are major
> differences as well. The datapath is completely different. ath11k
> supports multiple MACs, called "soc" in the firmware interface. And
> there's only one WMI interface to support.
>
> Currently ath11k supports only IEEE 802.11ac mode, but patches for
> 802.11ax are available and they will be submitted after ath11k is
> accepted to upstream.
>
> The firmware images are available from ath11k-firmware repository but
> they will be also submitted to linux-firmware:
>
> https://github.com/kvalo/ath11k-firmware

I also added to the commit log the version which was used in testing:

WLAN.HK.2.1.0.1-00629-QCAHKSWPL_SILICONZ-1

> --------------[cut]-------------------[cut]-----------------
>
> I have split the driver into multiple patches for easier review, but
> the final version will be split into three commits:
>
> 1. adding Documentatio/devicetree/bindings/net/wireless/qcom,ath11k.yaml
>
> 2. adding drivers/net/wireless/ath/ath11k/ with the commit log being the
>    text before the cut line above.
>
> 3. adding ath11k entry to MAINTAINERS file
>
> This version is based on commit ad10d2ff619f0797cb102b2ff488429d3f8e4a8a
> from ath11k-bringup branch on my ath.git tree:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=ath11k-bringup
>
> This patchset applies to wireless-drivers-next but needs
> CONFIG_COMPILE_TEST, CONFIG_REMOTEPROC AND CONFIG_QCOM_QMI_HELPERS to
> be able to compile on x86.
>
> Please review and comment.

I have now prepared the three commits and they are in the pending
branch for build testing:

https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=20bddf19da715842fe24c8e9990ae1b75825c747

https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=461a5c86cfa562bd3c4a8f6bec9a54c406540e87

https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=8710785df81b8b57e62a71e9048c111a7db98005

In the next few days I'll apply these to ath-next branch and queue for v5.6.

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2019-11-23  8:26 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  9:28 [PATCH v3 00/49] ath11k: driver for Qualcomm IEEE 802.11ax devices Kalle Valo
2019-11-15  9:28 ` [PATCH v3 01/49] dt: bindings: net: add qcom,ath11k.yaml Kalle Valo
2019-11-23  0:23   ` Rob Herring
2019-11-15  9:28 ` [PATCH v3 02/49] ath11k: add Kconfig Kalle Valo
2019-11-15  9:28 ` [PATCH v3 03/49] ath11k: add Makefile Kalle Valo
2019-11-15  9:28 ` [PATCH v3 04/49] ath11k: add ahb.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 05/49] ath11k: add ahb.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 06/49] ath11k: add ce.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 07/49] ath11k: add ce.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 08/49] ath11k: add core.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 09/49] ath11k: add core.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 10/49] ath11k: add debug.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 11/49] ath11k: add debug.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 12/49] ath11k: add debug_htt_stats.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 13/49] ath11k: add debug_htt_stats.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 14/49] ath11k: add debugfs_sta.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 15/49] ath11k: add dp.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 16/49] ath11k: add dp.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 17/49] ath11k: add dp_rx.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 18/49] ath11k: add dp_rx.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 19/49] ath11k: add dp_tx.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 20/49] ath11k: add dp_tx.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 21/49] ath11k: add hal.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 22/49] ath11k: add hal.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 23/49] ath11k: add hal_desc.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 24/49] ath11k: add hal_rx.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 25/49] ath11k: add hal_rx.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 26/49] ath11k: add hal_tx.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 27/49] ath11k: add hal_tx.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 28/49] ath11k: add htc.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 29/49] ath11k: add htc.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 30/49] ath11k: add hw.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 31/49] ath11k: add mac.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 32/49] ath11k: add mac.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 33/49] ath11k: add peer.c Kalle Valo
2019-11-15  9:28 ` [PATCH v3 34/49] ath11k: add peer.h Kalle Valo
2019-11-15  9:28 ` [PATCH v3 35/49] ath11k: add qmi.c Kalle Valo
2019-11-15  9:29 ` [PATCH v3 36/49] ath11k: add qmi.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 37/49] ath11k: add reg.c Kalle Valo
2019-11-15  9:29 ` [PATCH v3 38/49] ath11k: add reg.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 39/49] ath11k: add rx_desc.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 40/49] ath11k: add testmode.c Kalle Valo
2019-11-15  9:29 ` [PATCH v3 41/49] ath11k: add testmode.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 42/49] ath11k: add testmode_i.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 43/49] ath11k: add trace.c Kalle Valo
2019-11-15  9:29 ` [PATCH v3 44/49] ath11k: add trace.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 45/49] ath11k: add wmi.c Kalle Valo
2019-11-15  9:29 ` [PATCH v3 46/49] ath11k: add wmi.h Kalle Valo
2019-11-15  9:29 ` [PATCH v3 47/49] ath: add ath11k to Makefile Kalle Valo
2019-11-15  9:29 ` [PATCH v3 48/49] ath: add ath11k to Kconfig Kalle Valo
2019-11-15  9:29 ` [PATCH v3 49/49] MAINTAINERS: add ath11k Kalle Valo
2019-11-23  8:26 ` Kalle Valo [this message]
2019-11-25 12:31   ` [PATCH v3 00/49] ath11k: driver for Qualcomm IEEE 802.11ax devices 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=0101016e975ec74d-5c7043cf-f7c1-4301-939a-783203f9c80d-000000@us-west-2.amazonses.com \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.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).