public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Nathan Bryant <nbryant@allegientsystems.com>
Cc: saidani@info.unicaen.fr, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TEST of patch proposed for i810 audio
Date: Thu, 27 Dec 2001 00:35:43 -0500	[thread overview]
Message-ID: <3C2AB32F.2010905@redhat.com> (raw)
In-Reply-To: <3C2A56C7.5050801@allegientsystems.com> <3C2A5F24.6090501@allegientsystems.com>

Nathan Bryant wrote:

> Nathan Bryant wrote:
> 
>>
>> maybe this patch will solve your problem, samir, maybe it won't; 
>> regardless, it should fix at least one corner case and is either 
>> obviously correct or start_*c is not ;-)
>>
>> patch is against doug's 0.12.
> 
> 
> [snip]
> 
> attached is a slightly more anal retentive version of my previous patch. 
> as in the previous patch, the goal is to make update_lvi completely 
> self-contained, ie resistant to changes in higher-level code, ie not 
> deadlock even if somebody really sets it up with bad state, also 
> eliminates one if/then/else thinko in 0.12 that could theoretically 
> cause dac to be started when you're trying to record, which would cause 
> a deadlock.
> 
> 
> ------------------------------------------------------------------------
> 
> --- i810_audio.c.12	Wed Dec 19 02:04:06 2001
> +++ linux/drivers/sound/i810_audio.c	Wed Dec 26 18:22:37 2001
> @@ -952,12 +952,16 @@
>  	 * the CIV value to the next sg segment to be played so that when
>  	 * we call start_{dac,adc}, things will operate properly
>  	 */
> -	if (!dmabuf->enable && dmabuf->trigger) {
> -		if(rec && dmabuf->count != dmabuf->dmasize) {
> +	if (!dmabuf->enable && dmabuf->ready) {
> +		if(rec && dmabuf->count < dmabuf->dmasize &&
> +		   (dmabuf->trigger & PCM_ENABLE_INPUT))
> +		{
>  			outb((inb(port+OFF_CIV)+1)&31, port+OFF_LVI);
>  			__start_adc(state);
>  			while( !(inb(port + OFF_CR) & ((1<<4) | (1<<2))) ) ;
> -		} else if(dmabuf->count) {
> +		} else if (!rec && dmabuf->count &&
> +			   (dmabuf->trigger & PCM_ENABLE_OUTPUT))
> +		{
>  			outb((inb(port+OFF_CIV)+1)&31, port+OFF_LVI);
>  			__start_dac(state);
>  			while( !(inb(port + OFF_CR) & ((1<<4) | (1<<2))) ) ;
> 

This looks fine to me.  I've added it to my 0.12 driver, bumped the number 
to 0.13, put it up on my web site 
(http://people.redhat.com/dledford/i810_audio.c.gz) and if that solves 
people's problems then that's what I'll send to Marcello in a day or so.

Thanks Nathan, I've been to busy to look into it the last little bit :-(

-- 

  Doug Ledford <dledford@redhat.com>  http://people.redhat.com/dledford
       Please check my web site for aic7xxx updates/answers before
                       e-mailing me about problems


  reply	other threads:[~2001-12-27  5:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26 23:01 [PATCH] TEST of patch proposed for i810 audio Nathan Bryant
2001-12-26 23:37 ` Nathan Bryant
2001-12-27  5:35   ` Doug Ledford [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-17 21:14 Samir Saidani

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=3C2AB32F.2010905@redhat.com \
    --to=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbryant@allegientsystems.com \
    --cc=saidani@info.unicaen.fr \
    /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