From: Jaehoon Chung <jh80.chung@samsung.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <chris@printf.net>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
"tgih.jun@samsung.com" <tgih.jun@samsung.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCHv3 3/4] mmc: dw_mmc: remove the "supports-highspeed" property.
Date: Fri, 30 May 2014 17:12:25 +0900 [thread overview]
Message-ID: <53883D69.4010701@samsung.com> (raw)
In-Reply-To: <CAPDyKFpTTYHtkKjFmbPi6P_xfdfd8Fv8qfpKZMfpQBppRNZLwg@mail.gmail.com>
Hi, Ulf.
On 05/30/2014 05:01 PM, Ulf Hansson wrote:
> On 28 May 2014 07:35, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>> Removed the parser for "supports-highspeed".
>> It can be parsed with "cap-mmc-highsped" or "cap-sd-highspeed" at
>> mmc_of_parse().
>>
>> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
>> ---
>> drivers/mmc/host/dw_mmc.c | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
>> index 3285bdd..34b5210 100644
>> --- a/drivers/mmc/host/dw_mmc.c
>> +++ b/drivers/mmc/host/dw_mmc.c
>> @@ -2281,9 +2281,6 @@ static struct dw_mci_board *dw_mci_parse_dt(struct dw_mci *host)
>> return ERR_PTR(ret);
>> }
>>
>> - if (of_find_property(np, "supports-highspeed", NULL))
>> - pdata->caps |= MMC_CAP_SD_HIGHSPEED | MMC_CAP_MMC_HIGHSPEED;
>> -
>
> According to DT guys, normally we shouldn't remove DT bindings. Thus,
> you need to keep this, unless you can get some of the DT guys to ack
> it.
As you mentioned, this patch didn't need, right?
>
> Though, you still want to move the DTs to use common mmc bindings. And
> you could mark the documentation of the above binding as deprecated.
I added the comment for deprecated into dw-mmc dt-binding doc file.
"[PATCHv3,4/4] ARM: dts: replace the slot property into slot sub-node for dwmmc."
I think this patch can be discarded. then everything is ok.!? :)
If i'm wrong, let me know, plz.
Thank you for sharing the information.
Best Regards,
Jaehoon Chung
>
> Kind regards
> Ulf Hansson
>
next prev parent reply other threads:[~2014-05-30 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 5:35 [PATCHv3 0/4] mmc: fixed the mmc_of_parse for dwmmc Jaehoon Chung
2014-05-28 5:35 ` [PATCHv3 1/4] mmc: host: add slot argument to mmc_of_parse Jaehoon Chung
2014-05-28 5:35 ` [PATCHv3 2/4] mmc: dw_mmc: use the __mmc_of_parse to parse the slot node Jaehoon Chung
2014-05-30 12:53 ` Seungwon Jeon
2014-05-28 5:35 ` [PATCHv3 3/4] mmc: dw_mmc: remove the "supports-highspeed" property Jaehoon Chung
2014-05-30 8:01 ` Ulf Hansson
2014-05-30 8:12 ` Jaehoon Chung [this message]
2014-05-30 12:51 ` Seungwon Jeon
2014-06-03 13:43 ` Mark Rutland
2014-05-30 12:53 ` Seungwon Jeon
2014-05-28 5:35 ` [PATCHv3 4/4] ARM: dts: replace the slot property into slot sub-node for dwmmc Jaehoon Chung
2014-05-30 12:54 ` Seungwon Jeon
2014-05-30 18:15 ` Heiko Stübner
2014-06-02 13:08 ` Dinh Nguyen
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=53883D69.4010701@samsung.com \
--to=jh80.chung@samsung.com \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox