[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3f39a0bb-a766-f646-28b3-a51cf9983c6b@collabora.com>
Date: Fri, 3 Jul 2020 11:38:44 +0200
From: Arnaud Ferraris <arnaud.ferraris@...labora.com>
To: Nicolin Chen <nicoleotsuka@...il.com>
Cc: devicetree@...r.kernel.org, alsa-devel@...a-project.org,
linuxppc-dev@...ts.ozlabs.org, Timur Tabi <timur@...nel.org>,
Xiubo Li <Xiubo.Lee@...il.com>, linux-kernel@...r.kernel.org,
Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Brown <broonie@...nel.org>, kernel@...labora.com,
Fabio Estevam <festevam@...il.com>
Subject: Re: [PATCH 0/4] ASoC: fsl_asrc: allow selecting arbitrary clocks
Hi Nic,
Le 02/07/2020 à 20:42, Nicolin Chen a écrit :
> Hi Arnaud,
>
> On Thu, Jul 02, 2020 at 04:22:31PM +0200, Arnaud Ferraris wrote:
>> The current ASRC driver hardcodes the input and output clocks used for
>> sample rate conversions. In order to allow greater flexibility and to
>> cover more use cases, it would be preferable to select the clocks using
>> device-tree properties.
>
> We recent just merged a new change that auto-selecting internal
> clocks based on sample rates as the first option -- ideal ratio
> mode is the fallback mode now. Please refer to:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20200702&id=d0250cf4f2abfbea64ed247230f08f5ae23979f0
That looks interesting, thanks for pointing this out!
I'll rebase and see how it works for my use-case, will keep you informed.
Regards,
Arnaud
Powered by blists - more mailing lists