From: Chris Ball <cjb@laptop.org>
To: J Freyensee <james_p_freyensee@linux.intel.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chuanxiao Dong <chuanxiao.dong@intel.com>,
Hanumath Prasad <hanumath.prasad@stericsson.com>
Subject: Re: [RFC PATCH] mmc: support background operation
Date: Tue, 16 Aug 2011 12:43:57 -0400 [thread overview]
Message-ID: <m21uwlux0y.fsf@bob.laptop.org> (raw)
In-Reply-To: <4E4A9C40.3000708@linux.intel.com> (J. Freyensee's message of "Tue, 16 Aug 2011 09:35:12 -0700")
Hi,
On Tue, Aug 16 2011, J Freyensee wrote:
> On 08/12/2011 04:14 AM, Jaehoon Chung wrote:
>> Hi mailing.
>>
>> This RFC patch is supported background operation(BKOPS).
>> And if you want to test this patch, must apply "[PATCH v3] mmc:
>> support HPI send command"
>>
>> This patch is based on Hanumath Prasad's patch "mmc: enable
>> background operations for emmc4.41 with HPI support"
>> Hanumath's patch is implemented before applied per forlin's patch
>> "use nonblock mmc request...".
>> This patch is based on 3.1.0-rc1 in mmc-next.
>
> I'm a little confused by this statement. Was this patch done before
> Per Forlin's work, or is this patch the implementation of the
> infrastructure Per Forlin worked on to do non-blocking requests to the
> host controller?
As I understand it, the background operations referred to by this patch
are a feature of the spec/card, whereas the background operations in Per
Forlin's nonblocking patch are merely a feature of the DMA preparation
being done in the kernel (invisibly to the card).
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-08-16 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 11:14 [RFC PATCH] mmc: support background operation Jaehoon Chung
2011-08-16 16:35 ` J Freyensee
2011-08-16 16:43 ` Chris Ball [this message]
2011-08-17 4:03 ` Jaehoon Chung
2011-08-17 16:13 ` J Freyensee
2011-08-18 2:11 ` Jaehoon Chung
2011-08-18 3:16 ` J Freyensee
2011-08-17 8:02 ` Seungwon Jeon
2011-08-17 8:13 ` Jaehoon Chung
2011-08-17 8:30 ` 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=m21uwlux0y.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=chuanxiao.dong@intel.com \
--cc=hanumath.prasad@stericsson.com \
--cc=james_p_freyensee@linux.intel.com \
--cc=jh80.chung@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
/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