[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180824000807.GF53155@dtor-ws>
Date: Thu, 23 Aug 2018 17:08:07 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: ryans.lee@...imintegrated.com, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
lkml <linux-kernel@...r.kernel.org>, ryan.lee.maxim@...il.com
Subject: Re: [PATCH] ASoC: max98373: Added 10ms delay after amp software reset
On Thu, Aug 23, 2018 at 10:51:07AM +0100, Mark Brown wrote:
> On Wed, Aug 22, 2018 at 05:31:04PM -0700, Dmitry Torokhov wrote:
> > On Wed, Aug 22, 2018 at 5:21 PM Ryan Lee <ryans.lee@...imintegrated.com> wrote:
> > > + mdelay(10);
>
> > Is it really necessary for the CPU to spin for 10msec here?
> > usleep_range() would be better solution.
>
> Or msleep() for that matter, it's not going ot be the end of the world
> if we delay a bit too long.
Frankly, I'd rather we did not introduce extra delays. I do not know if
we use this part, but on ChromeOS we are interested in shaving as much
from the boot time as possible and 10 msecs here and 10 msecs there do
add up.
Thanks.
--
Dmitry
Powered by blists - more mailing lists