linux-kernel - Re: [RFC/PATCH 0/2] mmc: sdhci: Workaround Intel Merrifield issue for HS200

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: <5282A255.5090904@linux.intel.com>
Date:	Tue, 12 Nov 2013 13:49:09 -0800
From:	David Cohen <david.a.cohen@...ux.intel.com>
To:	cjb@...top.org
CC:	adrian.hunter@...el.com, gregkh@...uxfoundation.org,
	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	chuanxiao.dong@...el.com
Subject: Re: [RFC/PATCH 0/2] mmc: sdhci: Workaround Intel Merrifield issue
 for HS200

On 10/29/2013 10:58 AM, David Cohen wrote:
> Hi,
>
> SDHCI used to work well on Intel Merrifield until this patch was applied:
>
> commit 156e14b126ffb6f040bc6f1aff3c51077e42a744
> Author: Giuseppe CAVALLARO <peppe.cavallaro@...com>
> Date:   Wed Jun 12 08:16:38 2013 +0200
>
>      mmc: sdhci: fix caps2 for HS200
>
>      Although the HC supports HS200 (eMMC) the caps2 are always zero; this
>      means there's no way to use the super speed mode (when init the card).
>
>      If the HC support SDR104, for SD3.0, so it also supports HS200 for eMMC
>      and this patch just sets the MMC_CAP2_HS200 in the host caps2 field.
>
> Looks like there is a hw issue with unknown root cause so far.
>
> Is it acceptable to have the quirk I'm proposing to workaround the issue?

Ping. Any comments here?

Br, David Cohen
--
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/