All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Vroon <tony@linx.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [ALC262_FUJITSU patch_realtek.c] Use jack sense for both	headphone outputs
Date: Mon, 19 May 2008 11:31:09 +0100	[thread overview]
Message-ID: <1211193069.3899.4.camel@localhost> (raw)
In-Reply-To: <s5hod72d22y.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 707 bytes --]

On Mon, 2008-05-19 at 12:23 +0200, Takashi Iwai wrote:
> Any reason to remove this?
> Otherwise the internal speaker won't react together with the Master volume.

It seemed to only take the internal headphone output into account, not
the dock headphone output. But if it's just to link the two volumes
together I'll add it back. It will fix the compile warning as well.
Its purpose was unclear to me.

Will the existing mechanism cope if 0x14 (internal HP output) is muted
and 0x1B (dock HP output) is not?

> Maybe a cleaner fix is to remove the bind_sw and bind_vol hacks and
> use vmaster instead.

Is there example code I can look at please?

> thanks,
> Takashi

Regards,
Tony V.

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  reply	other threads:[~2008-05-19 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19  0:00 [ALC262_FUJITSU patch_realtek.c] Use jack sense for both headphone outputs Tony Vroon
2008-05-19 10:23 ` Takashi Iwai
2008-05-19 10:31   ` Tony Vroon [this message]
2008-05-19 10:37     ` Takashi Iwai
2008-05-19 10:56       ` Takashi Iwai
2008-05-19 11:33         ` Tony Vroon

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=1211193069.3899.4.camel@localhost \
    --to=tony@linx.net \
    --cc=alsa-devel@alsa-project.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.