[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87msohatii.fsf@kernel.org>
Date: Thu, 23 May 2024 10:15:33 +0300
From: Kalle Valo <kvalo@...nel.org>
To: <michael.nemanov@...com>
Cc: Johannes Berg <johannes.berg@...el.com>, Breno Leitao
<leitao@...ian.org>, Justin Stitt <justinstitt@...gle.com>, Kees Cook
<keescook@...omium.org>, <linux-wireless@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Sabeeh Khan <sabeeh-khan@...com>
Subject: Re: [PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx
wireless device family
<michael.nemanov@...com> writes:
> From: Michael Nemanov <michael.nemanov@...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
Powered by blists - more mailing lists