Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Christoph Niedermaier <cniedermaier@dh-electronics.com>
To:     "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
CC:     "ajay.kathat@microchip.com" <ajay.kathat@microchip.com>,
        "claudiu.beznea@microchip.com" <claudiu.beznea@microchip.com>,
        "tudor.ambarus@microchip.com" <tudor.ambarus@microchip.com>,
        "Andreas Geisreiter" <ageisreiter@dh-electronics.com>,
        "Marek MV. Vasut" <marex@denx.de>
Subject: Possible bug on wilc1000 [Klartext]
Thread-Topic: Possible bug on wilc1000 [Klartext]
Thread-Index: AdgdBYpowDRGmRhhS4ylc9cEzwODUw==
Date:   Tue, 8 Feb 2022 16:26:07 +0000
Message-ID: <3994a34bb0d84e9d8181ec490a3f71d2@dh-electronics.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk

Hello,

I tested the wireless chip wilc1000 with the 5.16.5 Kernel and the firmware=
 v15.4.1
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gi=
t/tree/atmel/wilc1000_wifi_firmware-1.bin)
on an i.MX6 QUAD with iperf3:

# iperf3 -c IP_ADDR -P 16 -t 0=20

After a while the test gets stuck and I got the following kernel messages:
mmc0: Timeout waiting for hardware interrupt.
mmc0: sdhci: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D SDHCI REGISTER DUMP =3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
mmc0: sdhci: Sys addr:  0x138f0200 | Version:  0x00000002
mmc0: sdhci: Blk size:  0x00000158 | Blk cnt:  0x00000001
mmc0: sdhci: Argument:  0x14000158 | Trn mode: 0x00000013
mmc0: sdhci: Present:   0x01d88a0a | Host ctl: 0x00000013
mmc0: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
mmc0: sdhci: Wake-up:   0x00000008 | Clock:    0x0000009f
mmc0: sdhci: Timeout:   0x0000008f | Int stat: 0x00000000
mmc0: sdhci: Int enab:  0x107f100b | Sig enab: 0x107f100b
mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000003
mmc0: sdhci: Caps:      0x07eb0000 | Caps_1:   0x0000a000
mmc0: sdhci: Cmd:       0x0000353a | Max curr: 0x00ffffff
mmc0: sdhci: Resp[0]:   0x00001000 | Resp[1]:  0x00000000
mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
mmc0: sdhci: Host ctl2: 0x00000000
mmc0: sdhci: ADMA Err:  0x00000007 | ADMA Ptr: 0x4c041200
mmc0: sdhci-esdhc-imx: =3D=3D=3D=3D=3D=3D=3D=3D=3D ESDHC IMX DEBUG STATUS D=
UMP =3D=3D=3D=3D=3D=3D=3D=3D=3D
mmc0: sdhci-esdhc-imx: cmd debug status:  0x2100
mmc0: sdhci-esdhc-imx: data debug status:  0x2200
mmc0: sdhci-esdhc-imx: trans debug status:  0x2300
mmc0: sdhci-esdhc-imx: dma debug status:  0x2402
mmc0: sdhci-esdhc-imx: adma debug status:  0x25b4
mmc0: sdhci-esdhc-imx: fifo debug status:  0x2610
mmc0: sdhci-esdhc-imx: async fifo debug status:  0x2751
mmc0: sdhci: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
wilc1000_sdio mmc0:0001:1: wilc_sdio_cmd53..failed, err(-110)
wilc1000_sdio mmc0:0001:1: Failed cmd53 [0], bytes read...

I tried to reduce the clock speed to 20MHz in the devicetree with
max-frequency =3D <20000000>;
but the problem then also occurs.

Is this a possible bug?


Thanks in advance and best regards
Christoph