From: Jaehoon Chung <jh80.chung@samsung.com>
To: Hyeonsu Kim <hyeonsu.kim@samsung.com>
Cc: linux-mmc@vger.kernel.org, cjb@laptop.org,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
kyungmin.park@samsung.com, tgih.jun@samsung.com
Subject: Re: [PATCH] mmc: dw_mmc: fixed a wrong UHS_REG 16 bit clear
Date: Fri, 22 Feb 2013 10:46:53 +0900 [thread overview]
Message-ID: <5126CE0D.9010400@samsung.com> (raw)
In-Reply-To: <1361496450-12647-1-git-send-email-hyeonsu.kim@samsung.com>
On 02/22/2013 10:27 AM, Hyeonsu Kim wrote:
> In the legacy code, driver clear not only UHS_REG 16 bit also 0-15bit.
> If we use UHS-1 mode spec card like SDR50, SDR104. UHS_REG 0-15 should be set by
> 1 according to slot id. In this case, legacy code can make problem.
UHS_REG register is consist of DDR_REG[31:16] and VOLT_REG[15:0].
Before adjusting this patch, bit[15:0] is always cleared.
So this patch looks good to me.
Acked-by: Jaehoon Chung <jh80.chung@samsung.com>
>
> Signed-off-by: Hyeonsu Kim <hyeonsu.kim@samsung.com>
> ---
> drivers/mmc/host/dw_mmc.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
> index 323c502..390c15c 100644
> --- a/drivers/mmc/host/dw_mmc.c
> +++ b/drivers/mmc/host/dw_mmc.c
> @@ -789,9 +789,9 @@ static void dw_mci_set_ios(struct mmc_host *mmc, struct mmc_ios *ios)
>
> /* DDR mode set */
> if (ios->timing == MMC_TIMING_UHS_DDR50)
> - regs |= (0x1 << slot->id) << 16;
> + regs |= ((0x1 << slot->id) << 16);
> else
> - regs &= ~(0x1 << slot->id) << 16;
> + regs &= ~((0x1 << slot->id) << 16);
>
> mci_writel(slot->host, UHS_REG, regs);
>
>
next prev parent reply other threads:[~2013-02-22 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 1:27 [PATCH] mmc: dw_mmc: fixed a wrong UHS_REG 16 bit clear Hyeonsu Kim
2013-02-22 1:46 ` Jaehoon Chung [this message]
2013-02-22 11:16 ` Seungwon Jeon
2013-03-22 16:04 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2013-02-22 0:32 Hyeonsu Kim
2013-02-22 1:12 ` 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=5126CE0D.9010400@samsung.com \
--to=jh80.chung@samsung.com \
--cc=cjb@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=hyeonsu.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=tgih.jun@samsung.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.