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?
Attachment:
signature.asc
Description: PGP signature
- Follow-Ups:
- Re: [PATCH 09/13] ASoC: ti: davinci-i2s: Enable unexpected frame pulses detection
- From: Bastien Curutchet
- Re: [PATCH 09/13] ASoC: ti: davinci-i2s: Enable unexpected frame pulses detection
- References:
- [PATCH 00/13] ASoC: ti: davinci-i2s: Add features to McBSP driver
- From: Bastien Curutchet
- [PATCH 09/13] ASoC: ti: davinci-i2s: Enable unexpected frame pulses detection
- From: Bastien Curutchet
- [PATCH 00/13] ASoC: ti: davinci-i2s: Add features to McBSP driver
- Prev by Date: Re: [PATCH 04/13] ASoC: ti: davinci-i2s: Replace dev_err with dev_err_probe
- Next by Date: Re: [PATCH 10/13] ASoC: ti: davinci-i2s: Make free-running mode optional
- Previous by thread: [PATCH 09/13] ASoC: ti: davinci-i2s: Enable unexpected frame pulses detection
- Next by thread: Re: [PATCH 09/13] ASoC: ti: davinci-i2s: Enable unexpected frame pulses detection
- Index(es):