From: Mark Brown <broonie@kernel.org>
To: Joerg Schambacher <joerg.hifiberry@gmail.com>
Cc: a-krasser@ti.com, joerg@hifiberry.com,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Zhang Qilong" <zhangqilong3@huawei.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ASoC: Adds support for TAS575x to the pcm512x driver
Date: Thu, 7 Sep 2023 17:28:30 +0100 [thread overview]
Message-ID: <bb3e5ccf-6eb5-4a36-9af0-b33f2db68445@sirena.org.uk> (raw)
In-Reply-To: <ZPn4nsypsSXdB3J7@ubuntu>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On Thu, Sep 07, 2023 at 06:21:50PM +0200, Joerg Schambacher wrote:
> And yes, we cannot be sure that future devices may require different
> settings, but I can hardly imagine anything completely different than
> this approach with the usual audio MCLK frequencies.
They may for example be restricted and just not the the incoming MCLK
divider, or require a higher frequency for some fancy processing. In
any case tas_device is just an obviously bad name here - there should be
a flag per quirk, not a flag per entire class of devices.
> > This is probably a separate quirk? I'm a bit concerned about what's
> > turning the PLL off here...
> The PLL should not be used in this specific case where all divisions are
> just divide-by-2's. Your original code does reflect that and turns the
> PLL off. It improves jitter and finally audio performance.
> But in the case of the TAS-devices we even then need the PLL to
> drive the AMP clocks.
That's definitely a separate quirk, and does sound like it should be
driven from the bias management or DAPM more than hw_params.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-07 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 16:12 Joerg Schambacher
2023-09-07 14:21 ` Mark Brown
2023-09-07 16:21 ` Joerg Schambacher
2023-09-07 16:28 ` Mark Brown [this message]
2023-09-11 11:59 ` Joerg Schambacher
2023-09-11 12:11 ` 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=bb3e5ccf-6eb5-4a36-9af0-b33f2db68445@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a-krasser@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=joerg.hifiberry@gmail.com \
--cc=joerg@hifiberry.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=zhangqilong3@huawei.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®