linux-kernel - Re: [PATCH v4 0/4]implement eMMC4.4 standard HW reset feature

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: <AANLkTinrPd9p4ocmE+Krj7t4yV8SMPsDeDFuTByy2=Q4@mail.gmail.com>
Date:	Tue, 7 Dec 2010 10:34:25 +0900
From:	Kyungmin Park <kmpark@...radead.org>
To:	"Dong, Chuanxiao" <chuanxiao.dong@...el.com>
Cc:	"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"cjb@...top.org" <cjb@...top.org>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"alan@...ux.intel.com" <alan@...ux.intel.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"Mai, Leonard" <leonard.mai@...el.com>,
	Arnd Bergmann <arnd@...db.de>,
	Wolfram Sang <w.sang@...gutronix.de>
Subject: Re: [PATCH v4 0/4]implement eMMC4.4 standard HW reset feature

On Tue, Dec 7, 2010 at 1:03 AM, Dong, Chuanxiao
<chuanxiao.dong@...el.com> wrote:
> Hello all,
> How about these patches? It implemented HW reset feature. When card occurred a timeout error during reading/writing/erasing, these patches will allow driver to reset eMMC card by trigger a HW reset signal.
> Does anyone have any comments about the implementation of these patches? Wolfram and Arnd already pointed out the unsuitable patch headers. Thanks! :)

Hi,
I'm not yet find a reason to use this feature. Now it uses the samsung
and sandisk v4.41 but still no problem.
I wonder what's the purpose and effect if it uses or not?

Thank you,
Kyungmin Park

>
>
>> -----Original Message-----
>> From: linux-mmc-owner@...r.kernel.org
>> [mailto:linux-mmc-owner@...r.kernel.org] On Behalf Of Chuanxiao Dong
>> Sent: Wednesday, December 01, 2010 8:49 PM
>> To: linux-mmc@...r.kernel.org
>> Cc: linux-kernel@...r.kernel.org; cjb@...top.org; arjan@...ux.intel.com;
>> alan@...ux.intel.com; akpm@...ux-foundation.org
>> Subject: [PATCH v4 0/4]implement eMMC4.4 standard HW reset feature
>>
>> Hi,
>>       These are the version 4 patches to implement eMMC4.4 HW reset
>>       feature. Host controller can use this feature by trigger RST_n signal.
>>       To enable this, byte 162 of EXT_CSD register should be set.
>>       HW reset is implemented in mmc core layer and sdhci host layer, and it
>>       will be used after each reading/writing/erasing timeout error occures.
>>
>>       change-log:
>>       This version change the way to detect timeout error conditions. Added a
>>       new routine mmc_handle_timeout_error to do this instead to do this in
>>       mmc_wait_for_req. Each timeout read/write/erase command can use this
>>       routine to do HW reset.
>>
>>       patch1: enable HW reset capability if card support.
>>
>>       patch2: add two new callback to implement HW reset in mmc core layer. In
>>       this patch, routine mmc_handle_timeout_error was added.
>>
>>       patch3: implement hardware_reset callback for sdhci host. A new callback
>>       reset_emmc was defined which will be each sdhci host controller to
>>       implement separately.
>>
>>       patch4: did a HW reset after each read/write/erase command.
>>
>> Thanks
>> Chuanxiao
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@...r.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
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/