Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Mark T.B. Carroll" <mtbc@ixod.org>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Marc Boucher <marc@linuxant.com>
Subject: Re: [ALSA] hda-codec - Fix laptop models for Cxt5045
Date: Tue, 01 Jul 2008 14:36:16 +0200	[thread overview]
Message-ID: <s5hr6adeq7z.wl%tiwai@suse.de> (raw)
In-Reply-To: <87y74liyd4.fsf@ixod.org>

At Tue, 01 Jul 2008 08:26:47 -0400,
Mark T.B. Carroll wrote:
> 
> Takashi Iwai <tiwai@suse.de> writes:
> 
> > At Tue, 1 Jul 2008 09:07:30 +0200 (CEST),
> > Jaroslav Kysela wrote:
> >> 
> >> On Mon, 30 Jun 2008, Mark T.B. Carroll wrote:
> >> 
> >> > Greetings. I thought I should mention that your patch
> >> > http://kerneltrap.org/mailarchive/git-commits-head/2008/2/1/670694
> >> > broke headphone sound for me on a Toshiba Satellite P105-S6197,
> >> > sound card PCI ID 8086:27d8 with Conexant CX20549 codec. The speakers
> >> > silence when I plug the headphones in but no sound comes from them.
> >
> > Do you mean that the no sound comes from the headphone even if you
> > plug it?  And, the speaker works again after unplugging the HP?
> 
> Yes.
> 
> >> > Details are at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488063
> >> > but half of my Debian bug reports go ignored for years.
> >> > 
> >> > A sufficient workaround for me is to comment out the `default:' in the
> >> > `switch (board_config)' in the function `patch_cxt5045' in
> >> > sound/pci/hda/patch_conexant.c. Then everything works fine again.
> >
> > Does the speaker auto-muting work if you do that?
> 
> Yes.
> 
> In both cases, the speakers work fine: they mute if I plug the
> headphones in, and unmute when I unplug them.

OK, it means that your hardware does hardware-muting, thus the driver
doesn't have to mute by itself.

> The difference is that if I leave the `default:' in the code, no sound
> comes from the headphones when they are plugged in.
> 
> > Please run alsa-info.sh (with --no-upload option) for both working
> > (patched) and non-working (the original) cases, and attach generated 
> > files to compare.  This will be helpful to analyze the problem.
> 
> Okay.

Thanks.


Takashi

  reply	other threads:[~2008-07-01 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871w2ea4ek.fsf@ixod.org>
2008-07-01  7:07 ` [ALSA] hda-codec - Fix laptop models for Cxt5045 Jaroslav Kysela
2008-07-01  9:54   ` Takashi Iwai
2008-07-01 12:26     ` Mark T.B. Carroll
2008-07-01 12:36       ` Takashi Iwai [this message]
2008-07-01 12:40       ` Takashi Iwai
2008-07-01 12:48         ` Takashi Iwai
2008-07-01 13:19           ` Mark T.B. Carroll
2008-07-01 13:23             ` Takashi Iwai
2008-07-01 13:03         ` Mark T.B. Carroll

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=s5hr6adeq7z.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=marc@linuxant.com \
    --cc=mtbc@ixod.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