linux-kernel - Re: [PATCH RFC 00/12] Add Qualcomm SD Card Controller support.

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]

Date:	Tue, 20 May 2014 09:10:48 +0100
From:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:	Bjorn Andersson <bjorn@...o.se>
CC:	linux-mmc@...r.kernel.org, Russell King <linux@....linux.org.uk>,
	Chris Ball <chris@...ntf.net>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	agross@...cinc.com, linux-arm-msm <linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH RFC 00/12] Add Qualcomm SD Card Controller support.

Thanks Bjorn for testing this series.

On 19/05/14 23:08, Bjorn Andersson wrote:
> On Mon, Apr 21, 2014 at 2:43 PM,<srinivas.kandagatla@...aro.org>  wrote:
>> >From: Srinivas Kandagatla<srinivas.kandagatla@...aro.org>
> [snip]
>> >
>> >This patches are tested in PIO mode on IFC8064 board with both eMMC and
>> >external SD card. I would appreciate any feedback/suggestions on the overall
>> >approach.
> Hi Srini,
>
> I finally got around to give this series a spin on our APQ8064 based
> devices as well. I had a few reported CRC issues on our msm8960 based
> devices, but thinks seems functionally "ok".
>
> On APQ8064, the kernel finds the onboard eMMC and when mounting it I
> get the following:
>
> [    1.624118] mmc0: new high speed MMC card at address 0001
> [    1.627521] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
> [    1.632714] mmcblk0boot0: mmc0:0001 MAG2GA partition 1 2.00 MiB
> [    1.636989] mmcblk0boot1: mmc0:0001 MAG2GA partition 2 2.00 MiB
> [    1.637393] Freeing unused kernel memory: 332K (c09c6000 - c0a19000)
> [    1.663379] mmcblk0: response CRC error sending r/w cmd command,
>
> [    2.292914] mmcblk0: response CRC error sending r/w cmd command,
> card status 0xb00
> [    2.300985] mmcblk0: response CRC error sending r/w cmd command,
>
>
> Any suggestions of what I could do to help you debug this?
>

There might be couple of reasons why this might happen,

First is the regluators. currently the upstream kernel does not have 
support for regulators. So, does the eMMC on your board work perfectly 
fine with the default 2.7v?

secondly it could be eMMC vendor specific quirks.

I stress tested eMMC on IFC6410 and I did not hit any issues as you 
mentioned.

Are you aware of any such quirks specific to the eMMC on your board?

thanks,
srini

> Regards,
> Bjorn
--
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/