All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerio tesei <valerio.tesei@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig
Date: Wed, 6 Apr 2011 12:49:20 +0200	[thread overview]
Message-ID: <BANLkTim1wU9RBpZ3As9uxb=YEXWVST1FVw@mail.gmail.com> (raw)
In-Reply-To: <s5htyeb9180.wl%tiwai@suse.de>

Sorry for the intrusion,

I've a P7H55D-M Pro motherboard with an hda-intel realtek card (ALC892) i
open a ticket in alsa bugtracker and Raymond says me to post here.
My motherboard had 6 pinjack behind and optical output on it, from the
specification page on asus (
http://uk.asus.com/product.aspx?P_ID=qWmZUAdNKeozTOXb&templete=2 )

Realtek ALC892 8-Channel High Definition Audio CODEC
- BD Audio Layer Content Protection
- Support Jack-dectection, Multi-streaming,Front Panel Jack-Retasking (Mic
in port)
- ASUS Noise Filter
- Optical S/PDIF out ports at back I/O

>From 2.6.38 kernel i've got a lot of problems with it, sound cracky,
microphone doesnt work or work badly, no sound after a random time of use
and some other problems.
I'm now using 2.6.39-rc1 with kernel distribuited alsa build-in with kernel,

About my bios config
[Front Panel] = AC97
[SPDIF OUT] = SPDIF

my latest alsa info is http://valeriotesei.com/alsa/alsainfo

Link to ticket (to see my discussion with Raymond)
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5331

Let me know if i could help in some way, i'm not so skilled to help with
source code, but i could be a beta tester.

Sorry if i'm off-topic.

Hope this will help you.

2011/4/6 Takashi Iwai <tiwai@suse.de>

> At Wed, 6 Apr 2011 16:29:56 +0800,
> Raymond Yau wrote:
> >
> > 2011/4/6 Takashi Iwai <tiwai@suse.de>
> >
> > > At Wed, 6 Apr 2011 15:35:16 +0800,
> > > Raymond Yau wrote:
> > > >
> > > > 2011/4/6 Takashi Iwai <tiwai@suse.de>
> > > >
> > > > > At Tue, 5 Apr 2011 22:59:29 +0800,
> > > > > Raymond Yau wrote:
> > > > > >
> > > > > > Fix alc662_dac_nid and change "6stack-dig" to "5stack-dig"
> > > > > >
> > > > > > alc662 series only have 3 stereo DAC , so it can only support
> > > 5stack-dig
> > > > > > instead of 6stack-dig
> > > > >
> > > > > Applied now.  Thanks.
> > > > >
> > > > >
> > > > > Takashi
> > > > >
> > > >
> > > > The other problem is this patch
> > > >
> > > >    { .id = 0x10ec0892, .name = "ALC892", .patch = patch_alc662 },
> > > >
> > > >
> > >
> http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=274693f37090ada2cadd09944ab883f05ea6ebe6
> > > >
> > > > ALC892 provides ten DAC channels that simultaneously support 7.1
> channel
> > > > sound playback, plus 2 channels of independent stereo sound output
> > > (multiple
> > > > streaming) through the front panel stereo outputs.
> > > >
> > > > It seem  that there is no specific code to distinguish a 10 channels
> > > alc892
> > > > from those 6 channels alc6xx
> > >
> > > Yeah, but there is no quirks specific to alc892.
> > >
> > > Remember that the final goal is to remove all model-quirks from the
> > > driver.
> > >
> > >
> > > Takashi
> > >
> >
> > My patch reduce the size of alc662_dac_nid may be wrong if the driver
> intend
> > to use  alc662_auto_fill_dac_nids()  to handle 6, 8 , 10 channels
>
> Don't worry, alc662_dac_nids is used only for the fixed quirks.
> The auto-parser doesn't use these fixed defined pin arrays.
>
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

  reply	other threads:[~2011-04-06 10:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 14:59 [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig Raymond Yau
2011-04-06  6:19 ` Takashi Iwai
2011-04-06  7:35   ` Raymond Yau
2011-04-06  7:41     ` Takashi Iwai
2011-04-06  8:29       ` Raymond Yau
2011-04-06  9:29         ` Takashi Iwai
2011-04-06 10:49           ` Valerio tesei [this message]
2011-04-07  1:53             ` Raymond Yau
2011-04-07 12:59               ` Valerio tesei
2011-04-07 13:13                 ` Raymond Yau
2011-04-07 13:55                   ` Valerio tesei
2011-04-07 19:44                   ` Valerio Tesei
2011-04-08  0:48                     ` Raymond Yau
2011-04-06 12:59           ` Raymond Yau
2011-04-06 13:07             ` Takashi Iwai
2011-04-06 13:19               ` Takashi Iwai
2011-04-08  2:06           ` Raymond Yau
2011-04-08  8:38             ` Valerio tesei
2011-04-08  9:28               ` OT: applying patches (was: [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig) Paul Menzel
2011-04-08  9:47                 ` Valerio tesei
2011-04-08 10:27                   ` snd-hda-intel and parameter `patch` (was: OT: applying patches) Paul Menzel
2011-04-08 14:44                     ` snd-hda-intel and parameter `patch` David Henningsson
2011-04-10  1:21               ` [PATCH ALSA HDA 1/1] Fix alc662_dac_nid and change 6stack-dig to 5stack-dig Raymond Yau
2011-04-11  8:21                 ` Valerio tesei
2011-04-11 19:28                   ` Valerio Tesei
2011-04-13  8:52                     ` Raymond Yau
2011-04-13 11:08                       ` Valerio tesei
2011-04-13 19:12                         ` Valerio Tesei
2011-04-14 11:11                         ` Raymond Yau
2011-04-18 19:53                           ` Valerio Tesei

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='BANLkTim1wU9RBpZ3As9uxb=YEXWVST1FVw@mail.gmail.com' \
    --to=valerio.tesei@gmail.com \
    --cc=alsa-devel@alsa-project.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 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.