From: Ben Dooks <ben@trinity.fluff.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Chris Ball <cjb@laptop.org>, Simon <horms@verge.net.au>,
Magnus <magnus.damm@gmail.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/3] mmc: block: add block number limitation flag for lultiple block read
Date: Fri, 30 May 2014 12:46:54 +0100 [thread overview]
Message-ID: <20140530114654.GF6241@trinity.fluff.org> (raw)
In-Reply-To: <538864C1.2040203@samsung.com>
On Fri, May 30, 2014 at 08:00:17PM +0900, Jaehoon Chung wrote:
> Hi, Kuninori.
>
> Subject has the typo. lultiple -> multiple?
> I didn't know why you need this patch. Would you use the MMC_CAP2_NO_MULTI_READ?
> And I think...it's not good that used the card's capability flags to fix your H/W bug.
If you do that, then there is around a 8-10x performance penalty.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
WARNING: multiple messages have this Message-ID (diff)
From: Ben Dooks <ben@trinity.fluff.org>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Chris Ball <cjb@laptop.org>, Simon <horms@verge.net.au>,
Magnus <magnus.damm@gmail.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 1/3] mmc: block: add block number limitation flag for lultiple block read
Date: Fri, 30 May 2014 11:46:54 +0000 [thread overview]
Message-ID: <20140530114654.GF6241@trinity.fluff.org> (raw)
In-Reply-To: <538864C1.2040203@samsung.com>
On Fri, May 30, 2014 at 08:00:17PM +0900, Jaehoon Chung wrote:
> Hi, Kuninori.
>
> Subject has the typo. lultiple -> multiple?
> I didn't know why you need this patch. Would you use the MMC_CAP2_NO_MULTI_READ?
> And I think...it's not good that used the card's capability flags to fix your H/W bug.
If you do that, then there is around a 8-10x performance penalty.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
next prev parent reply other threads:[~2014-05-30 11:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 10:40 [PATCH 0/3] mmc: Kuninori Morimoto
2014-05-30 10:40 ` Kuninori Morimoto
2014-05-30 10:40 ` [PATCH 1/3] mmc: block: add block number limitation flag for lultiple block read Kuninori Morimoto
2014-05-30 10:40 ` Kuninori Morimoto
2014-05-30 11:00 ` Jaehoon Chung
2014-05-30 11:00 ` Jaehoon Chung
2014-05-30 11:14 ` Kuninori Morimoto
2014-05-30 11:14 ` Kuninori Morimoto
2014-05-30 11:46 ` Ben Dooks [this message]
2014-05-30 11:46 ` Ben Dooks
2014-05-30 13:25 ` Sergei Shtylyov
2014-05-30 13:25 ` Sergei Shtylyov
2014-05-30 13:40 ` Kuninori Morimoto
2014-05-30 13:40 ` Kuninori Morimoto
2014-05-30 10:40 ` [PATCH 2/3] mmc: sdhi: tidyup mmc_data setting for R-Car SDHI Kuninori Morimoto
2014-05-30 10:40 ` Kuninori Morimoto
2014-05-30 10:40 ` [PATCH 3/3] mmc: tmio: care about DMA tx/rx addr offset Kuninori Morimoto
2014-05-30 10:40 ` Kuninori Morimoto
2014-05-30 10:56 ` Ben Dooks
2014-05-30 10:56 ` Ben Dooks
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=20140530114654.GF6241@trinity.fluff.org \
--to=ben@trinity.fluff.org \
--cc=cjb@laptop.org \
--cc=horms@verge.net.au \
--cc=jh80.chung@samsung.com \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@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 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.