[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a1289d568db3a5008ab11006b4c04952@codethink.co.uk>
Date: Mon, 30 Jul 2018 18:39:52 +0100
From: Ben Dooks <ben.dooks@...ethink.co.uk>
To: Mark Brown <broonie@...nel.org>
Cc: Jon Hunter <jonathanh@...dia.com>,
linux-kernel@...ts.codethink.co.uk, alsa-devel@...a-project.org,
lgirdwood@...il.com, linux-kernel@...r.kernel.org,
thierry.reding@...il.com, linux-tegra@...r.kernel.org
Subject: Re: [PATCH 2/4] ASoC: tegra: Add a TDM configuration
callback
On 2018-07-30 16:07, Mark Brown wrote:
> On Mon, Jul 30, 2018 at 03:04:46PM +0100, Jon Hunter wrote:
>> On 30/07/18 11:18, Mark Brown wrote:
>
>> > DSP modes only care about the rising edge of the LRCLK, the pulse can be
>> > any width without causing interoperability problems.
>
>> OK, thanks I was not able to find a spec that defines this, but I saw
>> a
>> lot of codecs use a single bit clock width. So then equally making the
>> default '1' should also be fine.
>
> There's not really a spec for this, it's just what tends to be
> implemented.
>
>> I still do not like configuring the fsync width in this function. The
>> fsync width needs to be configured for both DSP modes and normal I2S
>> modes and so it seems it would be more appropriate to do this in the
>> hw_params function for this driver.
>
> You *could* just always use the I2S width, it's going to look odd when
> people use a scope but it will work most of the time.
We did this as we were dealing with a legacy system in which we didn't
know if this was important setting or not, so we tried to make the
settings as close as possible to the original nvidia supplied source.
--
Ben
Powered by blists - more mailing lists