mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Hui Wang <hui.wang@canonical.com>,
	Raymond Yau <superquad.vortex2@gmail.com>,
	alex.hung@canonical.com,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Hui Wang <jason77.wang@gmail.com>,
	tiwai@suse.de,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	david.henningsson@canonical.com
Subject: Re: [alsa-devel] [V2 PATCH] ALSA: hda - Enable mute/mic-mute LEDs for more Thinkpads with Conexant codec
Date: Sat, 27 Jun 2015 12:50:44 -0300	[thread overview]
Message-ID: <20150627155044.GA3054@khazad-dum.debian.net> (raw)
In-Reply-To: <558E3BDE.5070708@web.de>

On Sat, 27 Jun 2015, Jan Kiszka wrote:
> > Please explain _in detail_ what you mean with "changing a power button to a
> > reset button by acessing the SSMS ACPI method in a X121e".
> > 
> > Are we trigering a bug somewhere that crashes the x121e and causes it to
> > reboot?
> 
> Well, there aren't much details to describe in this case: When this
> patch is applied and I press the power button, the device performs a
> hard reset. It doesn't reveal if the kernel crashes catastrophically,
> causing a triple fault or so, or if the firmware decides to reset the
> platform. Reverting the patch or preventing its effect via a quirk
> filter like I posted [1] makes the issue go away.

Ok, so we crashing the firmware, and on a box that is not likely to get
further updates.  Well, this is a pretty clear case: blacklist.

Since calling SSMS in the X121e is unsafe, it needs to be blacklisted in
thinkpad-acpi.  I will need dmidecode output for that (please XXX-out UUIDs
and serial numbers in the dmidecode output before you send it to me, but do
keep model numbers intact).

We can also have a blacklist in ALSA to avoid the whole symbol_request() for
something that will have to fail, of course.  I leave that for the ALSA
maintainers to decide.

That said, you blacklisted in ALSA by full codec->subsystem_id.  Which
thinkpads have the 0x17aa21ec subsystem ID on the codec?  Just the x121e?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2015-06-27 15:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1385534846-20829-1-git-send-email-hui.wang@canonical.com>
2014-06-29 11:33 ` Jan Kiszka
2014-06-30  2:04   ` Hui Wang
2014-06-30  6:45     ` Jan Kiszka
2014-07-01  2:15       ` Hui Wang
2014-07-01  7:38         ` Jan Kiszka
2014-07-01  9:26           ` Hui Wang
2014-07-03  7:04             ` Jan Kiszka
2014-07-03  8:59               ` Hui Wang
2014-07-03  9:05                 ` Jan Kiszka
2014-07-03  9:24                   ` Hui Wang
2015-05-23  8:49                     ` Jan Kiszka
     [not found]                       ` <CAN8cciZYZ4setSj7dgPqQUVrBrr98tSvofLrD_0zvyQqkWfd2Q@mail.gmail.com>
2015-05-23 16:22                         ` [alsa-devel] " Jan Kiszka
2015-06-24  5:37                           ` Jan Kiszka
2015-06-24  8:46                             ` Hui Wang
2015-06-25 11:02                               ` Jan Kiszka
2015-06-26  2:22                                 ` Hui Wang
2015-06-26  4:06                                   ` Jan Kiszka
2015-06-26 22:49                                   ` Henrique de Moraes Holschuh
2015-06-27  5:59                                     ` Jan Kiszka
2015-06-27 15:50                                       ` Henrique de Moraes Holschuh [this message]
2015-06-29  9:06                                         ` Takashi Iwai
     [not found]                       ` <CAN8ccibyupfc_1xa3q7FfH_T7iL_1_S8cRJ1ksHG-BBJ1SJyfw@mail.gmail.com>
2015-06-29  0:49                         ` Hui Wang
2015-07-01  9:51                           ` Hui Wang

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=20150627155044.GA3054@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=alex.hung@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=hui.wang@canonical.com \
    --cc=jan.kiszka@web.de \
    --cc=jason77.wang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=superquad.vortex2@gmail.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®