Re: Is it possible for the ext4/btrfs file system to pass some context related info to low level block driver?

2011-05-02 Thread Kyungmin Park
Hi, It seems similar with TRIM. So how about to consider TRIM implementation or extend it? I'm not familiar with NCQ implementation but it's also helpful to implement it. Thank you, Kyungmin Park On Tue, May 3, 2011 at 11:44 AM, Gao, Yunpeng wrote: > Currently, some new storage devices have the

Is it possible for the ext4/btrfs file system to pass some context related info to low level block driver?

2011-05-02 Thread Gao, Yunpeng
Currently, some new storage devices have the ability to do performance optimizations according to the type of data payload - say, file system metadata, time-stamps, sequential write in some granularity, random write and so on. For example, the latest eMMC 4.5 device can support the so-called 'C

Re: [PATCH v2 1/4]enable background operations for supported eMMC card

2011-05-02 Thread Per Forlin
On Fri, Dec 3, 2010 at 1:13 PM, Chuanxiao Dong wrote: > From 984adc755cf2f7966a89e510a50f085e314fe347 Mon Sep 17 00:00:00 2001 > From: Chuanxiao Dong > Date: Mon, 22 Nov 2010 16:31:12 +0800 > Subject: [PATCH 1/4] mmc: Enabled background operations feature if eMMC card > supports > > Background o

[PATCH V2 7/7] mmc: msm_sdcc: Handle dma resource not present case

2011-05-02 Thread Sahitya Tummala
From: Subhash Jadavani If DMA resource is not available then SDCC driver should atleast work in PIO data transfer mode. Signed-off-by: Subhash Jadavani Signed-off-by: Sahitya Tummala --- drivers/mmc/host/msm_sdcc.c | 15 ++- 1 files changed, 10 insertions(+), 5 deletions(-) dif

[PATCH V2 6/7] mmc: msm_sdcc: Change initialization order of busclk_timer in probe

2011-05-02 Thread Sahitya Tummala
Intialize busclk_timer before it is accessed in probe. Signed-off-by: Sahitya Tummala --- drivers/mmc/host/msm_sdcc.c |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/mmc/host/msm_sdcc.c b/drivers/mmc/host/msm_sdcc.c index 908524b..1fe4102 100644 --- a/driv

[PATCH V2 5/7] mmc: msm_sdcc: Use MCI_INT_MASK0 for PIO interrupts

2011-05-02 Thread Sahitya Tummala
Not all targets have IRQ1 line routed from the SD controller to the processor. So we cannot rely on IRQ1 for PIO interrupts. This patch moves all PIO interrupts to IRQ0 and enables the PIO mode. Signed-off-by: Murali Palnati Signed-off-by: Sahitya Tummala --- drivers/mmc/host/msm_sdcc.c | 20

[PATCH V2 4/7] msm: mmc: Remove "pio_irq" resource

2011-05-02 Thread Sahitya Tummala
On some targets, MCI_IRQ_MASK1 is not routed to the MSM in which case only "cmd_irq" must be used even for PIO. With this change, all the targets will use only "cmd_irq" for both CMD and PIO. Signed-off-by: Sahitya Tummala --- arch/arm/mach-msm/devices-msm7x00.c | 24

[PATCH V2 3/7] mmc: msm_sdcc: Enable SDC host->clk only after setting the rate.

2011-05-02 Thread Sahitya Tummala
For clocks that support rates which can be set (most clocks other than _pclk AHB clocks), a rate must be set using clk_set_rate() before the clock is enabled for the first time with clk_enable(). Subsequent calls to clk_enable() need not be preceded with the clk_set_rate() calls unless we wish to c

[PATCH V2 2/7] mmc: msm_sdcc: Handle error cases in probe

2011-05-02 Thread Sahitya Tummala
Signed-off-by: Sahitya Tummala --- drivers/mmc/host/msm_sdcc.c | 14 +++--- 1 files changed, 11 insertions(+), 3 deletions(-) diff --git a/drivers/mmc/host/msm_sdcc.c b/drivers/mmc/host/msm_sdcc.c index d06539d..66ef5c3 100644 --- a/drivers/mmc/host/msm_sdcc.c +++ b/drivers/mmc/host/ms

[PATCH V2 1/7] mmc: msm_sdcc: handle the platform gpio_data not present case

2011-05-02 Thread Sahitya Tummala
From: Subhash Jadavani If platform gpio_data is not present then don't do any gpio configuration. Signed-off-by: Subhash Jadavani Signed-off-by: Sahitya Tummala --- drivers/mmc/host/msm_sdcc.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/mmc/host/msm_sdcc.

Re: [PATCH] dw_mmc: fixed regulator control

2011-05-02 Thread Jaehoon Chung
Hi Chris.. Thanks for comments... I think that could confuse that message when didn't set CONFIG_REGULATOR. And i wonder how do you think about regulator control in suspend (dw_mmc.c)? @@ -1769,9 +1771,6 @@ static int dw_mci_suspend(struct platform_device *pdev, pm_message_t mesg) int i