Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ibm-acpi-devel@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: Re: Adding a alsa mixer interface to ibm-acpi
Date: Mon, 26 Feb 2007 16:31:40 +0100	[thread overview]
Message-ID: <s5h649pue8z.wl%tiwai@suse.de> (raw)
In-Reply-To: <20070225012017.GA19039@khazad-dum.debian.net>

At Sat, 24 Feb 2007 23:20:17 -0200,
Henrique de Moraes Holschuh wrote:
> 
> Hello,
> 
> I am the current maintainer of the ibm-acpi driver for the Linux kernel.
> Those of you that own a ThinkPad notebook probably know what I am talking
> about.
> 
> A ThinkPad notebook has a hardware mixer for volume control (two functions:
> volume and mute).  The user can interact with this volume control using
> three buttons (up/down/mute), and it is completely implemented in firmware.
> 
> ibm-acpi currently exports those controls through a procfs interface, but I
> am trying to get rid of it, and instead of just porting the interface to
> sysfs attributes, I tried to write a proof-of-concept alsa mixer -- if it is
> a mixer, it should be exported as one, not as some driver-specific sysfs
> attributes, IMHO :-)
> 
> It worked almost perfectly, and it was easy to write.  Many thanks to
> Takashi Iwai for his excellent docs at
> http://www.alsa-project.org/~iwai/writing-an-alsa-driver/index.html.
> 
> The only issue was in userspace, apparently alsamixer ignores VOLATILE
> controls and doesn't poll them for updates.  I wonder how widespread such
> misbehaviour is?  I may have to write an in-driver polling thread so that I
> can send notifications, if it is too widespread.

That's exactly the role of VOLATILE flag.  It's for controls with
frequently changing elements (e.g. VU-meters) and thus not suitable
for poll/select by a mixer app.  I think the case of volume buttons is
OK to use normal controls without VOLATILE flag.

> Anyway, the driver is *not* a stand-alone module, but rather just a small
> part of ibm-acpi.  I suppose I could break it into two modules so that the
> alsa mixer has its own module, but either it would *have* to depend on
> ibm-acpi, or it would have to duplicate a lot of thinkpad specific stuff.
> 
> How do you guys feel about an in-tree module that has alsa stuff in it, but
> is not part of the alsa tree?  Would that be a problem?

I'm basically for including it in ALSA driver (suppose intel8x0?) as
long as it's directly related with the sound.  If you have a working
patch, I'm willing to review and discuss more.

Anyway, the reply will be delayed since I'll be in vacation from now
for a week or so.


Thanks,

Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-02-26 15:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25  1:20 Adding a alsa mixer interface to ibm-acpi Henrique de Moraes Holschuh
2007-02-26 15:31 ` Takashi Iwai [this message]
     [not found]   ` <s5h649pue8z.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2007-02-26 16:28     ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-02-26 16:36       ` [ibm-acpi-devel] " Takashi Iwai
2007-02-26 17:41         ` Henrique de Moraes Holschuh
     [not found]           ` <20070226174145.GF2909-ZGHd14iZgfaRjzvQDGKj+xxZW9W5cXbT@public.gmane.org>
2007-02-27  1:50             ` [Alsa-devel] " Theodore Tso
2007-02-27  2:14               ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2007-03-07 21:59                 ` Takashi Iwai
     [not found]                   ` <s5hd53kaf5r.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2007-03-07 23:02                     ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-03-07 23:12                     ` Shem Multinymous
2007-03-07 23:23                       ` [ibm-acpi-devel] " Tobin Davis
2007-03-07 23:41                         ` Shem Multinymous
2007-03-07 23:42                       ` Henrique de Moraes Holschuh
2007-03-07 23:55                         ` Tobin Davis
     [not found]                           ` <1173311709.4531.30.camel-lPoCD4h/KdUU2NE2KMwFWnnhMCiq3JZZ@public.gmane.org>
2007-03-08  0:38                             ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-03-09 16:29                               ` [ibm-acpi-devel] " Takashi Iwai
     [not found]                                 ` <s5htzwugz22.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2007-03-10  3:50                                   ` [Alsa-devel] " Henrique de Moraes Holschuh
2007-03-12 12:03                                     ` [ibm-acpi-devel] " Takashi Iwai
2007-03-12 21:00                                       ` Henrique de Moraes Holschuh
2007-03-12 22:00                                         ` Alex Deucher

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=s5h649pue8z.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    /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