From: Jaehoon Chung <jh80.chung@samsung.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Chris Ball <cjb@laptop.org>, Will Newton <will.newton@imgtec.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH] mmc: dw_mmc: modified the DMA threshold for SD card
Date: Mon, 26 Sep 2011 13:24:20 +0900 [thread overview]
Message-ID: <4E7FFE74.3090000@samsung.com> (raw)
In-Reply-To: <4E7B0A58.8040408@imgtec.com>
James Hogan wrote:
> On 09/22/2011 11:01 AM, Jaehoon Chung wrote:
>> This patch modified the DMA threshold.
>>
>> I didn't know exactly why need this threshold.
>> But if this value is 16, we didn't read SCR register for SD card.
>> Because in mmc_app_send_scr this values are used data.blocks=1 and data.blksz=8.
>> (data.blocks * data.blksz = 8...so return -EINVAL)
>
> The idea is that for a small transaction the time to set up the DMA is
> probably not worth the effort, therefore it does it using PIO mode (see
> dw_mci_submit_data, if dw_mci_submit_data_dma fails, it sets itself up
> for pio mode instead).
Is there some reason that threshold is set 16?
>
> So if it's using PIO mode and the SCR cannot be read, then PIO mode is
> broken. What's the value of the register HCON? dw_mci_probe reads it and
> decides which pio push and pull function to use based on the host data
> width. I've only tested one of them as we only have one configuration of
> hardware available, but you may have a different one.
i used push/pull_data_32. What do you doubt this problem?
Best regards,
Jaehon Chung
next prev parent reply other threads:[~2011-09-26 4:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 10:01 [PATCH] mmc: dw_mmc: modified the DMA threshold for SD card Jaehoon Chung
2011-09-22 10:13 ` James Hogan
2011-09-26 4:24 ` Jaehoon Chung [this message]
2011-09-26 8:25 ` James Hogan
2011-09-26 8:34 ` Jaehoon Chung
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=4E7FFE74.3090000@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=james.hogan@imgtec.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=will.newton@imgtec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.