All of lore.kernel.org
 help / color / mirror / Atom feed
From: Massimo Del Fedele <max@veneto.com>
To: alsa-devel@alsa-project.org
Subject: Re: Fix for Asus G75 notebook subwoofer
Date: Thu, 01 Nov 2012 12:15:14 +0100	[thread overview]
Message-ID: <k6tlk1$2vr$1@ger.gmane.org> (raw)
In-Reply-To: <CAN8cciZEwLxxiMp69k8yyAzSnqRNQ6m2=7q373x91D_pMy=h-w@mail.gmail.com>

Il 01/11/2012 09:11, Raymond Yau ha scritto:

>
> can you post the output of alsa-info.sh ?

Where can I find the script ? I've not it on my machine
>
> http://git.kernel.org/?p=linux/kernel/git/tiwai/hda-emu.git;a=blob_plain;f=codecs/vt1802-asus-u30s;hb=HEAD
>
>     9.337454] ALSA hda_codec.c:4877 autoconfig: line_outs=1
> (0x24/0x0/0x0/0x0/0x0) type:speaker
> [    9.337458] ALSA hda_codec.c:4881    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [    9.337460] ALSA hda_codec.c:4885    hp_outs=1 (0x25/0x0/0x0/0x0/0x0)
> [    9.337462] ALSA hda_codec.c:4886    mono: mono_out=0x0
> [    9.337464] ALSA hda_codec.c:4889    dig-out=0x2d/0x0
> [    9.337465] ALSA hda_codec.c:4890    inputs:
> [    9.337467] ALSA hda_codec.c:4894  Internal Mic=0x29
> [    9.337469] ALSA hda_codec.c:4894  Mic=0x2b
>
> it is the auto parser put the speaker to autocfg->lineout

Yep, if you look at above, this one was exactly the output before my 2 patches; the only difference
was line 24, marked as type=SPEAKER; no trace of mono pin 0x33.
I guess the 0x33 is skipped because the parser don't find a path from it, as it have a connection to
widget 0x3e with is out of range (widgets are reported to be from 0x08 to 0x0c).
We could also patch the returned widget number to be 2 widgets more, even id 0x3d is NOT there.
>
> vt1802 also has connection to 0x3e in node 0x24 and 0x33

The 0x3e is a stereo to mono mixer, connecting to 0x1c.
As above, VT1802p reports to have widgets up to 0x3c.
>
> you cannot change the pin default from speaker of 0x24 to lineout if node
> 0x33 only support mono
>
> should the auto parser put it into autocfg->mono_out?
>

maybe.... I didn't try that one.
With both patches the stuffs appears like a 4 channel one; the correct would be 2+1, but
I didn't manage to get it right.

Anyways, I did all this without datasheet... I've tried to get it from VIA, with usual (null) results.
Maybe the 2 exceeding widgets are reported there, I don't know.

Resuming, without patches, the auto_parser report for asus :

0x24 Line out, type speaker
0x25 Hp out
0x33 is missing

Forcing the connection from 0x33 to 0x1c (skipping so 0x3e) the pin 0x33 don't appear
because bios marks it at none-connection.
Forcing the connection to JACK, it puts as a mono speaker, so no sound from it either.
Forcing to be a line out, sound only from it because then 0x24 takes the speaker place (marked as speaker in bios).
Forcing both 0x24 and 0x33 to be line out gives 4 channel sound (with 2 rear channels output to 0x33 mono).

No idea on how to get the 2+1 behaviour, but at least now it sounds.

Max

  reply	other threads:[~2012-11-01 11:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 16:49 Fix for Asus G75 notebook subwoofer Massimo Del Fedele
2012-11-01  8:11 ` Raymond Yau
2012-11-01 11:15   ` Massimo Del Fedele [this message]
2012-11-02  1:44     ` Raymond Yau
2012-11-02 14:57       ` Massimo Del Fedele
2012-11-03  0:37         ` Raymond Yau
2012-11-03  9:04           ` Massimo Del Fedele
2012-11-04  6:27         ` Raymond Yau
2012-11-04  9:31           ` Massimo Del Fedele
2012-11-07  0:50             ` Raymond Yau
2012-11-06  8:36 ` Takashi Iwai
2012-11-06  8:57   ` Massimo Del Fedele
2012-11-06  9:06     ` Takashi Iwai
2012-11-06 14:18       ` Massimo Del Fedele
2012-11-06 14:24         ` Takashi Iwai
2012-11-06 17:23           ` Massimo Del Fedele
2012-11-07  8:56             ` Takashi Iwai
2012-11-07  8:56             ` Takashi Iwai
2012-11-07 13:37               ` Massimo Del Fedele
2012-11-07 13:45                 ` Takashi Iwai
2012-11-07 15:51                   ` Massimo Del Fedele
2012-11-07 15:54                     ` Takashi Iwai
2012-11-07 17:02                       ` Massimo Del Fedele
2012-11-07 17:13                         ` 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='k6tlk1$2vr$1@ger.gmane.org' \
    --to=max@veneto.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.