[alsa-devel] SGTL500 and its external MCLK

[Mark Brown]

On Mon, Aug 11, 2014 at 08:29:01AM -0400, jonsmirl at gmail.com wrote:

> Mark - how is clock accuracy supposed to be handled in ALSA? Should my
> clocks tell their true rate 22.571428Mhz or lie and say they are
> 22.5792Mhz?

> Are there problems with division truncation from the slightly low
> clock rate lurking in the ALSA code that I need to avoid?

I don't think ALSA should be having to deal with tiny inaccuracies;
ideally the clock API would have some sort of accuracy management in it
(in much the same way that the regulator API does) but otherwise just
impedence match at the edge of the code.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20140813/5827b925/attachment.sig>