At Thu, 9 Dec 2010 21:37:24 +0100,
Rafael J. Wysocki wrote:
>
> On Thursday, December 09, 2010, Takashi Iwai wrote:
> > At Thu, 9 Dec 2010 01:53:03 +,
> > Chris Ball wrote:
> > >
> > > Hi Takashi,
> > >
> > > On Wed, Dec 08, 2010 at 04:23:59PM +0100, Takashi Iwai wrote:
> > > > The commit 4c
Hi Linus,
On Thu, Dec 02, 2010 at 02:36:58PM +0100, Linus Walleij wrote:
> The regulator and MMC frameworks provide the proper stub functions
> for the regulator functions anyway, get rid of this.
>
> Signed-off-by: Linus Walleij
> ---
> drivers/mmc/host/mmci.c |3 +--
> 1 files changed, 1
On Friday, December 10, 2010, Ohad Ben-Cohen wrote:
> When pm_runtime_put_sync() returns, the _put operation is completed,
> and if needed (zero usage_count, children are ignored or their count
> is zero, ->runtime_idle() called pm_runtime_suspend(), no
> runtime_error, no disable_depth, etc...) th
When pm_runtime_put_sync() returns, the _put operation is completed,
and if needed (zero usage_count, children are ignored or their count
is zero, ->runtime_idle() called pm_runtime_suspend(), no
runtime_error, no disable_depth, etc...) the device is powered down.
This behavior is sometimes desira
On Thursday, December 09, 2010, Takashi Iwai wrote:
> At Thu, 9 Dec 2010 01:53:03 +,
> Chris Ball wrote:
> >
> > Hi Takashi,
> >
> > On Wed, Dec 08, 2010 at 04:23:59PM +0100, Takashi Iwai wrote:
> > > The commit 4c2ef25fe0b847d2ae818f74758ddb0be1c27d8e
> > > mmc: fix all hangs related to mm
On Thu, Dec 9, 2010 at 5:35 PM, Chris Ball wrote:
> Hi Andrew,
>
> On Thu, Dec 09, 2010 at 04:01:57PM +, Chris Ball wrote:
>> > > Is there something we could depend on that would stop this driver being
>> > > presented to everyone, without being far too specific? At the moment
>> > > we'd be
Hi Andrew,
On Thu, Dec 09, 2010 at 04:01:57PM +, Chris Ball wrote:
> > > Is there something we could depend on that would stop this driver being
> > > presented to everyone, without being far too specific? At the moment
> > > we'd be making x86 desktop users say whether they have this IP, whi
Hi Will,
On Thu, Dec 09, 2010 at 12:11:06PM +, Will Newton wrote:
> > Is there something we could depend on that would stop this driver being
> > presented to everyone, without being far too specific? At the moment
> > we'd be making x86 desktop users say whether they have this IP, which
> >
Hi Daniel,
On Wed, 2010-12-08 at 10:25 -0800, Daniel Walker wrote:
> On Wed, 2010-12-08 at 15:03 +0530, Sahitya Tummala wrote:
> > In the context of request processing thread, data mover lock is
> > acquired after the host lock. In another context, in the completion
> > handler of data mover the
HW reset will reset eMMC card. So after reset, card should also be
reinitialized. Add two new callbacks to implement reset and reinitialize.
MMC core layer will check whether occurs a timeout error in the new added
routine mmc_handle_timeout_error
mmc_handle_timeout_error: check whether occurs a t
hardware_reset callback will be used for host to trigger RST_n signal. The
signal should be triggered by pull some GPIO or use some hardware else. Only
SDHCI host controller driver can touch such specific hardware. So a new
callback reset_emmc was added to trigger the reset signal. This patch
imple
Driver can do a HW reset for eMMC card if read/write/erase
occurs timeout error.
Signed-off-by: Chuanxiao Dong
---
drivers/mmc/card/block.c | 10 ++
drivers/mmc/core/core.c |2 ++
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/mmc/card/block.c b/drivers/mm
HW reset capability enable bit is byte 162 in card EXT_CSD register, only
version4.4 card or later can support to enable this feature.
HW reset feature can be used to reset eMMC card when occurs timeout error
during read/write/erase even eMMC card cannot correspond any command
Signed-off-by: Chua
Hi,
This is the version 5 of HW reset feature implementation. HW reset can
reset eMMC card when card occurs a read/write/erase timeout error. It is
useful when eMMC card cannot correspond any command after occurs a
timeout
error.
change-log:
patch1:
On Thu, Dec 9, 2010 at 6:47 AM, Chris Ball wrote:
> Hi Will,
>
> Thanks for the submission (and thanks for the review, Matt!).
>
> Some more comments below, mainly stylistic, and at the bottom I've
> attached an indentation and cleanup patch. It's okay if there are
> some changes in it that you'd
Dear All
JMicron 388 support the new generation SD card with Ultra-High speed
feature.
it have to run under 1.8V in this feature, that mean the capability of host
is claimed to support both 1.8V and 3.3V, but the 1.8V and 3.3V is only for
SD part, it is always 3.3V for MMC part.
In MMC-mobile car
At Wed, 8 Dec 2010 21:18:38 -0500,
zhangfei gao wrote:
>
> On Wed, Dec 8, 2010 at 4:04 AM, Takashi Iwai wrote:
> > JMicron 388 SD/MMC combo controller supports the 1.8V low-voltage for
> > SD, but MMC doesn't work with the low-voltage, resulting in an error
> > at probing.
> >
> > This patch adds
17 matches
Mail list logo