From: Jarkko Nikula <jhnikula@gmail.com>
To: kishore kadiyala <kishorek.kadiyala@gmail.com>
Cc: Vimal Singh <vimal.newwork@gmail.com>,
Madhusudhan <madhu.cr@ti.com>,
tony@atomide.com, svenkatr@ti.com, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, jarkko.lavinen@nokia.com
Subject: Re: [PATCH-V2] OMAP: Fix for bus width which improves SD card's peformance.
Date: Wed, 31 Mar 2010 16:11:53 +0300 [thread overview]
Message-ID: <20100331161153.73d687ee.jhnikula@gmail.com> (raw)
In-Reply-To: <h2p7f9d1ffb1003310003z508e21dbqe37b6e1cad425866@mail.gmail.com>
On Wed, 31 Mar 2010 12:33:01 +0530
kishore kadiyala <kishorek.kadiyala@gmail.com> wrote:
> This patch improves low speeds for SD cards.
> OMAP-MMC controller's can support maximum bus width of '8'.
> when bus width is mentioned as "8" in controller data,the SD
> stack will check whether bus width is "4" and if not it will
> set bus width to "1" and there by degrading performance.
> This patch fixes the issue and improves the performance of
> SD cards.
>
> Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
> Signed-off-by: Venkatraman S <svenkatr@ti.com>
> Acked-by: Madhusudhan Chikkature <madhu.cr@ti.com>
>
> ---
> In V2 : Appended Signed-off by Venkat and Ack by Madhu
>
> Here are my experiment numbers, on a Class 6 SDHC card:
> Read peformance is increased by 220%
> Write Performance is increased by 52%
>
Some results from the BeagleBoard and 2 GB SD card:
sync; time (dd if=/dev/zero of=`date +%s`.bin bs=1M count=100; sync)
-> ~40 % improvement over 4 writes.
time dd if=12700xxxxx.bin of=/dev/null
-> ~96 % improvement over 4 reads.
Feel free to add my tested-by.
Tested-by: Jarkko Nikula <jhnikula@gmail.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Nikula <jhnikula@gmail.com>
To: kishore kadiyala <kishorek.kadiyala@gmail.com>
Cc: Vimal Singh <vimal.newwork@gmail.com>,
Madhusudhan <madhu.cr@ti.com>,
tony@atomide.com, svenkatr@ti.com, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, jarkko.lavinen@nokia.com
Subject: Re: [PATCH-V2] OMAP: Fix for bus width which improves SD card's peformance.
Date: Wed, 31 Mar 2010 16:11:53 +0300 [thread overview]
Message-ID: <20100331161153.73d687ee.jhnikula@gmail.com> (raw)
In-Reply-To: <h2p7f9d1ffb1003310003z508e21dbqe37b6e1cad425866@mail.gmail.com>
On Wed, 31 Mar 2010 12:33:01 +0530
kishore kadiyala <kishorek.kadiyala@gmail.com> wrote:
> This patch improves low speeds for SD cards.
> OMAP-MMC controller's can support maximum bus width of '8'.
> when bus width is mentioned as "8" in controller data,the SD
> stack will check whether bus width is "4" and if not it will
> set bus width to "1" and there by degrading performance.
> This patch fixes the issue and improves the performance of
> SD cards.
>
> Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
> Signed-off-by: Venkatraman S <svenkatr@ti.com>
> Acked-by: Madhusudhan Chikkature <madhu.cr@ti.com>
>
> ---
> In V2 : Appended Signed-off by Venkat and Ack by Madhu
>
> Here are my experiment numbers, on a Class 6 SDHC card:
> Read peformance is increased by 220%
> Write Performance is increased by 52%
>
Some results from the BeagleBoard and 2 GB SD card:
sync; time (dd if=/dev/zero of=`date +%s`.bin bs=1M count=100; sync)
-> ~40 % improvement over 4 writes.
time dd if=12700xxxxx.bin of=/dev/null
-> ~96 % improvement over 4 reads.
Feel free to add my tested-by.
Tested-by: Jarkko Nikula <jhnikula@gmail.com>
next prev parent reply other threads:[~2010-03-31 13:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 14:20 [PATCH] OMAP: Fix for bus width which improves SD card's peformance kishore kadiyala
2010-02-11 14:20 ` kishore kadiyala
2010-02-11 17:34 ` Madhusudhan
2010-02-11 17:34 ` Madhusudhan
2010-03-31 6:07 ` [PATCH-V2] " kishore kadiyala
2010-03-31 6:07 ` kishore kadiyala
2010-03-31 6:27 ` Vimal Singh
2010-03-31 6:27 ` Vimal Singh
2010-03-31 7:03 ` kishore kadiyala
2010-03-31 7:03 ` kishore kadiyala
2010-03-31 13:11 ` Jarkko Nikula [this message]
2010-03-31 13:11 ` Jarkko Nikula
2010-03-31 16:37 ` Madhusudhan
2010-03-31 16:37 ` Madhusudhan
2010-04-01 6:31 ` kishore kadiyala
2010-04-01 6:31 ` kishore kadiyala
2010-04-01 15:41 ` Madhusudhan
2010-04-01 15:41 ` Madhusudhan
2010-04-05 12:56 ` [PATCH v3] " kishore kadiyala
2010-04-05 12:56 ` kishore kadiyala
2010-04-05 16:48 ` Felipe Balbi
2010-04-05 17:19 ` Madhusudhan
2010-04-05 17:19 ` Madhusudhan
2010-04-05 17:43 ` Madhusudhan
2010-04-05 17:43 ` Madhusudhan
2010-04-06 5:00 ` Felipe Balbi
2010-04-06 16:16 ` Madhusudhan
2010-04-06 16:16 ` Madhusudhan
2010-04-06 16:32 ` Felipe Balbi
2010-04-06 16:55 ` Nishanth Menon
2010-04-06 16:57 ` Felipe Balbi
2010-04-06 23:23 ` Madhusudhan
2010-04-06 23:23 ` Madhusudhan
2010-04-06 23:39 ` Nishanth Menon
2010-04-07 0:16 ` Madhusudhan
2010-04-07 0:16 ` Madhusudhan
2010-04-07 0:57 ` Nishanth Menon
2010-04-08 16:57 ` Madhusudhan
2010-04-08 16:57 ` Madhusudhan
2010-04-19 15:36 ` [PATCH v4] " kishore kadiyala
2010-04-19 15:36 ` kishore kadiyala
2010-04-19 15:51 ` kishore kadiyala
2010-04-19 15:51 ` kishore kadiyala
2010-04-22 0:26 ` Madhusudhan
2010-04-22 0:26 ` Madhusudhan
2010-06-14 16:10 ` [PATCH v5] " kishore kadiyala
2010-06-15 8:04 ` kishore kadiyala
2010-06-15 8:07 ` kishore kadiyala
2010-06-30 14:59 ` kishore kadiyala
2010-07-07 14:15 ` kishore kadiyala
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=20100331161153.73d687ee.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=jarkko.lavinen@nokia.com \
--cc=kishorek.kadiyala@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=svenkatr@ti.com \
--cc=tony@atomide.com \
--cc=vimal.newwork@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.