public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zach Brown <zab@zabbo.net>
To: Lukas Schroeder <lukas@edeal.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] ess maestro, support for hardware volume control
Date: Sat, 9 Jun 2001 13:25:01 -0400	[thread overview]
Message-ID: <20010609132501.C20514@erasmus.off.net> (raw)
In-Reply-To: <20010609190917.A10629@kosmo.edeal.de>
In-Reply-To: <20010609190917.A10629@kosmo.edeal.de>; from lukas@edeal.de on Sat, Jun 09, 2001 at 07:09:17PM +0200

> this patch applies to (at least) 2.4.3 up to and including 2.4.6-pre2.
> It enables the hardware volume control feature of the maestro.

cool.  I had support for this in the mega-patch I posted long ago, but
I never seperated and submitted those changes 'cause I'm a moron.

> By giving hwv=0 to insmod one can explicitly disable it. Setting

can we have a better name like 'hwvol_enable'?

> +		set_mixer(c, 0, val);

careful.  you just used the indirect ac97 registers without holding the
card's lock..  if another processor does a mixer ioctl while this is
happening you'll get weird behaviour.

it looks like you should just be able to spin_{,un}lock(card->lock)
around that call, but the maestro locking is so friggin' twisty.. this
gets even more exciting when the driver uses ac97_codec, which the
mega-patch also had in it.

Fix the locking (and the obscure parameter name? :)) and it looks
fine.. good work.

-- 
 zach

  reply	other threads:[~2001-06-09 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09 17:09 [patch] ess maestro, support for hardware volume control Lukas Schroeder
2001-06-09 17:25 ` Zach Brown [this message]
2001-06-09 18:16   ` Lukas Schroeder
2001-06-09 18:50     ` Zach Brown
2001-06-09 18:58       ` Alan Cox
2001-06-09 19:31 ` Alan Cox
2001-06-09 21:23   ` Ben Pfaff
2001-06-09 22:52     ` Zach Brown
2001-06-10 10:10       ` Abramo Bagnara
2001-06-09 23:36     ` Alan Cox
2001-06-10  3:43       ` Ben Pfaff
2001-06-10 13:08         ` Alan Cox
2001-06-10 17:53           ` Riley Williams
2001-06-12 12:31     ` Lukas Schroeder

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=20010609132501.C20514@erasmus.off.net \
    --to=zab@zabbo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@edeal.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