From: Jaehoon Chung <jh80.chung@samsung.com>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Shawn Lin <shawn.lin@rock-chips.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [RFC] improve mmc init sequence
Date: Thu, 17 Mar 2016 19:55:57 +0900 [thread overview]
Message-ID: <56EA8D3D.3080502@samsung.com> (raw)
In-Reply-To: <CAPDyKFq3PWHZpzi4CyPU4WYHdRXK7QVQW7+Ekf+2AkWxey971g@mail.gmail.com>
On 03/17/2016 07:43 PM, Ulf Hansson wrote:
> On 17 March 2016 at 04:41, Shawn Lin <shawn.lin@rock-chips.com> wrote:
>> Hello Ulf,
>> I notice we add MMC_CAP2_NO_SDIO to avoid sending sdio commands
>> during initialization. So that means we can use it to improve mmc init
>> sequence if a specific board use one slot just for emmc or sd. But I realize
>> that we can move a step further to add more cap2 like NO_SD/
>> NO_MMC in order to reduce the boot time. Does that make sense? If the
>> answer is *yes*, I am happy to push some patches for it since I have
>> been doing it on my local tree and testing for a long time.
>
> I am not against it, so please go ahead!
>
> Although, you need to give some proof of the amount of saved boot time
> (or better the decreased initialization time of a couple of different
> cards).
I have already tested with similar sequence..I have remembered there is a benefit for decreasing the booting time.
But i didn't remember how much time is decreased...because it wast too long time ago.
Best Regards,
Jaehoon Chung
>
> Kind regards
> Uffe
> --
> 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
>
>
prev parent reply other threads:[~2016-03-17 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 3:41 [RFC] improve mmc init sequence Shawn Lin
2016-03-17 10:43 ` Ulf Hansson
2016-03-17 10:55 ` Jaehoon Chung [this message]
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=56EA8D3D.3080502@samsung.com \
--to=jh80.chung@samsung.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@rock-chips.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.