From: Ian Molton <ian@mnementh.co.uk>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, dan.j.williams@intel.com,
Paul Mundt <lethal@linux-sh.org>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <rmk@arm.linux.org.uk>,
sameo@linux.intel.com,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
linux-mmc@vger.kernel.org
Subject: Re: + mmc-add-dma-support-to-tmio_mmc-driver-when-used-on-superh.patch
Date: Thu, 13 May 2010 21:46:31 +0000 [thread overview]
Message-ID: <AANLkTikV-qMrdJq9hbdeRnqjZf811lY6eAHPP7rRV2qf@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1005131616230.4671@axis700.grange>
Sounds good to me, and you're right - the MFD level is good for this
config option.
--
Ian Molton
Linux, Automotive, and other hacking:
http://www.mnementh.co.uk/
On 13 May 2010 15:18, Guennadi Liakhovetski <g.liakhovetski@gmx.de> wrote:
> On Thu, 13 May 2010, Guennadi Liakhovetski wrote:
>
>> On Thu, 13 May 2010, Ian Molton wrote:
>>
>> > Might be worth exposing for now, whilst the feature is new. but yes,
>> > automatic select yes on all the platforms you are comfortable with.
>> >
>> > Im not sure if it should be per MFD or per platform. I tend to think
>> > the latter, given that its slave DMA and thus I could have the same
>> > MFD in platforms with different CPUs (eg. e740 and e800) where a CPU
>> > bug might upset one but not the other.
>>
>> So far I went for the least effort - not exposed, selected by MFDs. If we
>> ever have a need to change this, e.g., make it user-selectable or per
>> platform, we can always do so later. For now all SuperH / SH-Mobile
>> platforms I tested can use this driver with DMA. Expect updated patches
>> shortly.
>
> One more thing I forgot to mention - even if your MFD enables DMA, it
> still can further decide when (on which platforms) to enable and when to
> disable DMA by providing or not providing DMA slave configuration to
> tmio_mmc.
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
>
prev parent reply other threads:[~2010-05-13 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201005122255.o4CMtmvN025653@imap1.linux-foundation.org>
[not found] ` <AANLkTim5U-JbrVCBKHnERgHol2GcwTfweQyI4onR1Skh@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.1005131357500.4671@axis700.grange>
[not found] ` <AANLkTinPW2W6aV1smLsQObLOAS3bECDZ7mhSGCm2aqgO@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.1005131415460.4671@axis700.grange>
[not found] ` <AANLkTik4gzuZvrAwbK-dyCXVYf5gLD0RGrpvM55YLzOK@mail.gmail.com>
2010-05-13 13:20 ` + mmc-add-dma-support-to-tmio_mmc-driver-when-used-on-superh.patch Guennadi Liakhovetski
2010-05-13 14:18 ` Guennadi Liakhovetski
2010-05-13 21:46 ` Ian Molton [this message]
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=AANLkTikV-qMrdJq9hbdeRnqjZf811lY6eAHPP7rRV2qf@mail.gmail.com \
--to=ian@mnementh.co.uk \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=sameo@linux.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;
as well as URLs for NNTP newsgroup(s).