[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SN6PR04MB4925C1C304B992339621808AFC260@SN6PR04MB4925.namprd04.prod.outlook.com>
Date: Thu, 18 Apr 2019 06:20:26 +0000
From: Avri Altman <Avri.Altman@....com>
To: Raul E Rangel <rrangel@...omium.org>,
"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>
CC: "djkurtz@...omium.org" <djkurtz@...omium.org>,
"zwisler@...omium.org" <zwisler@...omium.org>,
hongjiefang <hongjiefang@...micro.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Shawn Lin <shawn.lin@...k-chips.com>,
Kyle Roeschley <kyle.roeschley@...com>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: RE: [PATCH v2] mmc: core: Verify SD bus width
>
> The SD Physical Layer Spec says the following: Since the SD Memory Card
> shall support at least the two bus modes 1-bit or 4-bit width, then any SD
> Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101").
>
> This change verifies the card has specified a bus width.
>
> AMD SDHC Device 7806 can get into a bad state after a card disconnect
> where anything transferred via the DATA lines will always result in a
> zero filled buffer. Currently the driver will continue without error if
> the HC is in this condition. A block device will be created, but reading
> from it will result in a zero buffer. This makes it seem like the SD
> device has been erased, when in actuality the data is never getting
> copied from the DATA lines to the data buffer.
>
> SCR is the first command in the SD initialization sequence that uses the
> DATA lines. By checking that the response was invalid, we can abort
> mounting the card.
>
> Acked-by: Avri Altman <avri.altman@....com>
>
> Signed-off-by: Raul E Rangel <rrangel@...omium.org>
Reviewed-by: Avri Altman <avri.altman@....com>
Thanks,
Avri
Powered by blists - more mailing lists