[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51866f62-460d-4035-bcf1-b9f03cf9be0b@sirena.org.uk>
Date: Fri, 15 Mar 2024 14:09:50 +0000
From: Mark Brown <broonie@...nel.org>
To: Bastien Curutchet <bastien.curutchet@...tlin.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Peter Ujfalusi <peter.ujfalusi@...il.com>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
linux-sound@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
herve.codina@...tlin.com, christophercordahi@...ometrics.ca
Subject: Re: [PATCH 09/13] ASoC: ti: davinci-i2s: Enable unexpected frame
pulses detection
On Fri, Mar 15, 2024 at 12:27:41PM +0100, Bastien Curutchet wrote:
> McBSP can generate an SYNCERR when unexpected frame pulses are
> detected. The driver always disables this feature and ignore the
> unexpected frame pulses.
What does "unexpected" mean?
> Enable the generation of SYNCERR by the McBSP according to the
> 'ti,enable-sync-err' device-tree property.
Why would this be optional, and how is this reported - I'm not seeing
any interrupt handling updates?
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists