linux-kernel - mmc: host: sdhci-esdhc-imx: async sdio interrupt and hardware auto-tuning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <a0bc23f0d7c4996b208c46508f9981a5804ab94d.camel@toradex.com>
Date:   Wed, 2 Nov 2022 20:43:25 +0000
From:   Marcel Ziswiler <marcel.ziswiler@...adex.com>
To:     "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "linux-imx@....com" <linux-imx@....com>,
        "kernel@...gutronix.de" <kernel@...gutronix.de>,
        "s.hauer@...gutronix.de" <s.hauer@...gutronix.de>,
        "haibo.chen@....com" <haibo.chen@....com>,
        "ulf.hansson@...aro.org" <ulf.hansson@...aro.org>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        "adrian.hunter@...el.com" <adrian.hunter@...el.com>,
        "festevam@...il.com" <festevam@...il.com>
Subject: mmc: host: sdhci-esdhc-imx: async sdio interrupt and hardware
 auto-tuning

Hi there

When we investigated an SDIO Wi-Fi stability issue I discovered the
following downstream-only commit in NXP's latest downstream BSP
5.15.52_2.1.0 [1]. The asynchronous SDIO interrupt seems to adversly
affect the hardware auto-tuning. As a workaround what got implemented
is an fsl-custom device tree property that limits the auto-tuning to
1 bit only (e.g. on DAT[0]) while the SDIO interrupt stays on DAT[1].

Does anybody know any further details about this?

Would this be a reasonable thing to also implement upstream?

Unfortunately, so far we have not really done any extensive SDIO
validation using upstream but I plan to set something like that up so
we may see whether or not we are also hitting such issue.

Thanks!

[1] https://github.com/nxp-imx/linux-imx/commit/84c529a1474a9f6614e475e178ca5fe23b6177de

Cheers

Marcel