From: Mark Brown <broonie@kernel.org>
To: Ryan Lee <RyanS.Lee@maximintegrated.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Grant Grundler <grundler@chromium.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Benson Leung <bleung@chromium.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ryan.lee.maxim@gmail.com" <ryan.lee.maxim@gmail.com>
Subject: Re: [PATCH V2] ASoC: max98373: Added max98373_reset for stable amp reset
Date: Wed, 28 Nov 2018 09:49:55 +0000 [thread overview]
Message-ID: <20181128094955.GG6828@sirena.org.uk> (raw)
In-Reply-To: <20181128031926.7157-1-ryans.lee@maximintegrated.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
On Wed, Nov 28, 2018 at 03:20:16AM +0000, Ryan Lee wrote:
> Signed-off-by: Ryan Lee <ryans.lee@maximintegrated.com>
> ---
Not seeing a changelog here like I asked for :(
> Changes : Created max98373_reset function to minimize code duplication.
> Changed regmap_write to regmap_update_bits. Other bits except LSB need to be masked.
> Added reset verification step to make sure software reset is completed well. Software reset is done in 10ms in normal case.
> Revision ID is available when the amp is in the idle state which means software reset is completed.
> Software reset will be performed maximum 3 times to avoid amp reset failure. Generally it is done in the first trial.
> sleep time after software reset is increased + 30ms for every retrial. Maximum possible msleep time is 100 ms (initial 10 ms + 30 ms * 3 times).
This looks like it's supposed to be a changelog but it isn't one?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-28 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 3:20 Ryan Lee
2018-11-28 9:49 ` Mark Brown [this message]
2018-11-28 17:07 ` Ryan Lee
2018-11-29 1:55 ` Grant Grundler
2018-11-29 11:26 ` Mark Brown
2018-11-30 3:17 ` Ryan Lee
2018-11-30 3:10 ` Ryan Lee
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=20181128094955.GG6828@sirena.org.uk \
--to=broonie@kernel.org \
--cc=RyanS.Lee@maximintegrated.com \
--cc=alsa-devel@alsa-project.org \
--cc=bleung@chromium.org \
--cc=grundler@chromium.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=ryan.lee.maxim@gmail.com \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®