From: Takashi Iwai <tiwai@suse.de>
To: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Cc: patches@opensource.cirrus.com, alsa-devel@alsa-project.org,
Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.
Date: Mon, 05 Dec 2022 17:43:12 +0100 [thread overview]
Message-ID: <87sfhtvm1r.wl-tiwai@suse.de> (raw)
In-Reply-To: <20221205145713.23852-1-vitalyr@opensource.cirrus.com>
On Mon, 05 Dec 2022 15:57:13 +0100,
Vitaly Rodionov wrote:
>
> New HW platforms with multiple CS42L42 parts, faster CPU and i2c
> requre some extra delay to allow PLL to settle and lock. Adding
> extra 10ms delay.
>
> Signed-off-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Thanks, applied.
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
<alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock.
Date: Mon, 05 Dec 2022 17:43:12 +0100 [thread overview]
Message-ID: <87sfhtvm1r.wl-tiwai@suse.de> (raw)
In-Reply-To: <20221205145713.23852-1-vitalyr@opensource.cirrus.com>
On Mon, 05 Dec 2022 15:57:13 +0100,
Vitaly Rodionov wrote:
>
> New HW platforms with multiple CS42L42 parts, faster CPU and i2c
> requre some extra delay to allow PLL to settle and lock. Adding
> extra 10ms delay.
>
> Signed-off-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Thanks, applied.
Takashi
next prev parent reply other threads:[~2022-12-05 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 14:57 [PATCH] ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock Vitaly Rodionov
2022-12-05 14:57 ` Vitaly Rodionov
2022-12-05 16:43 ` Takashi Iwai [this message]
2022-12-05 16:43 ` Takashi Iwai
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=87sfhtvm1r.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=vitalyr@opensource.cirrus.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 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.