[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM1KZSnvDqUHd2ENKyaZc=WyRgL18TrsF766_ZJVeeAiPth+Vw@mail.gmail.com>
Date: Tue, 29 Apr 2025 18:38:20 +0200
From: Ezra Buehler <ezra@...yb.ch>
To: Michael Nemanov <michael.nemanov@...com>
Cc: Kalle Valo <kvalo@...nel.org>, "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Sabeeh Khan <sabeeh-khan@...com>
Subject: Re: [PATCH v5 00/17] wifi: cc33xx: Add driver for new TI CC33xx
wireless device family
Hi Michael,
On Thu, Nov 7, 2024 at 1:51 PM Michael Nemanov <michael.nemanov@...com> wrote:
> 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.
Thanks for going through the effort of upstreaming the driver.
We have started looking into the CC33xx chips (in conjunction with the
AM62L SoC) and noticed the following behavior:
# curl https://speedtest.init7.net/1GB.dd >/dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
4 1024M 4 42.4M 0 0 2358k 0 0:07:24 0:00:18 0:07:06 0
After downloading some megabytes of data, with reasonable speed,
something seems to lock up and no further communication is possible
through the Wi-Fi interface.
AFAICT nothing is logged, however, when I unload the driver, I see errors
like:
[16590.256433] cc33xx: ERROR failed to initiate cmd role disable
[16590.256446] cc33xx: CC33xx driver attempting recovery
[16590.256455] cc33xx: Driver being removed, recovery disabled
[16590.272950] wlan0: deauthenticating from ab:cd:ef:01:23:45 by local
choice (Reason: 3=DEAUTH_LEAVING)
[16590.784390] cc33xx: WARNING Unable to flush all TX buffers, timed
out (timeout 500 ms
[16591.296388] cc33xx: WARNING Unable to flush all TX buffers, timed
out (timeout 500 ms
[16591.808379] cc33xx: WARNING Unable to flush all TX buffers, timed
out (timeout 500 ms
[16591.816792] wlan0: failed to remove key (0, ab:cd:ef:01:23:45) from
hardware (-11)
[16593.840379] cc33xx: WARNING CONFIGURE command NOK
[16593.845172] cc33xx: WARNING tx param cfg failed: -5
[16595.856352] cc33xx: WARNING CONFIGURE command NOK
[16595.861159] cc33xx: WARNING tx param cfg failed: -5
[16597.872323] cc33xx: WARNING CONFIGURE command NOK
[16597.877079] cc33xx: WARNING tx param cfg failed: -5
[16599.888317] cc33xx: WARNING CONFIGURE command NOK
[16599.893069] cc33xx: WARNING tx param cfg failed: -5
[16600.400303] cc33xx: WARNING Unable to flush all TX buffers, timed
out (timeout 500 ms
[16600.912270] cc33xx: WARNING Unable to flush all TX buffers, timed
out (timeout 500 ms
[16600.920388] wlan0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from
hardware (-11)
We can easily reproduce this behavior on our ATMDS62LEVM board in
conjunction with the M2-CC3351 card. We run a Yocto-based distribution
(Scarthgap) using the latest linux-ti-staging-6.12 kernel recipe (Linux
6.12.17+).
So far, I haven't tried to dig into this deeper. Any ideas on how to
debug this further?
Cheers,
Ezra.
Powered by blists - more mailing lists