Hi Yi,
I tested your patch on msm platform and found few issues. Please see my
comments inline.
On Thu, June 4, 2015 7:50 pm, Yi Sun wrote:
> Enhance Strobe is defined in v5.1 eMMC spec. This commit
Please replace "Enhance Strobe" to "Enhanced Strobe" as per spec
throughout the documentation and
On Thu, Jun 11, 2015 at 08:11:45PM +0800, Wan ZongShun wrote:
> The KERNCZ is new AMD SB/FCH generation name, like HUDSON2.
> We will adopt 0x790b as device ID since from this gereration.
s/We will adopt 0x790b as device ID since from/0x790b is the device ID for/
s/gereration/generation/
> Signed
Hi Ben,
On Friday 12 June 2015 14:23:55 Ben Hutchings wrote:
> On Fri, 2015-06-12 at 10:18 +0300, Laurent Pinchart wrote:
> > Hi Ben,
> >
> > (CC'ing Linus Walleij)
> >
> > Thank you for the patch.
> >
> > On Wednesday 10 June 2015 00:23:31 Ben Hutchings wrote:
> > > All the SHDIs can operate w
On Fri, Jun 12, 2015 at 12:22 AM, Dong Aisheng wrote:
> I think this patch will break the eMMC DDR 3.3v mode support.
I think you are right.
On a imx6q-sabresd which has 'no-1-8-v' in the emmc node we have originally:
mmc2: new DDR MMC card at address 0001
After applying this patch I get:
mm
On Fri, 2015-06-12 at 10:18 +0300, Laurent Pinchart wrote:
> Hi Ben,
>
> (CC'ing Linus Walleij)
>
> Thank you for the patch.
>
> On Wednesday 10 June 2015 00:23:31 Ben Hutchings wrote:
> > All the SHDIs can operate with either 3.3V or 1.8V signals, depending
> > on negotiation with the card.
> >
On Thu, Jun 04, 2015 at 06:58:06PM +0300, Peter Ujfalusi wrote:
> Vinod,
>
> On 06/02/2015 03:55 PM, Vinod Koul wrote:
> > On Fri, May 29, 2015 at 05:32:50PM +0300, Peter Ujfalusi wrote:
> >> On 05/29/2015 01:18 PM, Vinod Koul wrote:
> >>> On Fri, May 29, 2015 at 11:42:27AM +0200, Geert Uytterhoev
From 0e01e7546745f39843d54810f74c198e01cb8226 Mon Sep 17 00:00:00 2001
From: justin.wang
Date: Mon, 18 May 2015 20:14:15 +0800
Subject: [PATCH v2] mmc: card: Fixup request missing in mmc_blk_issue_rw_rq
The current handler of MMC_BLK_CMD_ERR in mmc_blk_issue_rw_rq function
may cause new coming re
Hi Dong,
On Fri, Jun 12, 2015 at 12:22 AM, Dong Aisheng wrote:
> I think this patch will break the eMMC DDR 3.3v mode support.
I don't think so.
This patch only changes the behaviour when 'no-1-8-v' property is used.
This custom board has an eMMC that can operate at 1.8V, but the board
itself
From: Mirza Krak
Add support for current states of pinctrl, which are "default", "idle"
and "sleep".
The "default" pinctrl state is set by Drivers core before
calling the driver's probe, hence we do not need a initial call to
"default" state.
Signed-off-by: Mirza Krak
---
drivers/mmc/host/sdh
Hi,
today I plugged in an SD card into the laptop's built-in reader on
x86-64 and got "Corrupted low memory" as a result:
Corrupted low memory at 88001000 (1000 phys) = 22b7d67df2f6d1cf
Corrupted low memory at 88001008 (1008 phys) = 63848a5216b7dd95
Corrupted low memory at 8800
On 12 June 2015 at 03:54, Jaehoon Chung wrote:
> Dear, Ulf.
>
> Could you pull this patch for mmc-next?
>
> Best Regards,
> Jaehoon Chung
>
>
> The following changes since commit 5fd26c7ecb32082745b0bd33c8e35badd1cb5a91:
>
> mmc: sdhci: Restore behavior while creating OCR mask (2015-06-08 09:49:
On 12/06/15 07:39, Fabio Estevam wrote:
> From: Fabio Estevam
>
> If mmc_gpio_alloc() fails we miss to call 'kfree(host)', so rearrange
> the error path to fix it.
Are you sure it doesn't get freed through put_device()?
>
> Signed-off-by: Fabio Estevam
> ---
> drivers/mmc/core/host.c | 18 +
Hi Ben,
(CC'ing Linus Walleij)
Thank you for the patch.
On Wednesday 10 June 2015 00:23:31 Ben Hutchings wrote:
> All the SHDIs can operate with either 3.3V or 1.8V signals, depending
> on negotiation with the card.
>
> Add separate functions for the 1.8V mode, and implement the set_mux
> opera
13 matches
Mail list logo
