From: Jaehoon Chung <jh80.chung@samsung.com>
To: Yuvaraj Kumar C D <yuvaraj.cd@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
cjb@laptop.org, jh80.chung@samsung.com, tgih.jun@samsung.com,
ks.giri@samsung.com, t.figa@samsung.com, alim.akhtar@samsung.com,
Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>
Subject: Re: [RFC V3 0/4] dw_mmc platform specific private data and SMU init
Date: Thu, 29 Aug 2013 12:05:17 +0900 [thread overview]
Message-ID: <521EBA6D.2070900@samsung.com> (raw)
In-Reply-To: <1377691731-7226-1-git-send-email-yuvaraj.cd@samsung.com>
Hi Yuvaraj,
I have tested on Exynos4 series.
I didn't test for SMU feature. If Seungwon could test or review and confirm this patch,
then looks good to me.
With exynos4 series,
Tested-by: Jaehoon Chung <jh80.chung@samsung.com>
Best Regards.
Jaehoon Chung
On 08/28/2013 09:08 PM, Yuvaraj Kumar C D wrote:
> changes from V2:
> 1.dropped the bypass-smu quirk
> mmc: dw_mmc: exynos: configure SMU in exynos5420.
> 2.Changed the subject line for this patch
> add a quirk for SMU -> configure SMU in exynos5420
>
> mmc: dw_mmc: exynos: configure SMU in exynos5420
> was earlier
> mmc: dw_mmc: exynos: add a quirk for SMU.
>
> changes from V1:
> 1.Added a new RFC patch
> mmc: dw_mmc: socfpga: move socfpga private init
> 2.Avoid code duplication in
> mmc: dw_mmc: exynos: add a quirk for SMU.
>
> Yuvaraj Kumar C D (4):
> mmc: dw_mmc: exynos: move the exynos private init
> mmc: dw_mmc: socfpga: move socfpga private init
> mmc: dw_mmc: move the platform specific init call
> mmc: dw_mmc: exynos: configure SMU in exynos5420.
>
> drivers/mmc/host/dw_mmc-exynos.c | 56 +++++++++++++++++++++++++++----------
> drivers/mmc/host/dw_mmc-pltfm.c | 7 -----
> drivers/mmc/host/dw_mmc-socfpga.c | 29 ++++++++++---------
> drivers/mmc/host/dw_mmc.c | 9 ++++++
> 4 files changed, 65 insertions(+), 36 deletions(-)
>
next prev parent reply other threads:[~2013-08-29 3:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 12:08 [RFC V3 0/4] dw_mmc platform specific private data and SMU init Yuvaraj Kumar C D
2013-08-28 12:08 ` [RFC V3 1/4] mmc: dw_mmc: exynos: move the exynos private init Yuvaraj Kumar C D
2013-08-28 12:08 ` [RFC V3 2/4] mmc: dw_mmc: socfpga: move socfpga " Yuvaraj Kumar C D
2013-08-29 11:59 ` Seungwon Jeon
2013-09-04 19:31 ` Dinh Nguyen
2013-09-05 5:41 ` Yuvaraj Kumar
2013-08-28 12:08 ` [RFC V3 3/4] mmc: dw_mmc: move the platform specific init call Yuvaraj Kumar C D
2013-08-28 12:08 ` [RFC V3 4/4] mmc: dw_mmc: exynos: configure SMU in exynos5420 Yuvaraj Kumar C D
2013-08-29 8:23 ` Seungwon Jeon
2013-08-29 9:08 ` Alim Akhtar
2013-08-29 9:44 ` Seungwon Jeon
2013-08-29 10:04 ` Yuvaraj Kumar
2013-08-29 10:10 ` Yuvaraj Kumar
2013-08-29 10:36 ` Seungwon Jeon
2013-08-29 11:46 ` Tomasz Figa
2013-08-30 3:44 ` Seungwon Jeon
2013-08-29 9:42 ` Yuvaraj Kumar
2013-08-29 3:05 ` Jaehoon Chung [this message]
2013-08-29 7:12 ` [RFC V3 0/4] dw_mmc platform specific private data and SMU init Seungwon Jeon
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=521EBA6D.2070900@samsung.com \
--to=jh80.chung@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=cjb@laptop.org \
--cc=ks.giri@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=t.figa@samsung.com \
--cc=tgih.jun@samsung.com \
--cc=yuvaraj.cd@gmail.com \
--cc=yuvaraj.cd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox