Re: [PATCH 3/3 RESEND] mmc: sdhci: check voltage range only on regulators aware of voltage value

2013-02-12 Thread Guennadi Liakhovetski
On Wed, 13 Feb 2013, Marek Szyprowski wrote: > Hello, > > On 2/12/2013 11:10 PM, Guennadi Liakhovetski wrote: > > Hi Marek > > > > On Tue, 12 Feb 2013, Marek Szyprowski wrote: > > > > > Some regulators don't report any voltage values, so checking supported > > > voltage range results in disabli

Re: [PATCH 3/3 RESEND] mmc: sdhci: check voltage range only on regulators aware of voltage value

2013-02-12 Thread Marek Szyprowski
Hello, On 2/12/2013 11:10 PM, Guennadi Liakhovetski wrote: Hi Marek On Tue, 12 Feb 2013, Marek Szyprowski wrote: > Some regulators don't report any voltage values, so checking supported > voltage range results in disabling all SDHCI_CAN_VDD_* flags and > registration failure. This patch finall

Re: [PATCH 3/3 RESEND] mmc: sdhci: check voltage range only on regulators aware of voltage value

2013-02-12 Thread Guennadi Liakhovetski
Hi Marek On Tue, 12 Feb 2013, Marek Szyprowski wrote: > Some regulators don't report any voltage values, so checking supported > voltage range results in disabling all SDHCI_CAN_VDD_* flags and > registration failure. This patch finally provides a correct fix for the > registration of SDHCI drive

Re: [PATCH v3 1/3] dmaengine: add dma_get_slave_sg_caps()

2013-02-12 Thread Vinod Koul
On Mon, Feb 04, 2013 at 02:47:02PM -0500, Matt Porter wrote: > Add a dmaengine API to retrieve slave SG transfer capabilities. > > The API is optionally implemented by dmaengine drivers and when > unimplemented will return a NULL pointer. A client driver using > this API provides the required dma

Re: [PATCH v7 07/10] dmaengine: add dma_request_slave_channel_compat()

2013-02-12 Thread Vinod Koul
On Fri, Feb 01, 2013 at 01:22:52PM -0500, Matt Porter wrote: > Adds a dma_request_slave_channel_compat() wrapper which accepts > both the arguments from dma_request_channel() and > dma_request_slave_channel(). Based on whether the driver is > instantiated via DT, the appropriate channel request cal

Re: [patch] mmc: check correct variable after kzalloc()

2013-02-12 Thread Dan Carpenter
On Tue, Feb 12, 2013 at 07:27:26AM -0500, Chris Ball wrote: > Hi Dan, > > On Tue, Feb 12 2013, Dan Carpenter wrote: > > There is a typo here so we check "mqrq_cur->packed" instead of > > "mqrq_prev->packed". > > > > Signed-off-by: Dan Carpenter > > > > diff --git a/drivers/mmc/card/queue.c b/driv

Re: [patch] mmc: check correct variable after kzalloc()

2013-02-12 Thread Chris Ball
Hi Dan, On Tue, Feb 12 2013, Dan Carpenter wrote: > There is a typo here so we check "mqrq_cur->packed" instead of > "mqrq_prev->packed". > > Signed-off-by: Dan Carpenter > > diff --git a/drivers/mmc/card/queue.c b/drivers/mmc/card/queue.c > index c0d1315..97a848b 100644 > --- a/drivers/mmc/card/

[patch] mmc: check correct variable after kzalloc()

2013-02-12 Thread Dan Carpenter
There is a typo here so we check "mqrq_cur->packed" instead of "mqrq_prev->packed". Signed-off-by: Dan Carpenter diff --git a/drivers/mmc/card/queue.c b/drivers/mmc/card/queue.c index c0d1315..97a848b 100644 --- a/drivers/mmc/card/queue.c +++ b/drivers/mmc/card/queue.c @@ -378,7 +378,7 @@ int mm

Re: [PATCH v3 1/3] mmc: davinci_mmc: add DT support

2013-02-12 Thread Mark Rutland
Hi Prakash, I think this looks pretty good now :) Reviewed-by: Mark Rutland Thanks, Mark. On Tue, Feb 12, 2013 at 06:37:36AM +, Manjunathappa, Prakash wrote: > Adds device tree support for davinci_mmc. Also add binding documentation. > As of now in non-dma PIO mode and without GPIO card_de

RE: [PATCH v9 0/2] mmc: support packed command feature of eMMC4.5

2013-02-12 Thread Seungwon Jeon
On Tuesday, February 12, 2013, Arnd Bergmann wrote: > On Monday 11 February 2013, Chris Ball wrote: > > On Wed, Feb 06 2013, Seungwon Jeon wrote: > > > This patch-set adds support of packed command feature for eMMC4.5 devices. > > > Specially, packed write is introduced. > > > > Thanks, I've pushed

[PATCH 3/3 RESEND] mmc: sdhci: check voltage range only on regulators aware of voltage value

2013-02-12 Thread Marek Szyprowski
Some regulators don't report any voltage values, so checking supported voltage range results in disabling all SDHCI_CAN_VDD_* flags and registration failure. This patch finally provides a correct fix for the registration of SDHCI driver with all possible voltage regulators: dummy, fixed and regulat