linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huijin Park <bbanghj.park@gmail.com>
To: Avri Altman <Avri.Altman@wdc.com>
Cc: Huijin Park <huijin.park@samsung.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] mmc: core: adjust polling interval for CMD1
Date: Mon, 8 Nov 2021 23:29:07 +0900	[thread overview]
Message-ID: <CAMy0x0mUO3Sv-87MTvkn+hpYtKeWW7bEWSrjMopqupFytpOCpQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR04MB657559D2E25D4FF21689116CFC8D9@DM6PR04MB6575.namprd04.prod.outlook.com>

2021년 11월 4일 (목) 오후 4:27, Avri Altman <Avri.Altman@wdc.com>님이 작성:
>
>
> > In mmc_send_op_cond(), loops are continuously performed at the same
> > interval of 10 ms.  However the behaviour is not good for some eMMC which
> > can be out from a busy state earlier than 10 ms if normal.
> >
> > Rather than fixing about the interval time in mmc_send_op_cond(), let's
> > instead convert into using the common __mmc_poll_for_busy().
> >
> > The reason for adjusting the interval time is that it is important to reduce the
> > eMMC initialization time, especially in devices that use eMMC as rootfs.
> That's an impressive improvement.
> Can you share some of the use-cases in which 10ms reduction in boot time is required?

It can be used as one of the improvements and tuning items that
can make rootfs preparation faster for cold booting.
(e.g. if it is delayed, it outputs "Waiting for root device.." log.)
Above all, I think it is not desirable to delay even though mmc
initialization is done.

Thanks,

>
> Thanks,
> Avri

  reply	other threads:[~2021-11-08 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20211104063243epcas1p4526b49feac019f3eadb33a23dc132976@epcas1p4.samsung.com>
2021-11-04  6:32 ` [PATCH v2 0/2] mmc: core: adjust polling interval for CMD1 Huijin Park
     [not found]   ` <CGME20211104063247epcas1p15d9d319877f1a8519c0ee52a41a176ef@epcas1p1.samsung.com>
2021-11-04  6:32     ` [PATCH v2 1/2] mmc: core: change __mmc_poll_for_busy() parameter type Huijin Park
     [not found]   ` <CGME20211104063250epcas1p36056caad956e599300146bae77f799d6@epcas1p3.samsung.com>
2021-11-04  6:32     ` [PATCH v2 2/2] mmc: core: adjust polling interval for CMD1 Huijin Park
2021-11-04  7:27       ` Avri Altman
2021-11-08 14:29         ` Huijin Park [this message]
2021-11-15 14:54   ` [PATCH v2 0/2] " Ulf Hansson

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=CAMy0x0mUO3Sv-87MTvkn+hpYtKeWW7bEWSrjMopqupFytpOCpQ@mail.gmail.com \
    --to=bbanghj.park@gmail.com \
    --cc=Avri.Altman@wdc.com \
    --cc=huijin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).