From: Maxime Ripard <maxime@cerno.tech>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Tobias Schramm <t.schramm@manjaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: sunxi-ng: v3s: add support for variable rate audio pll output
Date: Thu, 18 Feb 2021 10:44:26 +0100 [thread overview]
Message-ID: <20210218094426.fc5pxmz463fivm2w@gilmour> (raw)
In-Reply-To: <2BA0A0C7-DA37-486B-B12F-C485F1000F8E@aosc.io>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Thu, Feb 18, 2021 at 05:21:16PM +0800, Icenowy Zheng wrote:
>
>
> 于 2021年2月18日 GMT+08:00 下午5:18:39, Tobias Schramm <t.schramm@manjaro.org> 写到:
> >Hi Icenowy,
> >
> > > We have introducee SDM-based accurate audio PLL on several
> >> other SoCs. Some people is quite sensitive about audio-related
> >things.
> > >
> >While it is possible to support 24MHz * 128 / 25 / 5 = 24.576MHz
> >without
> >delta sigma modulation, matching 22.5792MHz is indeed not possible. I
> >read you'd prefer me to use SDM like the other SoCs though? Shall I
> >send
> >a v2 utilizing SDM?
>
> Yes, I think so.
Yes I'd rather have consistency about how we deal with this across all SoCs
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-02-18 11:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 13:57 Tobias Schramm
2021-02-18 7:58 ` Maxime Ripard
2021-02-18 8:04 ` Icenowy Zheng
2021-02-18 8:08 ` Chen-Yu Tsai
2021-02-18 9:18 ` Tobias Schramm
2021-02-18 9:21 ` Icenowy Zheng
2021-02-18 9:44 ` Maxime Ripard [this message]
2021-02-18 8:51 ` Tobias Schramm
2021-02-18 8:53 ` Tobias Schramm
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=20210218094426.fc5pxmz463fivm2w@gilmour \
--to=maxime@cerno.tech \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=t.schramm@manjaro.org \
--cc=wens@csie.org \
/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®