From: Herbert Xu <herbert@gondor.apana.org.au>
To: linux-kernel@vger.kernel.org, tv@lio96.de, jgarzik@pobox.com,
marcelo.tosatti@cyclades.com
Subject: Re: [patch 2.4.29] i810_audio: offset LVI from CIV to avoid stalled start
Date: Fri, 21 Jan 2005 07:27:59 +1100 [thread overview]
Message-ID: <20050120202759.GA32453@gondor.apana.org.au> (raw)
In-Reply-To: <20050120202258.GA7687@tuxdriver.com>
On Thu, Jan 20, 2005 at 03:22:59PM -0500, John W. Linville wrote:
>
> + /* if we are currently stopped, then our CIV is actually set to our
> + * *last* sg segment and we are ready to wrap to the next. However,
> + * if we set our LVI to the last sg segment, then it won't wrap to
> + * the next sg segment, it won't even get a start. So, instead, when
> + * we are stopped, we set both the LVI value and also we increment
> + * the CIV value to the next sg segment to be played so that when
> + * we call start, things will operate properly
> + */
> if (!dmabuf->enable && dmabuf->ready) {
> if (!(dmabuf->trigger & trigger))
> return;
>
> + CIV_TO_LVI(state->card, port, 1);
> +
BTW, I think you want to fix up the last sentence in the comment.
It doesn't seem to correspond to what the code is doing.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2005-01-20 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 20:22 John W. Linville
2005-01-20 20:27 ` Herbert Xu [this message]
2005-01-20 21:07 ` John W. Linville
2005-01-20 21:23 ` John W. Linville
2005-01-20 22:01 ` John W. Linville
2005-01-20 22:07 ` Herbert Xu
2005-01-22 3:02 ` Herbert Xu
2005-01-23 14:48 ` John W. Linville
2005-01-23 14:54 ` John W. Linville
2005-08-03 18:18 ` [patch 2.4.32-pre1] " John W. Linville
2005-08-03 18:35 ` John W. Linville
2005-08-03 18:36 ` [patch 2.4.32-pre1 (corrected)] " John W. Linville
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=20050120202759.GA32453@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=tv@lio96.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
all inboxes | Powered by JetHome®