All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: <michael.nemanov@ti.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
	 Breno Leitao <leitao@debian.org>,
	 Justin Stitt <justinstitt@google.com>,
	 Kees Cook <keescook@chromium.org>,
	 <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 Sabeeh Khan <sabeeh-khan@ti.com>
Subject: Re: [PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family
Date: Thu, 23 May 2024 10:15:33 +0300	[thread overview]
Message-ID: <87msohatii.fsf@kernel.org> (raw)
In-Reply-To: <20240521171841.884576-1-michael.nemanov@ti.com> (michael nemanov's message of "Tue, 21 May 2024 20:18:24 +0300")

<michael.nemanov@ti.com> writes:

> From: Michael Nemanov <michael.nemanov@ti.com>
>
> Hello everyone,
>
> This series adds support for CC33xx which is a new family of WLAN
> IEEE802.11 a/b/g/n/ax and BLE 5.4 transceivers by Texas Instruments.
> These devices are 20MHz single spatial stream enabling STA
> (IEEE802.11ax) and AP (IEEE802.11n only) roles as well as both roles
> simultaneously. Communication to the CC33xx is done via 4-bit SDIO
> with two extra GPIOs: Enable and Interrupt.
>
> Data sheet: https://www.ti.com/lit/gpn/cc3301
>
> This driver's architecture is a soft-MAC and derivative of existing
> wl18xx + wlcore code [1]. It has been tested with the AM335x, AM625x,
> and i.MX8-MP evaluation kits.
>
> All code passes sparse and checkpatch with very few pragmatic exceptions.
>
> Known gaps to be addressed in following patches:
> 1. BLE support
>
> Test log:
> https://0x0.st/XPUd.log
>
> Change log:
> v1:
> * Added dt-bindings
> * Removed debugfs to ease review
> * Fix build issue with CONFIG_CFG80211_CERTIFICATION_ONUS
> * Fix multiple build warnings found with Clang 18 and W=12
>
> RFC: https://lore.kernel.org/linux-wireless/20240512183247.2190242-1-michael.nemanov@ti.com/
>
>
> [1] It was considered implementing CC33xx as another user of wlcore
> but The differences in HW, host interface, IRQ functionality, Rx/Tx
> behavior and supported features were too significant so this was
> abandoned.

The community (myself included) has been frustrated that TI has dropped
the ball on their existing wireless drivers:

https://docs.kernel.org/process/maintainers.html#ti-wilink-wireless-drivers

This kind of behaviour is not exactly building trust. So how is this
driver going to be any different?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

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

  parent reply	other threads:[~2024-05-23  7:15 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 17:18 [PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family michael.nemanov
2024-05-21 17:18 ` [PATCH 01/17] Add cc33xx.h, cc33xx_i.h michael.nemanov
2024-05-22  9:38   ` Krzysztof Kozlowski
2024-05-22 15:44     ` Nemanov, Michael
2024-08-06 16:56     ` Nemanov, Michael
2024-05-21 17:18 ` [PATCH 02/17] Add debug.h michael.nemanov
2024-05-21 17:18 ` [PATCH 03/17] Add sdio.c, io.c, io.h michael.nemanov
2024-05-21 17:18 ` [PATCH 04/17] Add cmd.c, cmd.h michael.nemanov
2024-05-21 17:18 ` [PATCH 05/17] Add acx.c, acx.h michael.nemanov
2024-05-21 17:18 ` [PATCH 06/17] Add event.c, event.h michael.nemanov
2024-05-21 17:18 ` [PATCH 07/17] Add boot.c, boot.h michael.nemanov
2024-05-22  8:54   ` Breno Leitao
2024-05-22 11:12     ` Krzysztof Kozlowski
2024-05-22 15:15       ` [EXTERNAL] " Nemanov, Michael
2024-05-21 17:18 ` [PATCH 08/17] Add main.c michael.nemanov
2024-05-22  8:52   ` Breno Leitao
2024-05-22  9:46   ` Krzysztof Kozlowski
2024-05-30 11:54     ` Nemanov, Michael
2024-05-30 14:37       ` Kalle Valo
2024-05-31  7:35       ` Krzysztof Kozlowski
2024-05-31 13:50         ` Nemanov, Michael
2024-06-05  9:55           ` Nemanov, Michael
2024-06-05 10:04             ` Krzysztof Kozlowski
2024-06-05 11:13               ` Kalle Valo
2024-05-21 17:18 ` [PATCH 09/17] Add rx.c, rx.h michael.nemanov
2024-05-22  8:55   ` Breno Leitao
2024-05-26  6:03     ` Nemanov, Michael
2024-05-21 17:18 ` [PATCH 10/17] Add tx.c, tx.h michael.nemanov
2024-05-21 17:18 ` [PATCH 11/17] Add init.c, init.h michael.nemanov
2024-05-21 17:18 ` [PATCH 12/17] Add scan.c, scan.h michael.nemanov
2024-05-21 17:18 ` [PATCH 13/17] Add conf.h michael.nemanov
2024-05-22  9:48   ` Krzysztof Kozlowski
2024-05-23  7:08     ` Kalle Valo
2024-05-23  7:13       ` Krzysztof Kozlowski
2024-05-23  7:18         ` Kalle Valo
2024-05-24  7:48           ` Nemanov, Michael
2024-05-21 17:18 ` [PATCH 14/17] Add ps.c, ps.h michael.nemanov
2024-05-21 17:18 ` [PATCH 15/17] Add testmode.c, testmode.h michael.nemanov
2024-05-21 17:18 ` [PATCH 16/17] Add Kconfig, Makefile and integrate into wireless/ti folder michael.nemanov
2024-05-21 17:18 ` [PATCH 17/17] Add ti,cc33xx.yaml michael.nemanov
2024-05-22  9:35   ` Krzysztof Kozlowski
2024-05-26  6:35     ` Nemanov, Michael
2024-05-23  7:15 ` Kalle Valo [this message]
2024-05-24  7:48   ` [PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Nemanov, Michael

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=87msohatii.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=johannes.berg@intel.com \
    --cc=justinstitt@google.com \
    --cc=keescook@chromium.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michael.nemanov@ti.com \
    --cc=sabeeh-khan@ti.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.