public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@rcn.com.hk>
To: Adrian Cox <adrian@humboldt.co.uk>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Thomas Sailer <sailer@scs.ch>,
	linux-kernel@vger.kernel.org
Subject: Re: via82cxxx_audio locking problems
Date: Fri, 21 Sep 2001 16:50:44 +0800	[thread overview]
Message-ID: <3BAAFF64.971B6D28@rcn.com.hk> (raw)
In-Reply-To: <Pine.LNX.3.96.1010920112905.26319I-100000@mandrakesoft.mandrakesoft.com> <3BAAF129.1090104@humboldt.co.uk> <3BAAFC04.1F7B9C7C@rcn.com.hk>

David Chow ¼g¹D¡G
> 
> Adrian Cox ¼g¹D¡G
> >
> > Jeff Garzik wrote:
> >
> > > On Thu, 20 Sep 2001, Thomas Sailer wrote:
> > >>   Dropping and reacquiring syscall_sem around interruptible_sleep_on
> > >>   in via_dsp_do_read, via_dsp_do_write and via_dsp_drain_playback
> > >>   should solve the problem. Does anyone see a problem with this?
> >
> > > Is there a possibility of do_read being re-entered during that window?
> > > I agree its a problem but the solution sounds racy?
> >
> > What's probably needed is one semaphore to lock read/write and ioctls
> > that look at the playback engine, and another semaphore to lock accesses
> > to the AC97 codec. That may be simpler to implement than dropping and
> > releasing the syscall_sem.
> >
> > --
> > Adrian Cox   http://www.humboldt.co.uk/
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> I receive the same problem when probing the via sound module. Since I am
> in a motherboard design project which I also uses the AC97 interface
> from VIA. The sample board from VIA didn't have any problem, but have 3
> motherboard from 3rd party, each of them uses the VIA694X + VIA686A,
> only one of them have no problem using the sound module, I think it is a
> hardware problem or the module itself didn't handle some cases. It seems
> it should be the same for hardware design, since different codec may
> have different effect on the module. All boards are tested with
> Windows98 and Linux and then all works fine runnign Windows. The sample
> board from VIA is a VIA694T + VIA686B which all of them are pin-2-pin
> compatible with the old 694X+686A. I am sure the problem is from the
> driver, but it is hardware dependent??? My board design just use exactly
> the same chips of the VIA sample board, then we will be save using the
> via_82cxxx module properly. I will try to find out which codec is the
> trouble boards using. The one I'm surely stable without locking is using
> the VIA codec VT1611A . Does you guys require more information about the
> codec specs? I can get them from VIA if you want. Thanks.
> 
> regards,
> 
> David
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Just find out the board that cause lock up both uses a Yamaha codec.

      reply	other threads:[~2001-09-21  8:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-20  8:39 via82cxxx_audio locking problems Thomas Sailer
2001-09-20 11:33 ` Nicholas Knight
2001-09-20 12:07   ` Adrian Cox
2001-09-20 12:24     ` Nicholas Knight
2001-09-20 13:40       ` André Dahlqvist
2001-09-20 13:41         ` Thomas Sailer
2001-09-21  9:27         ` Thomas Sailer
2001-09-21 12:06           ` André Dahlqvist
2001-09-21 13:01             ` Lockups fixed! (Was: via82cxxx_audio locking problems) André Dahlqvist
2001-09-20 16:33 ` via82cxxx_audio locking problems Jeff Garzik
2001-09-21  7:50   ` Adrian Cox
2001-09-21  8:36     ` David Chow
2001-09-21  8:50       ` David Chow [this message]

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=3BAAFF64.971B6D28@rcn.com.hk \
    --to=davidchow@rcn.com.hk \
    --cc=adrian@humboldt.co.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sailer@scs.ch \
    /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