From: Dongjin Kim <tobetter@gmail.com>
To: Seungwon Jeon <tgih.jun@samsung.com>
Cc: "'unlisted-recipients:'"@samsung.com,
"'no To-header on input'"@samsung.com,
Jaehoon Chung <jh80.chung@samsung.com>,
Sachin Kamat <sachin.kamat@linaro.org>,
Chris Ball <cjb@laptop.org>, Arnd Bergmann <arnd@arndb.de>,
Thomas Abraham <thomas.abraham@linaro.org>,
Will Newton <will.newton@imgtec.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mmc: dw_mmc: Add MSHC compatible for Exynos4412
Date: Tue, 19 Feb 2013 21:34:27 +0900 [thread overview]
Message-ID: <CADoNuNc2cjOU-PjWgwtB2wo9USMABGdwP=udCBHBYO9jgiLnvw@mail.gmail.com> (raw)
In-Reply-To: <000501ce0e8a$91ef7c30$b5ce7490$%jun@samsung.com>
Hello Seungwon,
Thank you for reviewing and I understand what you mean.
I agree that Exynos5250 and Exynos4412 are not same, no idea how much
they are different because no Exynos5250 spec on my hand. But at least
I assumed that the capabilities below are supported by Exynos4412 in
terms of its datasheet and it does work on my end as expected. :) Also
I assumed it will be separated if one of both become different to add
more capabilities.
MMC_CAP_UHS_DDR50 | MMC_CAP_1_8V_DDR |
MMC_CAP_8_BIT_DATA | MMC_CAP_CMD23,
Maybe my understanding or approach is wrong since I do not have the
information of Exynos5250.
And suggestion do you have?
Regards,
Dongjin.
On Tue, Feb 19, 2013 at 7:19 PM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
> On Tuesday, February 19, 2013, Dongjin Kim wrote:
>> This patch adds the compatible string for MSHC controller of Exynos4412, and
>> share the controller specific properties with Exynos5250 since they have same
>> features. Its driver data name is changed to exynos_drv_data instead SoC
>> specific name.
>
> It's not actually same.
> Exynos4412 doesn't have forward compatibilities for Exynos5250.
> I agree that functionality of exynos_drv_data is common.
> These functions have been implemented for existing Exynos*.
> But in case of caps, it can't applied completely.
> I'm concerning about this.
>
> Thanks,
> Seungwon Jeon
>>
>> Cc: Jaehoon Chung <jh80.chung@samsung.com>
>> Cc: Sachin Kamat <sachin.kamat@linaro.org>
>> Signed-off-by: Dongjin Kim <tobetter@gmail.com>
>> ---
>> drivers/mmc/host/dw_mmc-exynos.c | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/mmc/host/dw_mmc-exynos.c b/drivers/mmc/host/dw_mmc-exynos.c
>> index 4d50da6..38cd03c 100644
>> --- a/drivers/mmc/host/dw_mmc-exynos.c
>> +++ b/drivers/mmc/host/dw_mmc-exynos.c
>> @@ -199,8 +199,8 @@ static int dw_mci_exynos_setup_bus(struct dw_mci *host,
>> return 0;
>> }
>>
>> -/* Exynos5250 controller specific capabilities */
>> -static unsigned long exynos5250_dwmmc_caps[4] = {
>> +/* Exynos4412/Exynos5250 controller specific capabilities */
>> +static unsigned long exynos_dwmmc_caps[4] = {
>> MMC_CAP_UHS_DDR50 | MMC_CAP_1_8V_DDR |
>> MMC_CAP_8_BIT_DATA | MMC_CAP_CMD23,
>> MMC_CAP_CMD23,
>> @@ -208,8 +208,8 @@ static unsigned long exynos5250_dwmmc_caps[4] = {
>> MMC_CAP_CMD23,
>> };
>>
>> -static const struct dw_mci_drv_data exynos5250_drv_data = {
>> - .caps = exynos5250_dwmmc_caps,
>> +static const struct dw_mci_drv_data exynos_drv_data = {
>> + .caps = exynos_dwmmc_caps,
>> .init = dw_mci_exynos_priv_init,
>> .setup_clock = dw_mci_exynos_setup_clock,
>> .prepare_command = dw_mci_exynos_prepare_command,
>> @@ -219,8 +219,10 @@ static const struct dw_mci_drv_data exynos5250_drv_data = {
>> };
>>
>> static const struct of_device_id dw_mci_exynos_match[] = {
>> + { .compatible = "samsung,exynos4412-dw-mshc",
>> + .data = &exynos_drv_data, },
>> { .compatible = "samsung,exynos5250-dw-mshc",
>> - .data = &exynos5250_drv_data, },
>> + .data = &exynos_drv_data, },
>> {},
>> };
>> MODULE_DEVICE_TABLE(of, dw_mci_exynos_match);
>> --
>> 1.7.10.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-02-19 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:06 [PATCH v3] mmc: dw_mmc: Add MSHC compatible for Exynos4412 Dongjin Kim
2013-02-18 22:36 ` Arnd Bergmann
2013-02-19 10:19 ` Seungwon Jeon
2013-02-19 12:34 ` Dongjin Kim [this message]
2013-02-19 16:40 ` Alim Akhtar
2013-02-21 10:53 ` Seungwon Jeon
2013-02-22 1:39 ` Dongjin Kim
2013-02-22 11:16 ` Seungwon Jeon
2013-02-22 15:17 ` [PATCH v4] " Dongjin Kim
2013-03-13 14:17 ` Seungwon Jeon
2013-03-22 16:56 ` Chris Ball
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='CADoNuNc2cjOU-PjWgwtB2wo9USMABGdwP=udCBHBYO9jgiLnvw@mail.gmail.com' \
--to=tobetter@gmail.com \
--cc="'no To-header on input'"@samsung.com \
--cc="'unlisted-recipients:'"@samsung.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=tgih.jun@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=will.newton@imgtec.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;
as well as URLs for NNTP newsgroup(s).