From: Paul Mundt <lethal@linux-sh.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 0/3] Make DMA slave ID 0 invalid to simplify platform data
Date: Wed, 25 May 2011 11:32:17 +0900 [thread overview]
Message-ID: <20110525023217.GF14329@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1105241147010.31628@axis700.grange>
On Tue, May 24, 2011 at 12:23:55PM +0200, Guennadi Liakhovetski wrote:
> Currently platforms, using the SDHI TMIO driver, have to specify negative
> DMA slave IDs to force PIO mode. If default 0 is left, the driver
> recognises it as a valid DMA slave ID and tries to acquire channels. This
> fails then, because the driver cannot allocate two channels with the same
> ID, but it would be better to just make 0 an invalid ID to prevent this.
>
I suppose the ordering for this will be adding the invalid IDs for all of
the CPUs first and then updating the SDHI driver accordingly during -rc2
or something like that.
next prev parent reply other threads:[~2011-05-25 2:32 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
2011-05-25 2:32 ` Paul Mundt [this message]
2011-05-25 6:48 ` [PATCH 0/3] Make DMA slave ID 0 invalid to simplify platform data 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=20110525023217.GF14329@linux-sh.org \
--to=lethal@linux-sh.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