From: 유한경 <hankyung.yu@lge.com>
To: 'Adrian Hunter' <adrian.hunter@intel.com>,
'Chanho Min' <chanho.min@lge.com>
Cc: 'Chris Ball' <chris@printf.net>,
'Ulf Hansson' <ulf.hansson@linaro.org>,
'Seungwon Jeon' <tgih.jun@samsung.com>,
'Jaehoon Chung' <jh80.chung@samsung.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
'HyoJun Im' <hyojun.im@lge.com>,
gunho.lee@lge.com
Subject: RE: [PATCH] mmc:core: fix hs400 timing selection
Date: Wed, 29 Oct 2014 08:30:00 +0900 [thread overview]
Message-ID: <00b501cff307$1de03fb0$59a0bf10$@lge.com> (raw)
In-Reply-To: <544F98DD.6040605@intel.com>
Hi I'm Hankyung Yu
I will answer instead Chanho Min
HS200 mode right thing to support less than 52Mhz
However CLK <-> DATA delay timing is dependent on the clock.
So only lower clock without adjusting the timing and mode of a control h/w
ever the problem may occur.
So change the operating mode and to lower the clock.
-----Original Message-----
From: Adrian Hunter [mailto:adrian.hunter@intel.com]
Sent: Tuesday, October 28, 2014 10:24 PM
To: Chanho Min
Cc: Chris Ball; Ulf Hansson; Seungwon Jeon; Jaehoon Chung; linux-
mmc@vger.kernel.org; linux-kernel@vger.kernel.org; HyoJun Im; gunho.lee@lge.
com; Hankyung Yu
Subject: Re: [PATCH] mmc:core: fix hs400 timing selection
On 22/10/14 05:55, Chanho Min wrote:
> According to JEDEC v5.01 spec (6.6.5), In order to switch to HS400
> mode, host should perform the following steps.
>
> 1. HS200 mode selection completed
> 2. Set HS_TIMING to 0x01(High Speed)
> 3. Host changes frequency to =< 52MHz 4. Set the bus width to DDR
> 8bit (CMD6) 5. Host may read Driver Strength (CMD8) 6. Set HS_TIMING
> to 0x03 (HS400)
>
> In current implementation, the order of 2 and 3 is reversed.
But HS200 mode supports running at speeds less than 52 MHz whereas High
Speed mode does not support running at speeds greater than
52 MHz.
So the switch command might succeed, but the subsequent send_status command
(see __mmc_switch) could be expected to fail unless the frequency is
changed first.
> The HS_TIMING field should be set to 0x1 before the clock frequency is
> set to a value not greater than 52 MHz. Otherwise, Initialization of
> timing can be failed. Also, the host contoller's UHS timing mode
> should be set to DDR50 after the bus width is set to DDR 8bit.
>
> Signed-off-by: Hankyung Yu <hankyung.yu@lge.com>
> Signed-off-by: Chanho Min <chanho.min@lge.com>
> ---
> drivers/mmc/core/mmc.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c index
> a301a78..52f78e0 100644
> --- a/drivers/mmc/core/mmc.c
> +++ b/drivers/mmc/core/mmc.c
> @@ -1061,9 +1061,6 @@ static int mmc_select_hs400(struct mmc_card *card)
> * Before switching to dual data rate operation for HS400,
> * it is required to convert from HS200 mode to HS mode.
> */
> - mmc_set_timing(card->host, MMC_TIMING_MMC_HS);
> - mmc_set_bus_speed(card);
> -
> err = __mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> EXT_CSD_HS_TIMING, EXT_CSD_TIMING_HS,
> card->ext_csd.generic_cmd6_time, @@ -1074,6
+1071,14 @@ static
> int mmc_select_hs400(struct mmc_card *card)
> return err;
> }
>
> + /*
> + * According to JEDEC v5.01 spec (6.6.5), Clock frequency should
> + * be set to a value not greater than 52MHz after the HS_TIMING
> + * field is set to 0x1.
> + */
> + mmc_set_timing(card->host, MMC_TIMING_MMC_HS);
> + mmc_set_bus_speed(card);
> +
> err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> EXT_CSD_BUS_WIDTH,
> EXT_CSD_DDR_BUS_WIDTH_8,
> @@ -1084,6 +1089,8 @@ static int mmc_select_hs400(struct mmc_card *card)
> return err;
> }
>
> + mmc_set_timing(card->host, MMC_TIMING_MMC_DDR52);
> +
> err = __mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> EXT_CSD_HS_TIMING, EXT_CSD_TIMING_HS400,
> card->ext_csd.generic_cmd6_time,
>
WARNING: multiple messages have this Message-ID (diff)
From: 유한경 <hankyung.yu@lge.com>
To: "'Adrian Hunter'" <adrian.hunter@intel.com>,
"'Chanho Min'" <chanho.min@lge.com>
Cc: "'Chris Ball'" <chris@printf.net>,
"'Ulf Hansson'" <ulf.hansson@linaro.org>,
"'Seungwon Jeon'" <tgih.jun@samsung.com>,
"'Jaehoon Chung'" <jh80.chung@samsung.com>,
<linux-mmc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"'HyoJun Im'" <hyojun.im@lge.com>, <gunho.lee@lge.com>
Subject: RE: [PATCH] mmc:core: fix hs400 timing selection
Date: Wed, 29 Oct 2014 08:30:00 +0900 [thread overview]
Message-ID: <00b501cff307$1de03fb0$59a0bf10$@lge.com> (raw)
In-Reply-To: <544F98DD.6040605@intel.com>
Hi I'm Hankyung Yu
I will answer instead Chanho Min
HS200 mode right thing to support less than 52Mhz
However CLK <-> DATA delay timing is dependent on the clock.
So only lower clock without adjusting the timing and mode of a control h/w
ever the problem may occur.
So change the operating mode and to lower the clock.
-----Original Message-----
From: Adrian Hunter [mailto:adrian.hunter@intel.com]
Sent: Tuesday, October 28, 2014 10:24 PM
To: Chanho Min
Cc: Chris Ball; Ulf Hansson; Seungwon Jeon; Jaehoon Chung; linux-
mmc@vger.kernel.org; linux-kernel@vger.kernel.org; HyoJun Im; gunho.lee@lge.
com; Hankyung Yu
Subject: Re: [PATCH] mmc:core: fix hs400 timing selection
On 22/10/14 05:55, Chanho Min wrote:
> According to JEDEC v5.01 spec (6.6.5), In order to switch to HS400
> mode, host should perform the following steps.
>
> 1. HS200 mode selection completed
> 2. Set HS_TIMING to 0x01(High Speed)
> 3. Host changes frequency to =< 52MHz 4. Set the bus width to DDR
> 8bit (CMD6) 5. Host may read Driver Strength (CMD8) 6. Set HS_TIMING
> to 0x03 (HS400)
>
> In current implementation, the order of 2 and 3 is reversed.
But HS200 mode supports running at speeds less than 52 MHz whereas High
Speed mode does not support running at speeds greater than
52 MHz.
So the switch command might succeed, but the subsequent send_status command
(see __mmc_switch) could be expected to fail unless the frequency is
changed first.
> The HS_TIMING field should be set to 0x1 before the clock frequency is
> set to a value not greater than 52 MHz. Otherwise, Initialization of
> timing can be failed. Also, the host contoller's UHS timing mode
> should be set to DDR50 after the bus width is set to DDR 8bit.
>
> Signed-off-by: Hankyung Yu <hankyung.yu@lge.com>
> Signed-off-by: Chanho Min <chanho.min@lge.com>
> ---
> drivers/mmc/core/mmc.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c index
> a301a78..52f78e0 100644
> --- a/drivers/mmc/core/mmc.c
> +++ b/drivers/mmc/core/mmc.c
> @@ -1061,9 +1061,6 @@ static int mmc_select_hs400(struct mmc_card *card)
> * Before switching to dual data rate operation for HS400,
> * it is required to convert from HS200 mode to HS mode.
> */
> - mmc_set_timing(card->host, MMC_TIMING_MMC_HS);
> - mmc_set_bus_speed(card);
> -
> err = __mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> EXT_CSD_HS_TIMING, EXT_CSD_TIMING_HS,
> card->ext_csd.generic_cmd6_time, @@ -1074,6
+1071,14 @@ static
> int mmc_select_hs400(struct mmc_card *card)
> return err;
> }
>
> + /*
> + * According to JEDEC v5.01 spec (6.6.5), Clock frequency should
> + * be set to a value not greater than 52MHz after the HS_TIMING
> + * field is set to 0x1.
> + */
> + mmc_set_timing(card->host, MMC_TIMING_MMC_HS);
> + mmc_set_bus_speed(card);
> +
> err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> EXT_CSD_BUS_WIDTH,
> EXT_CSD_DDR_BUS_WIDTH_8,
> @@ -1084,6 +1089,8 @@ static int mmc_select_hs400(struct mmc_card *card)
> return err;
> }
>
> + mmc_set_timing(card->host, MMC_TIMING_MMC_DDR52);
> +
> err = __mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> EXT_CSD_HS_TIMING, EXT_CSD_TIMING_HS400,
> card->ext_csd.generic_cmd6_time,
>
next prev parent reply other threads:[~2014-10-28 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 2:55 [PATCH] mmc:core: fix hs400 timing selection Chanho Min
2014-10-28 4:38 ` Jaehoon Chung
2014-10-28 23:52 ` 유한경
2014-10-28 23:52 ` 유한경
2014-10-29 2:05 ` Jaehoon Chung
2014-10-29 5:14 ` 유한경
2014-10-29 5:14 ` 유한경
2014-10-28 13:23 ` Adrian Hunter
2014-10-28 23:30 ` 유한경 [this message]
2014-10-28 23:30 ` 유한경
2014-10-29 9:33 ` Adrian Hunter
2014-10-29 23:27 ` 유한경
2014-10-29 23:27 ` 유한경
[not found] ` <00cb01cff5a4$c746a090$55d3e1b0$@min@lge.com>
2014-11-07 10:18 ` Adrian Hunter
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='00b501cff307$1de03fb0$59a0bf10$@lge.com' \
--to=hankyung.yu@lge.com \
--cc=adrian.hunter@intel.com \
--cc=chanho.min@lge.com \
--cc=chris@printf.net \
--cc=gunho.lee@lge.com \
--cc=hyojun.im@lge.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=tgih.jun@samsung.com \
--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.