public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-sh@vger.kernel.org, linux-mmc@vger.kernel.org,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <damm@opensource.se>, Ian Molton <ian@mnementh.co.uk>,
	Dan Williams <dan.j.williams@intel.com>,
	Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH 3/3] mmc: SDHI: DMA slave ID 0 is invalid
Date: Mon, 20 Jun 2011 15:37:13 -0400	[thread overview]
Message-ID: <m2tybkxpjq.fsf@bob.laptop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1106201527210.11365@axis700.grange> (Guennadi Liakhovetski's message of "Mon, 20 Jun 2011 16:52:16 +0200 (CEST)")

Hi Guennadi,

On Mon, Jun 20 2011, Guennadi Liakhovetski wrote:
> Can we please get this patch too in for 3.0? It is a part of a 
> patch-series, of which all others havs already been applied. This specific 
> patch makes the behaviour of the SDHI driver consistent with other DMA 
> users on sh-mobile, namely, that default platform data with no DMA 
> information provided immediately switches the driver to the PIO mode. This 
> patch fixes this logical error of trying to acquire DMA channels with 
> invalid configuration information and avoids ugly error messages in the 
> kernel log.
>
> Thanks
> Guennadi
>
> On Tue, 24 May 2011, Guennadi Liakhovetski wrote:
>
>> Don't try to allocate DMA resources, if the platform didn't specify
>> positive DMA slave IDs.
>> 
>> Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
>> ---
>>  drivers/mmc/host/sh_mobile_sdhi.c |    2 +-
>>  1 files changed, 1 insertions(+), 1 deletions(-)
>> 
>> diff --git a/drivers/mmc/host/sh_mobile_sdhi.c b/drivers/mmc/host/sh_mobile_sdhi.c
>> index c05d699..e646741 100644
>> --- a/drivers/mmc/host/sh_mobile_sdhi.c
>> +++ b/drivers/mmc/host/sh_mobile_sdhi.c
>> @@ -132,7 +132,7 @@ static int __devinit sh_mobile_sdhi_probe(struct platform_device *pdev)
>>  		mmc_data->ocr_mask = p->tmio_ocr_mask;
>>  		mmc_data->capabilities |= p->tmio_caps;
>>  
>> -		if (p->dma_slave_tx >= 0 && p->dma_slave_rx >= 0) {
>> +		if (p->dma_slave_tx > 0 && p->dma_slave_rx > 0) {
>>  			priv->param_tx.slave_id = p->dma_slave_tx;
>>  			priv->param_rx.slave_id = p->dma_slave_rx;
>>  			priv->dma_priv.chan_priv_tx = &priv->param_tx;
>> -- 
>> 1.7.2.5

Thanks, pushed to mmc-next for 3.0.

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-06-20 19:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 10:23 [PATCH 0/3] Make DMA slave ID 0 invalid to simplify platform data Guennadi Liakhovetski
2011-05-24 10:23 ` [PATCH 1/3] sh: mark DMA slave ID 0 as invalid Guennadi Liakhovetski
2011-05-24 10:24 ` [PATCH 2/3] ARM: mach-shmobile: " Guennadi Liakhovetski
2011-05-24 10:24 ` [PATCH 3/3] mmc: SDHI: DMA slave ID 0 is invalid Guennadi Liakhovetski
2011-06-20 14:52   ` Guennadi Liakhovetski
2011-06-20 19:37     ` Chris Ball [this message]
2011-05-25  2:32 ` [PATCH 0/3] Make DMA slave ID 0 invalid to simplify platform data Paul Mundt
2011-05-25  6:48   ` Guennadi Liakhovetski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2tybkxpjq.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=damm@opensource.se \
    --cc=dan.j.williams@intel.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=horms@verge.net.au \
    --cc=ian@mnementh.co.uk \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=vinod.koul@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox