alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Maciel Dias Vieira <gustavo@sagui.org>
To: Predrag Ivanovic <predivan@open.telekom.rs>
Cc: alsa-devel@alsa-project.org
Subject: Re: [REGRESSION][IDT 92HD88B1] Reversed mute key LED status after update to 3.2
Date: Thu, 12 Jan 2012 08:55:23 -0200	[thread overview]
Message-ID: <1326365723.2760.1.camel@oberon.sagui.org> (raw)
In-Reply-To: <20120108013908.30a90bc1@deus.skynet.net>

Em Dom, 2012-01-08 às 01:39 +0100, Predrag Ivanovic escreveu:
> With kernel-3.2, LED on a mute button reversed its function.
> When sound is muted,it is off, when sound is unmuted, it is on.
> With 3.1.6, works as it should. 
> 
> It seems that commit
> https://github.com/torvalds/linux/commit/e2ef36c688d5844a986424c3194bd33212c968ce
> 
> (originated from "[PATCH] ALSA: hda: invert mute led polarity for HP
> laptops"
> http://mailman.alsa-project.org/pipermail/alsa-devel/2011-December/046862.html)
> 
> broke it, because when I reverted it, and rebuilt the modules, LED
> works as expected.
> 
> Link to Bugzilla issue I have opened :
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5505
> 
> Output of alsa-info.sh is attached there, and some more info.
> 
> If you need more information, I'll be happy to provide it.
> Would output of dmidecode be useful in any way?
> Please cc me, I am not subscribed to the list.

The output of dmidecode would definitely help.

Abraços,
Gustavo

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

       reply	other threads:[~2012-01-12 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120108013908.30a90bc1@deus.skynet.net>
2012-01-12 10:55 ` Gustavo Maciel Dias Vieira [this message]
2012-01-12 19:04   ` [REGRESSION][IDT 92HD88B1] Reversed mute key LED status after update to 3.2 Predrag Ivanovic
2012-01-23 19:59     ` Gustavo Maciel Dias Vieira
2012-01-24  8:38       ` Takashi Iwai

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=1326365723.2760.1.camel@oberon.sagui.org \
    --to=gustavo@sagui.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=predivan@open.telekom.rs \
    /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;
as well as URLs for NNTP newsgroup(s).