Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211104063231.2115-1-huijin.park@samsung.com>
 <CGME20211104063250epcas1p36056caad956e599300146bae77f799d6@epcas1p3.samsung.com>
 <20211104063231.2115-3-huijin.park@samsung.com> <DM6PR04MB657559D2E25D4FF21689116CFC8D9@DM6PR04MB6575.namprd04.prod.outlook.com>
In-Reply-To: <DM6PR04MB657559D2E25D4FF21689116CFC8D9@DM6PR04MB6575.namprd04.prod.outlook.com>
From:   Huijin Park <bbanghj.park@gmail.com>
Date:   Mon, 8 Nov 2021 23:29:07 +0900
Message-ID: <CAMy0x0mUO3Sv-87MTvkn+hpYtKeWW7bEWSrjMopqupFytpOCpQ@mail.gmail.com>
Subject: Re: [PATCH v2 2/2] mmc: core: adjust polling interval for CMD1
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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

2021=EB=85=84 11=EC=9B=94 4=EC=9D=BC (=EB=AA=A9) =EC=98=A4=ED=9B=84 4:27, A=
vri Altman <Avri.Altman@wdc.com>=EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:
>
>
> > 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 whi=
ch
> > 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 r=
educe 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