Received-SPF: pass (google.com: domain of linux-wireless+bounces-8802-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <ee08c815-9389-4277-be6d-197511636892@linutronix.de>
Date: Tue, 11 Jun 2024 17:54:09 +0200
Precedence: bulk
MIME-Version: 1.0
Content-Language: de-DE
To: Ping-Ke Shih <pkshih@realtek.com>,
 Bitterblue Smith <rtl8821cerfe2@gmail.com>
Cc: linux-wireless@vger.kernel.org
From: Martin Kaistra <martin.kaistra@linutronix.de>
Subject: ETIMEDOUT with rtl8xxxu
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Ping-Ke, hi Bitterblue,

I have a problem with the rtl8xxxu driver and 8188f, but only on some boards. 
More specifically, I can see that during the second channel switch (which 
happens when I do "iw dev wlan0 scan"),  the rtl8xxxu_read32(0e08) returns -110 
(ETIMEDOUT) and after that no reads or writes work anymore until I unload and 
reload the driver.

The strange thing now is, that even though it seems to be hardware dependent the 
vendor driver does not have this problem.

I tried to change the probe and start functions, so that they behaved exactly as 
their vendor driver equivalents, but so far I don't see any improvement.

I was hoping, that one of you maybe has an idea, what could be causing such an 
issue and how to avoid it.

Martin