From: Chris Ball <cjb@laptop.org>
To: Will Newton <will.newton@gmail.com>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
linux-mmc@vger.kernel.org, girish.shivananjappa@linaro.org,
James Hogan <James.Hogan@imgtec.com>
Subject: Re: [PATCH] Revert "mmc: dw_mmc: Add check for IDMAC configuration"
Date: Wed, 19 Sep 2012 02:03:26 -0400 [thread overview]
Message-ID: <m3sjaeim6p.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <CAFbHwiRWkCoxm553u8Ep3hF3XZpBihA-2_FW2Y0sVq1RC3riHg@mail.gmail.com> (Will Newton's message of "Mon, 17 Sep 2012 12:15:46 +0100")
Hi,
On Mon, Sep 17 2012, Will Newton wrote:
> On Tue, Sep 11, 2012 at 3:23 AM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
>> This reverts commit 94c6cee91(Add check for IDMAC configuration).
>> Synopsys says that only if internal dmac is not present, optional
>> external dma interface is present. When internal dmac is present,
>> '0' value in DMA_INTERFACE of HCON is reasonable. DMA_INTERFACE
>> indicates external dma interface. And idmac initialization is
>> prohibited now. So, let's revert this commit.
>>
>> CC: Girish K S <girish.shivananjappa@linaro.org>
>> Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
>> ---
>> drivers/mmc/host/dw_mmc.c | 15 ++-------------
>> 1 files changed, 2 insertions(+), 13 deletions(-)
>
> I think this revert is a good idea. The original patch tries to check
> whether IDMAC is supported and falls back to PIO, but it is not clear
> to me that HCON gives you the appropriate information to do this (at
> least in my version of the manual, I have not tried to clarify this
> with Synopsys). Also falling back to PIO mode seems like it would
> provide pretty awful performance, I would not expect to see instances
> of this block with no DMA support anywhere other than FPGA so
> configuring with IDMAC without it's presence would be a serious
> misconfiguration in any case.
>
> Acked-by: Will Newton <will.newton@imgtec.com>
Thanks, pushed to mmc-next for 3.7.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-09-19 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 2:23 [PATCH] Revert "mmc: dw_mmc: Add check for IDMAC configuration" Seungwon Jeon
2012-09-11 3:46 ` Girish K S
2012-09-11 4:36 ` Jaehoon Chung
2012-09-11 4:40 ` Girish K S
2012-09-11 4:46 ` Jaehoon Chung
2012-09-11 5:46 ` Seungwon Jeon
2012-09-11 5:58 ` Girish K S
2012-09-11 6:39 ` Seungwon Jeon
2012-09-11 7:11 ` Girish K S
2012-09-11 7:14 ` Girish K S
2012-09-12 2:21 ` Seungwon Jeon
2012-09-12 4:08 ` Girish K S
2012-09-17 11:15 ` Will Newton
2012-09-19 6:03 ` Chris Ball [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=m3sjaeim6p.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=James.Hogan@imgtec.com \
--cc=girish.shivananjappa@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--cc=will.newton@gmail.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