Le 30/04/2025 à 02:23, Mark Brown a écrit :
On Mon, Apr 28, 2025 at 11:20:42AM +0200, Christophe Leroy wrote:
Le 10/04/2025 à 15:47, Mark Brown a écrit :
Would it be possible to get this patch into one of the v6.15 rc as it is a
bug fix ?
It appears to be queued as a fix, could you be mo
On Mon, Apr 28, 2025 at 11:20:42AM +0200, Christophe Leroy wrote:
> Le 10/04/2025 à 15:47, Mark Brown a écrit :
> Would it be possible to get this patch into one of the v6.15 rc as it is a
> bug fix ?
It appears to be queued as a fix, could you be more specific please?
Please delete unneeded con
Hi Mark,
Le 10/04/2025 à 15:47, Mark Brown a écrit :
On Thu, 10 Apr 2025 11:16:43 +0200, Herve Codina wrote:
On SNDRV_PCM_TRIGGER_START event, audio data pointers are not reset.
This leads to wrong data buffer usage when multiple TRIGGER_START are
received and ends to incorrect buffer usage b
On Thu, 10 Apr 2025 11:16:43 +0200, Herve Codina wrote:
> On SNDRV_PCM_TRIGGER_START event, audio data pointers are not reset.
>
> This leads to wrong data buffer usage when multiple TRIGGER_START are
> received and ends to incorrect buffer usage between the user-space and
> the driver. Indeed, th
Le 10/04/2025 à 11:16, Herve Codina a écrit :
On SNDRV_PCM_TRIGGER_START event, audio data pointers are not reset.
This leads to wrong data buffer usage when multiple TRIGGER_START are
received and ends to incorrect buffer usage between the user-space and
the driver. Indeed, the driver can re
On SNDRV_PCM_TRIGGER_START event, audio data pointers are not reset.
This leads to wrong data buffer usage when multiple TRIGGER_START are
received and ends to incorrect buffer usage between the user-space and
the driver. Indeed, the driver can read data that are not already set by
the user-space
