Re: Overflow in calculating audio timestamp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Pierre-Louis Bossart <pierre-louis.bossart@xxxxxxxxxxxxxxx>, Jaroslav Kysela <perex@xxxxxxxx>, o-takashi@xxxxxxxxxxxxx
Subject: Re: Overflow in calculating audio timestamp
From: Alan Young <consult.awy@xxxxxxxxx>
Date: Mon, 6 Feb 2023 15:25:08 +0000
Cc: alsa-devel@xxxxxxxxxxxxxxxx
In-reply-to: <4398e3f3-ea2f-1e23-d64b-39723e4790d2@linux.intel.com>
References: <70ff4e3a-b171-131c-a039-4fc99aa4bbfc@gmail.com> <Y9xWlbhPg3PteH5G@workstation> <2598bf64-708c-cf62-e634-44db5a850226@gmail.com> <74350bce-a6ea-c3b8-7b00-4deb47f7e623@perex.cz> <4398e3f3-ea2f-1e23-d64b-39723e4790d2@linux.intel.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0


On 04/02/2023 00:54, Pierre-Louis Bossart wrote:

I am not following how the boundary comes into play for cases where the
timestamp comes directly from a link counter, and is not related to the
DMA hw_ptr at all.

I don't think it does. This is all only for theSNDRV_PCM_AUDIO_TSTAMP_TYPE_DEFAULT case.

References:
- Overflow in calculating audio timestamp
  - From: Alan Young
- Re: Overflow in calculating audio timestamp
  - From: Takashi Sakamoto
- Re: Overflow in calculating audio timestamp
  - From: Alan Young
- Re: Overflow in calculating audio timestamp
  - From: Jaroslav Kysela
- Re: Overflow in calculating audio timestamp
  - From: Pierre-Louis Bossart

Prev by Date: Re: [PATCH 01/19] ASoC: amd: ps: create platform devices based on acp config
Next by Date: [PATCH v2 0/7] ASoC: dt-bindings: meson: covert axg audio to schema
Previous by thread: Re: Overflow in calculating audio timestamp
Next by thread: Re: Overflow in calculating audio timestamp
Index(es):
- Date
- Thread

[Index of Archives] [ALSA User] [Linux Audio Users] [Pulse Audio] [Kernel Archive] [Asterisk PBX] [Photo Sharing] [Linux Sound] [Video 4 Linux] [Gimp] [Yosemite News]