alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Ken Prox <knprox@mi.rr.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Ken Prox <kprox@users.sourceforge.net>
Subject: Re: [PATCH - hda intel conextant 1/1] Fixed microphone mixer for HP Compaq Presario F700 Added conextant patch for	Hewlett-Packard Company Device Subsystem id - 103c:30ea
Date: Mon, 25 Jan 2010 19:19:31 -0500	[thread overview]
Message-ID: <4B5E3513.6050907@mi.rr.com> (raw)
In-Reply-To: <s5h4ombbxok.wl%tiwai@suse.de>

On 01/24/2010 05:32 AM, Takashi Iwai wrote:
> At Tue, 12 Jan 2010 10:07:02 +0100,
> I wrote:
>    
>> At Fri, 8 Jan 2010 09:09:54 +0100 (CET),
>> Jaroslav Kysela wrote:
>>      
>>> On Sun, 3 Jan 2010, knprox@mi.rr.com wrote:
>>>
>>>        
>>>> From: Ken Prox<kprox@users.sourceforge.net>
>>>>
>>>>
>>>> Signed-off-by: Ken Prox<kprox@users.sourceforge.net>
>>>>          
>>> I've applied your patch to my "devel" git tree with space/tab
>>> replacements. Please, use same coding style matching other ALSA code and
>>> run "scripts/checkpatch.pl" on your patch before posting. Thanks.
>>>        
>> I pulled your branches now to sound git tree.
>>      
> And, now I'm checking the code and your change again while I'm working
> on fixing / clean-up of cxt5051 code.  I don't understand why your patch
> works.  Does it really work as is?
>
> For example, the pin 0x17 has no multiple connections.  So, changing
> the amp for the input #1 doesn't make sense at all.  If it supports only
> the pin 0x1d, then the init verbs have to be different.
>
> Doesn't another model, e.g. model=hp-dv6736, work as is?
>    

> thanks,
>
> Takashi
>    

Hello Takashi,

Yes, using model=hp-dv6736 works for device 103c:30ea, but the mixer 
control does not control the microphone.  However, with the patch I 
supplied, the microphone mixer control does work.

Yes, the patch for the 103c:30ea does work as is.  If there is a change 
to the init verbs that you would like me to try, I would be more than 
happy to help.

-- 
"So often do the spirits of great events stride on before the events. And in today already walks tomorrow." - Coleridge

Ken

pgp     hkp://wwwkeys.eu.pgp.net
Skype   callto://ken.prox

  parent reply	other threads:[~2010-01-26  0:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04  0:40 [PATCH - hda intel conextant 1/1] Fixed microphone mixer for HP Compaq Presario F700 Added conextant patch for Hewlett-Packard Company Device Subsystem id - 103c:30ea knprox
2010-01-08  8:09 ` Jaroslav Kysela
2010-01-12  9:07   ` Takashi Iwai
2010-01-24 10:32     ` Takashi Iwai
2010-01-24 13:59       ` Jacopo De Simoi
2010-01-26  0:19       ` Ken Prox [this message]
2010-01-26  6:32         ` Takashi Iwai
2010-01-26 10:19           ` Jacopo De Simoi
2010-01-26 13:14             ` Takashi Iwai
2010-01-26 16:46               ` Jacopo De Simoi
2010-01-26 23:38           ` Ken Prox
2010-01-28 16:39             ` 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=4B5E3513.6050907@mi.rr.com \
    --to=knprox@mi.rr.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kprox@users.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).