From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Haibo Chen <haibo.chen@freescale.com>, linux-mmc@vger.kernel.org
Cc: aisheng.dong@freescale.com, ulf.hansson@linaro.org,
chris@printf.net, shawn.guo@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/6] mmc: sdhci-esdhc-imx: config watermater levles and burst lengths
Date: Wed, 10 Jun 2015 07:36:00 -0700 [thread overview]
Message-ID: <55784B50.6030101@boundarydevices.com> (raw)
In-Reply-To: <1433926244-29244-5-git-send-email-haibo.chen@freescale.com>
Hi Haibo,
On 06/10/2015 01:50 AM, Haibo Chen wrote:
> i.MX7D support eMMC HS400 mode, this mode can run in 8 bit,200MHZ
> DDR mode. So the I/O speed improve a lot compare to SD3.0
>
> The default burst length is 8, if we don't change this value, in
> HS400 mode, when we do eMMC read operation, we can find that the
> clock signal will stop for a period of time. This means the speed
> of data moving on AHB bus is slower than I/O speed. So we should
> improve the speed of data moving on AHB bus.
>
> For imx7d usdhc, this patch set the burst length as 16, and set
> watermater levle as 64. The test result is the clock signal has
> no stop during the eMMC HS400 operation. For other imx usdhc, remain
"watermark", not "watermater".
> the default value: burst length as 8, watermater level as 16.
>
Same goes for the subject.
Also "levels", not "levles", so:
mmc: sdhci-esdhc-imx: config watermark level and burst length
WARNING: multiple messages have this Message-ID (diff)
From: eric.nelson@boundarydevices.com (Eric Nelson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] mmc: sdhci-esdhc-imx: config watermater levles and burst lengths
Date: Wed, 10 Jun 2015 07:36:00 -0700 [thread overview]
Message-ID: <55784B50.6030101@boundarydevices.com> (raw)
In-Reply-To: <1433926244-29244-5-git-send-email-haibo.chen@freescale.com>
Hi Haibo,
On 06/10/2015 01:50 AM, Haibo Chen wrote:
> i.MX7D support eMMC HS400 mode, this mode can run in 8 bit,200MHZ
> DDR mode. So the I/O speed improve a lot compare to SD3.0
>
> The default burst length is 8, if we don't change this value, in
> HS400 mode, when we do eMMC read operation, we can find that the
> clock signal will stop for a period of time. This means the speed
> of data moving on AHB bus is slower than I/O speed. So we should
> improve the speed of data moving on AHB bus.
>
> For imx7d usdhc, this patch set the burst length as 16, and set
> watermater levle as 64. The test result is the clock signal has
> no stop during the eMMC HS400 operation. For other imx usdhc, remain
"watermark", not "watermater".
> the default value: burst length as 8, watermater level as 16.
>
Same goes for the subject.
Also "levels", not "levles", so:
mmc: sdhci-esdhc-imx: config watermark level and burst length
next prev parent reply other threads:[~2015-06-10 14:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:50 [PATCH 0/6] mmc: imx: a few fixes and new feature add Haibo Chen
2015-06-10 8:50 ` Haibo Chen
2015-06-10 8:50 ` [PATCH 1/6] mmc: sdhci-esdhc-imx: add imx7d support and support HS400 Haibo Chen
2015-06-10 8:50 ` Haibo Chen
2015-06-10 8:50 ` [PATCH 2/6] mmc: sdhci-esdhc-imx: add tuning-step seting support Haibo Chen
2015-06-10 8:50 ` Haibo Chen
2015-07-03 11:10 ` Shawn Guo
2015-07-03 11:10 ` Shawn Guo
2015-07-06 3:05 ` Chen Bough
2015-07-06 3:05 ` Chen Bough
2015-07-08 9:00 ` Shawn Guo
2015-07-08 9:00 ` Shawn Guo
2015-06-10 8:50 ` [PATCH 3/6] ARM: dts: imx7d-sdb: add eMMC5.0 support Haibo Chen
2015-06-10 8:50 ` Haibo Chen
2015-06-10 8:50 ` [PATCH 4/6] mmc: sdhci-esdhc-imx: config watermater levles and burst lengths Haibo Chen
2015-06-10 8:50 ` Haibo Chen
2015-06-10 14:36 ` Eric Nelson [this message]
2015-06-10 14:36 ` Eric Nelson
2015-06-10 8:50 ` [PATCH 5/6] mmc: sdhci-esdhc-imx: set back the burst_length_enable bit to 1 Haibo Chen
2015-06-10 8:50 ` Haibo Chen
2015-06-10 8:50 ` [PATCH 6/6] mmc: sdhci-esdhc-imx: add compatible string in binding doc Haibo Chen
2015-06-10 8:50 ` Haibo Chen
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=55784B50.6030101@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=aisheng.dong@freescale.com \
--cc=chris@printf.net \
--cc=haibo.chen@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=ulf.hansson@linaro.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 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.