linux-kernel - Re: [RFC][PATCH] MMC: Use write timeout value as read from CSR

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200809081218.49766.david-b@pacbell.net>
Date:	Mon, 8 Sep 2008 12:18:49 -0700
From:	David Brownell <david-b@...bell.net>
To:	"Matt Fleming" <mattjfleming@...glemail.com>
Cc:	"Pierre Ossman" <drzeus-mmc@...eus.cx>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] MMC: Use write timeout value as read from CSR

On Monday 08 September 2008, Matt Fleming wrote:
> Currently, the MMC/SD over SPI code has a hard-coded timeout value of
> 250ms on writes and 100ms on reads. This is correct for SDHC cards
> and is specified in the spec, but it is not correct for MMC/SD cards.
> 
> For MMC cards the values that are read from the CSR should be used.
> For SD cards the values from the CSR should be used as long as they
> do not exceed 250ms for writes and 100ms for reads.
> 
> Signed-off-by: Matthew Fleming <matthew.fleming@...tec.com>

OK by me.  I was viewing those values as ceilings, such that
waiting too long wouldn't much matter.  If there are cases
where the CSR values are larger, they clearly should trump.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/