From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000667]: How to integrate turning on and off LED:s on laptops
Date: Mon, 31 Jan 2005 19:04:38 +0100 [thread overview]
Message-ID: <bd533cce5968083d93e43b98f38728e1@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=667>
======================================================================
Reported By: linus
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 667
Category: PCI - intel8x0
Reproducibility: always
Severity: feature
Priority: normal
Status: closed
Distribution: Fedora Core 3
Kernel Version: 2.6.9
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 11-23-2004 15:27 CET
Last Modified: 01-31-2005 19:04 CET
======================================================================
Summary: How to integrate turning on and off LED:s on laptops
Description:
This machine, an HP Compaq NC6000 (also on other models
such as NC8000) has a mute LED that
turns on and off when mute is activated/deactivated.
It is accomplished by way of the "External Amplifier"
setting - this has been wired to a LED instead of an
amplifier, so the "mute" function should (theoretically)
activate/deactivate the "External Amplifier" when muting
is selected for the device. The chip used is AD1981B.
This script shows how it is done:
if ( amixer sget "External Amplifier"|grep off > /dev/null )
then
# Toggles the LED, no actual volume change
amixer set "External Amplifier" unmute > /dev/null
# Toggles the audio level
amixer set "Master" unmute > /dev/null
else
amixer set "External Amplifier" mute > /dev/null
amixer set "Master" mute > /dev/null
fi
The question of how this is to be implemented remains. Is
this an issue for ALSA or shall it be handled on a higher,
user-space level? I also have a bug open in GNOME for the
same thing, I need to decide how to finally resolve this
and need input from the ALSA team on the best solution.
(See http://bugzilla.gnome.org/show_bug.cgi?id=157748)
======================================================================
----------------------------------------------------------------------
tiwai - 12-23-04 16:08
----------------------------------------------------------------------
OK, here is a test patch. Could you try it wheter it works?
----------------------------------------------------------------------
tiwai - 12-27-04 15:28
----------------------------------------------------------------------
I commited the newer patch to CVS.
Issue History
Date Modified Username Field Change
======================================================================
11-23-04 15:27 linus New Issue
11-23-04 15:27 linus Distribution => Fedora Core 3
11-23-04 15:27 linus Kernel Version => 2.6.9
11-23-04 15:41 tiwai Note Added: 0002516
11-23-04 21:28 linus Note Added: 0002528
11-24-04 12:22 tiwai Note Added: 0002549
11-24-04 13:00 IceRAM Note Added: 0002555
11-24-04 13:07 tiwai Note Added: 0002558
11-24-04 14:27 linus Note Added: 0002562
11-24-04 15:07 linus Note Added: 0002567
11-24-04 18:47 Clemens LadischFile Added: muteled.c
11-24-04 18:47 Clemens LadischNote Added: 0002580
12-02-04 19:36 tiwai Note Added: 0002695
12-23-04 16:08 tiwai Note Added: 0002923
12-23-04 16:09 tiwai File Added: mute-led.diff
12-27-04 15:28 tiwai Status new => resolved
12-27-04 15:28 tiwai Resolution open => fixed
12-27-04 15:28 tiwai Assigned To => tiwai
12-27-04 15:28 tiwai Note Added: 0002962
12-27-04 15:28 tiwai Assigned To tiwai =>
01-03-05 12:03 piesis Issue Monitored: piesis
01-03-05 12:03 piesis Issue End Monitor: piesis
01-31-05 19:04 tiwai Status resolved => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-01-31 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 18:04 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-27 14:28 [ALSA - driver 0000667]: How to integrate turning on and off LED:s on laptops bugtrack
2004-12-23 15:08 bugtrack
2004-12-02 18:36 bugtrack
2004-11-24 17:47 bugtrack
2004-11-24 14:07 bugtrack
2004-11-24 13:27 bugtrack
2004-11-24 12:07 bugtrack
2004-11-24 12:00 bugtrack
2004-11-24 11:22 bugtrack
2004-11-23 20:28 bugtrack
2004-11-23 14:41 bugtrack
2004-11-23 14:27 bugtrack
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=bd533cce5968083d93e43b98f38728e1@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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