From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] ALSA: aaci: report FIFO size in frames
Date: Mon, 1 Apr 2024 12:04:51 +0100 [thread overview]
Message-ID: <ZgqU0ygGn3zhbgQw@shell.armlinux.org.uk> (raw)
In-Reply-To: <ZgqSHq6obzwRDfXs@ugly>
On Mon, Apr 01, 2024 at 12:53:18PM +0200, Oswald Buddenhagen wrote:
> On Mon, Apr 01, 2024 at 11:37:27AM +0100, Russell King (Oracle) wrote:
> > runtime->hw.fifo_size is only measured in _frames_ if
> > SNDRV_PCM_INFO_FIFO_IN_FRAMES is set.
> >
> yes, which is exactly why the other hunk in the patch sets it.
>
> > So now I have to ask what caused you to generate this patch. I don't
> > think you've actually run this driver, so presumably it's by []
> > code inspection...
> >
> yes, it was a random find while trying to make sense of this parameter.
The driver worked when I wrote it. The fifo_size contents was correct
when I wrote it. The choice for using bytes here and not setting
SNDRV_PCM_INFO_FIFO_IN_FRAMES means that ALSA correctly takes the
real FIFO size (which is in bytes) and correctly translates that
itself into frames.
I fail to see how this is any better - in fact, I think it's a lot
worse because, as you've pointed out, it doesn't deal with stereo.
In fact, it only supports 16-bit mono, whereas the driver supports
lots more than that.
I think where the confusion comes from is that fifo_depth is the
depth of the hardware FIFO in units of 16-bit quantities, which is
why we multiply by two to get to bytes. 16-bit quantities does not
necessarily equate to ALSA frames - it can be in specific cases but
not always.
As far as I'm concerned, the code is correct as it stands and your
patch will introduce regressions.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-04-01 11:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 10:13 [PATCH] ALSA: aaci: report FIFO size in frames Oswald Buddenhagen
2024-04-01 10:31 ` Russell King (Oracle)
2024-04-01 10:37 ` Russell King (Oracle)
2024-04-01 10:53 ` Oswald Buddenhagen
2024-04-01 11:04 ` Russell King (Oracle) [this message]
2024-04-01 11:45 ` Oswald Buddenhagen
2024-04-01 13:34 ` Russell King (Oracle)
2024-04-01 14:17 ` Oswald Buddenhagen
2024-04-01 20:59 ` Russell King (Oracle)
2024-04-01 23:01 ` Oswald Buddenhagen
2024-04-01 23:25 ` Russell King (Oracle)
2024-04-02 10:46 ` Oswald Buddenhagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgqU0ygGn3zhbgQw@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=oswald.buddenhagen@gmx.de \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.