Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing	Beep
Date: Thu, 29 Jul 2010 10:52:36 +0200	[thread overview]
Message-ID: <s5h39v2acvf.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100729084138.GA15456@darkside.kls.lan>

At Thu, 29 Jul 2010 10:41:38 +0200,
Mario 'BitKoenig' Holbe wrote:
> 
> On Thu, Jul 29, 2010 at 10:26:22AM +0200, Takashi Iwai wrote:
> > FYI, you can change SSID by writing /sys/class/sound/hwC*D*/subsystem_id
> > file.  Then reconfigure the codec via triggering
> > /sys/class/sound/hwC*D*/reconfig.
> 
> Great, that's what I meant with "Or am I somehow able to tweak it? Is
> there a module parameter to set this SSID bit?" :)
> 
> $ for i in /sys/class/sound/hwC*D*/subsystem_id; do echo "$i: $(cat $i)"; done   
> /sys/class/sound/hwC0D0/subsystem_id: 0x1043829f
> /sys/class/sound/hwC0D1/subsystem_id: 0xffffffff
> 
> So, obviously the first check in
> 	if (ass != codec->bus->pci->subsystem_device && (ass & 1))
> is false. How can I tweak the subsystem_id least-invasive not to match
> codec->bus->pci->subsystem_device (which should be 0x829f then) anymore?

Usually the codec SSID isn't checked in other places, so passing a
bogus value should be OK.  Pass a value like 2:

	# echo -n 2 > /sys/class/sound/hwC0D0/subsystem_id
then
	# echo -n 1 > /sys/class/sound/hwC0D0/reconfig

The latter needs that the all sound device files are closed beforehand.


Takashi

  reply	other threads:[~2010-07-29  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 14:49 Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing Beep Mario 'BitKoenig' Holbe
2010-07-28 15:35 ` Takashi Iwai
2010-07-28 16:03   ` [alsa-devel] " Takashi Iwai
2010-07-28 21:27     ` Mario 'BitKoenig' Holbe
2010-07-29  5:44       ` Takashi Iwai
2010-07-29  8:09         ` [alsa-devel] " Mario 'BitKoenig' Holbe
2010-07-29  8:26           ` Takashi Iwai
2010-07-29  8:41             ` Mario 'BitKoenig' Holbe
2010-07-29  8:52               ` Takashi Iwai [this message]
2010-07-29  9:15                 ` Mario 'BitKoenig' Holbe
2010-07-29  9:42                   ` Takashi Iwai
2010-07-29 13:25                     ` Mario 'BitKoenig' Holbe
2010-07-29 13:33                       ` 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=s5h39v2acvf.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Mario.Holbe@TU-Ilmenau.DE \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.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