From: Sameer Pujar <spujar@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
thierry.reding@gmail.com, jonathanh@nvidia.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
Date: Thu, 7 Sep 2023 19:51:13 +0530 [thread overview]
Message-ID: <61ca531e-6138-7abe-74d1-357369134748@nvidia.com> (raw)
In-Reply-To: <2c3371b7-3dae-48d7-8cc8-1acfd5bd267c@sirena.org.uk>
On 07-09-2023 17:21, Mark Brown wrote:
> On Thu, Sep 07, 2023 at 12:22:13PM +0530, Sameer Pujar wrote:
>
>> Fixes: 202e2f774543 ("ASoC: tegra: Add audio graph based card driver")
>> Cc: stable@vger.kernel.org
> This is just a performance improvement rather than a correctness fix as
> far as I can tell?
This was supposed to be a performance improvement. However this is found
to be resolving a DMIC clock discrepancy and suspect is it happens
because of back to back quick PLLA updates. Thought it would be safer to
have this fix in stable releases. May be I should mention these points
to justify the 'Fixes' and 'stable' tag?
next prev parent reply other threads:[~2023-09-07 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 6:52 [PATCH 0/2] Fix redundant PLLA update Sameer Pujar
2023-09-07 6:52 ` [PATCH 1/2] ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol Sameer Pujar
2023-09-07 6:52 ` [PATCH 2/2] ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates Sameer Pujar
2023-09-07 11:51 ` Mark Brown
2023-09-07 14:21 ` Sameer Pujar [this message]
2023-09-07 14:35 ` Mark Brown
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=61ca531e-6138-7abe-74d1-357369134748@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stable@vger.kernel.org \
--cc=thierry.reding@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®