On Fri, Apr 05, 2024 at 01:22:41PM +0200, Manuel Lauss wrote:
On Mon, Apr 1, 2024 at 10:11 PM Oswald Buddenhagen
<oswald.buddenhagen@xxxxxx> wrote:
Is this right? The comment on the field says "fifo entries of
AC97/I2S
PSC", which doesn't suggest bytes. The data sheet speaks of "words" and
"byte masks", but without digging into it I can't tell how it would
behave with different sample widths and channel counts (which the driver
does not seem to limit _at all_? what am I missing?).
Each fifo entry contains a sample; wordsize is configured in register
0x08[24:21].
The fifo is 16 samples deep, so you can have 8 stereo frames or 16
mono frames queued up.
ok, so i'm apparently onto something, though the patch is wrong.
But the fifo isn't managed by hand, dma transfers are used instead and
the amount
of transmitted bytes is extracted from DMA information, so I think this change
is pointless.
not *quite* pointless - that field is used for calculating latencies
which are reported to user space. this doesn't really matter except for
pro audio equipment. it also isn't very precise if converter latencies
(which can be rather substantial for delta-sigma convs) are not also
taken into account. it's even more "interesting" when a single pcm
stream is connected to multiple ports with different latencies (e.g.,
s/pdif and analog).
HDA has the proper framework for tracking the entire path's latency and
the driver seems to support that, but from the drivers i surveyed that
was the only one which takes the matter seriously. most (legacy?)
drivers just set it explicitly to zero or leave it at the zero default,
which is a somewhat clear expression of "no clue / don't care".
so if you don't want to bother with getting it right or it is hopeless
due to inaccessible variables, just deleting the code is an option. or
simply ignoring the problem ...
i'm sure the alsa maints will correct me if i got anything wrong. ^^
