From: Takashi Iwai <tiwai@suse.de>
To: Lauri Kasanen <cand@gmx.com>
Cc: linux-mips@vger.kernel.org, tsbogend@alpha.franken.de, perex@perex.cz
Subject: Re: [PATCH 5/6 v2] sound: Add n64 driver
Date: Mon, 11 Jan 2021 11:11:39 +0100 [thread overview]
Message-ID: <s5h8s8zvl44.wl-tiwai@suse.de> (raw)
In-Reply-To: <20210111114323.d522f6e30a705d0731b41b93@gmx.com>
On Mon, 11 Jan 2021 10:43:23 +0100,
Lauri Kasanen wrote:
>
> On Mon, 11 Jan 2021 09:05:04 +0100
> Takashi Iwai <tiwai@suse.de> wrote:
>
> > On Sun, 10 Jan 2021 18:41:46 +0100,
> > Lauri Kasanen wrote:
> > > It was returning nextpos, but the pointer printk was in bytes. 8192
> > > bytes = 2048 frames.
> >
> > OK, then it must be right.
> >
> > Then I suppose that the update of pos should be changed in a different
> > way; it should always point to the previous nextpos. That is,
> > something like:
> >
> > static void n64audio_push(struct n64audio_t *priv, uint8_t irq)
> > {
> > ....
> > if (irq)
> > priv->chan.pos = priv->chan.nextpos;
> > priv->chan.nextpos += count;
> > priv->chan.nextpos %= priv->chan.bufsize;
> >
> > If we use nextpos as the position, it'll lead to the double steps at
> > the first IRQ handling without snd_pcm_period_elapsed() call (the
> > first step missed it), and this may confuse PCM core.
>
> This almost works, speed is correct, but the last part is played twice.
Oh yes, at the last IRQ, the push should be avoided.
I guess that the code order should be changed to the following way:
1. advance the position for a period size
2. call snd_pcm_period_elapsed()
3. check if the stream is still running
4. copy the next chunk and update nextpos
So, it's something like:
static irqreturn_t n64audio_isr(int irq, void *dev_id)
{
struct n64audio *priv = dev_id;
// Check it's ours
const u32 intrs = n64mi_read_reg(MI_INTR_REG);
if (!(intrs & MI_INTR_AI))
return IRQ_NONE;
n64audio_write_reg(AI_STATUS_REG, 1);
priv->chan.pos += priv->chan.nextpos;
snd_pcm_period_elapsed(priv->chan.substream);
if (priv->chan.substream == SNDRV_PCM_STATE_RUNNING)
n64audio_push(priv);
return IRQ_HANDLED;
}
By calling snd_pcm_period_elapsed(), PCM core detects the end of the
stream and it stops with the state change. Then we can avoid the
unnecessary push after the stop.
The irq argument in n64audio_push() is dropped in the above, as it's
superfluous now.
Takashi
next prev parent reply other threads:[~2021-01-11 10:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 8:35 [PATCH 5/6 v2] sound: Add n64 driver Lauri Kasanen
2021-01-08 9:06 ` Takashi Iwai
2021-01-08 10:13 ` Lauri Kasanen
2021-01-09 7:23 ` Lauri Kasanen
2021-01-09 8:16 ` Takashi Iwai
2021-01-09 17:46 ` Lauri Kasanen
2021-01-09 18:17 ` Takashi Iwai
2021-01-09 20:54 ` Takashi Iwai
2021-01-10 7:15 ` Lauri Kasanen
2021-01-10 10:24 ` Takashi Iwai
2021-01-10 17:03 ` Lauri Kasanen
2021-01-10 17:22 ` Takashi Iwai
2021-01-10 17:41 ` Lauri Kasanen
2021-01-11 8:05 ` Takashi Iwai
2021-01-11 9:43 ` Lauri Kasanen
2021-01-11 10:11 ` Takashi Iwai [this message]
2021-01-11 12:02 ` Lauri Kasanen
2021-01-11 15:25 ` Takashi Iwai
2021-01-11 15:51 ` Lauri Kasanen
2021-01-13 11:57 ` Lauri Kasanen
2021-01-13 12:04 ` Takashi Iwai
2021-01-13 12:14 ` Lauri Kasanen
2021-01-13 12:38 ` Takashi Iwai
2021-01-13 12:49 ` Lauri Kasanen
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=s5h8s8zvl44.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=cand@gmx.com \
--cc=linux-mips@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox