From: Chris Ball <cjb@laptop.org>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: 'Kyoungil Kim' <ki0351.kim@samsung.com>,
linux-mmc@vger.kernel.org,
'Jaehoon Chung' <jh80.chung@samsung.com>
Subject: Re: [PATCH v3] mmc: dw_mmc: read all data in FIFO after Data transfer over interrupt in pio mode
Date: Fri, 22 Mar 2013 12:01:21 -0400 [thread overview]
Message-ID: <871ub7qv8u.fsf@octavius.laptop.org> (raw)
In-Reply-To: <001401ce0dc5$ea3b0d20$beb12760$%jun@samsung.com> (Seungwon Jeon's message of "Mon, 18 Feb 2013 19:51:32 +0900")
Hi,
On Mon, Feb 18 2013, Seungwon Jeon wrote:
> Hi Chris,
>
> Could you merge this patch in your tree.
> We've verified.
>
> Thanks,
> Seungwon Jeon
>
> On Tuesday, January 22, 2013, Kyoungil Kim wrote:
>> In dwc manual, the below contents are described.
>> "During end of packet, interrupt is not generated if threshold
>> programming is larger than any remaining data. It is responsibility
>> of host to read remaining bytes on seeing Data Transfer Done
>> interrupt"
>> We also have seen the data cannot be read fully
>> when "sg_miter->length" is less than FIFO size.
>>
>> Signed-off-by: Kyoungil Kim <ki0351.kim@samsung.com>
>> Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
>> Acked-by: Jaehoon Chung <jh80.chung@samsung.com>
Thanks, pushed to mmc-next for 3.10.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2013-03-22 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:46 [PATCH v3] mmc: dw_mmc: read all data in FIFO after Data transfer over interrupt in pio mode Kyoungil Kim
2013-02-18 10:51 ` Seungwon Jeon
2013-03-22 16:01 ` 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=871ub7qv8u.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=ki0351.kim@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.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