mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PARTIAL PATCH] snd-hda-intel on Medion WIM2160
Date: Thu, 20 Sep 2007 13:05:00 +0200	[thread overview]
Message-ID: <s5hir65r40z.wl%tiwai@suse.de> (raw)
In-Reply-To: <200709192026.28082.bero@arklinux.org>

At Wed, 19 Sep 2007 20:26:27 +0200,
Bernhard Rosenkraenzer wrote:
> 
> On Thursday 13 September 2007, Takashi Iwai wrote:
> > > The patch below fixes it, but unfortunately, Medion MD2 uses the same PCI
> > > (and subvendor/subdevice) ID -- so the patch quite likely breaks Medion
> > > MD2 support.
> >
> > In that case, try to reset board_config after
> > snd_hda_check_board_config() but before setup_preset().  See
> > patch_alc885() for example (appeariny in the latest ALSA tree, also in
> > mm tree).
> 
> Will do...
> 
> > Otherwise it looks OK to me.  But, what is the primary difference in
> > the setup between MD2 and WIM2160?
> 
> I don't know -- I made it work by trial and error (I don't have access to any 
> hardware specs or the likes). By some more trial and error, I could minimize 
> the patch some more - it's down to editing the init_verbs and mixers.
> In the mixers, this one seems to be the key:
> HDA_BIND_MUTE("Master Playback Switch", 0x0c, 2, HDA_INPUT)

Hmm, these should be constantly unmuted at initialization via
alc883_medion_md2_verbs[] in MD2 model, too.

Could you double-check whether MD2 model doesn't work?  If really not
works, check codec#* output whether the inputs of NID 0x0c get unmuted
or not.


Takashi

      reply	other threads:[~2007-09-20 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 12:16 Bernhard Rosenkraenzer
2007-09-13 12:47 ` [alsa-devel] " Takashi Iwai
2007-09-19 18:26   ` Bernhard Rosenkraenzer
2007-09-20 11:05     ` Takashi Iwai [this message]

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=s5hir65r40z.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bero@arklinux.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

all inboxes | Powered by JetHome®