alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Patrick Shirkey" <pshirkey@boosthardware.com>
To: alsa-devel@alsa-project.org
Subject: Re: Testing/Debugging alc668 with ASUS N750JK
Date: Thu, 31 Jul 2014 17:32:32 +1000 (EST)	[thread overview]
Message-ID: <55293.86.107.254.57.1406791952.squirrel@boosthardware.com> (raw)
In-Reply-To: <CAN8ccia3mi9G2oyaYyvJx14xu6F8dLhNZ6r0dpraO1F8qeLjBg@mail.gmail.com>


On Thu, July 31, 2014 1:27 pm, Raymond Yau wrote:

>
> You can use hda-verb GET_PIN_SENSE to test all the pin complex nodes which
> pincap support DETECT
>

I have tried a few attempts but it's pretty confusing.

These ones don't do anything:

# hda-verb /dev/snd/hwC1D0  GET_PIN_SENSE
# hda-verb /dev/snd/hwC1D0  0x0 GET_PIN_SENSE


I don't know what to make of this output:

# hda-verb /dev/snd/hwC1D0  0x0 GET_PIN_SENSE PIN_CAP
nid = 0x0, verb = 0xf09, param = 0xc
value = 0x0
# hda-verb /dev/snd/hwC0D0  0x0 GET_PIN_SENSE PIN_CAP
nid = 0x0, verb = 0xf09, param = 0xc
value = 0x0
# hda-verb /dev/snd/hwC0D0  0x16 GET_PIN_SENSE PIN_CAP
nid = 0x16, verb = 0xf09, param = 0xc
value = 0xffffffff
# hda-verb /dev/snd/hwC0D0  0x19 GET_PIN_SENSE PIN_CAP
nid = 0x19, verb = 0xf09, param = 0xc
value = 0xffffffff
# hda-verb /dev/snd/hwC0D0  0x1a GET_PIN_SENSE PIN_CAP
nid = 0x1a, verb = 0xf09, param = 0xc
value = 0xffffffff
# hda-verb /dev/snd/hwC0D0  0x1b GET_PIN_SENSE PIN_CAP
nid = 0x1b, verb = 0xf09, param = 0xc
value = 0xffffffff



>> > Do surround 2.1 works ?
>> >
>>
>> It says it is working but I do not get sound out of the sub woofer.  I
>> can
>> hear static(whitenoise) through the front speakers (with pulseaudio
>> test)
>> if  I set pins 0x19 and 0x1a to Line Out (Center/LFE) and Internal
>> (Center/LFE) or vice versa with hdajackretask.
>>
>
> http://git.alsa-project.org/?p=alsa-tools.git;a=blob;f=hdajackretask/README;hb=HEAD
>
> Did you use apply button(dyanmic reconfiguartion) or installment boot
> override (early patching) ?
>

I have tried both options.

After rebooting with the apply option set I don't hear any static or audio
with the PA test app.

>>
>> I do not see any controls for the bass volume in alsamixer
>>
>>
>
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=f37bc7a88d374448a1f4bba9267d308606d78bf2
>

I have checked alsamixer again after the last round of tinkering with
hdajackretask and" Speaker CLFE" is now showing up but it does not have
volume control just mute on/off.

I see the following new controls

Speaker CFLE (mute only)
Speaker Front (mute + vol)
Speaker Side (mute only)
Speaker Surround (mute + vol)


>> >>
>> >> >> - I have found a couple of kernel bug reports  for other ASUS
>> models
>> >> >> with
>> >> >> this chipset but they are both marked resolved. Should I open a
>> new
>> >> >> ticket
>> >> >> ?
>> >> >>
>> >> >> https://bugzilla.kernel.org/show_bug.cgi?id=65091
>> >> >> https://bugzilla.kernel.org/show_bug.cgi?id=66271
>> >> >>
>> >> >> - I can hear static through the front speakers (with pulseaudio
> test)
>> >> >> if
>> >> >> I set pins 0x19 and 0x1a to Line Out (Center/LFE) and Internal
>> >> >> (Center/LFE) or vice versa with hdajackretask.
>> >> >>
>
>> > For multi channel, the sequence number is ascending and the driver
> expect
>> > they have same type i.e, all speakers or all line out jacks
>> >
>
> Pin Default 0x90170110: [Fixed] Speaker at Int N/A
>     Conn = Analog, Color = Unknown
>     DefAssociation = 0x1, Sequence = 0x0
>     Misc = NO_PRESENCE
>
> The rear speaker need  same default association but  sequence number
> higher than that of the front speaker
>
> The external subwoofer may use [jack] speaker with same default
> association and higher sequence number if it can be detected
>
> The driver won't use all of them for multi channel if you retasked it as
> line out
>

I have tried several combinations with hdajackretask

I am not able to get audio out of the physical rear speakers or sonic
master output.

I can get audio to play back in the front l/c/r speakers with varying
combinations.

ex.

7.1 side l/r plays through front l/r or front c
4.0 rear r/l plays through front l/r
2.1 l/r plays through front l/r
2.1 subwoofer plays white noise through front c

Most of the time it is only front left/right that make any sound.
Sometimes there is no sound on one audio profile but it works on a couple
of channels on another profile.

Any time that the Center LFE works it produces white noise.

I have tried with both options: apply and patch/reboot

I can keep playing around with the settings until I eventually stumble on
a combination that works but it seems like this process should be
scriptable. Given that I will probably spend hours of my time on the test
process and I have already spent 4 separate sessions on testing it seems
like it would be better value for my time and others going forward to
write a test script.

So what do I need to do to write a script that will test all the
combinations and play audio through them? Or am I missing something that
someone else has already written for this purpose?

Currently I am using this process:

1: hdajackretask - modify params
2: pulseaudio -k
3: hdajackretask : apply settings
4: pulseaudio -D
5: open PA audio config
6: select audio output option and press test speakers button
7: manually press every button

Rinse and repeat.

Surely there is a more humane method for testing the variations ;-)




--
Patrick Shirkey
Boost Hardware Ltd

  reply	other threads:[~2014-07-31  7:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  4:03 [PATCH v3 0/2] Add Freescale ASRC driver Nicolin Chen
2014-07-25  4:03 ` [PATCH v3 1/2] ARM: imx: Add the secondary request into the structure for imx-sdma Nicolin Chen
     [not found] ` <cover.1406259578.git.nicoleotsuka-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-25  4:03   ` [PATCH v3 2/2] ASoC: fsl_asrc: Add ASRC ASoC CPU DAI and platform drivers Nicolin Chen
2014-07-25  4:24     ` Varka Bhadram
2014-07-25  5:30       ` Nicolin Chen
2014-07-25  5:40       ` Testing/Debugging alc668 with ASUS N750JK Patrick Shirkey
2014-07-26  4:01         ` Raymond Yau
2014-07-26  8:18           ` Patrick Shirkey
2014-07-29  3:58             ` Raymond Yau
2014-07-29  4:46               ` Patrick Shirkey
2014-07-31  3:27                 ` Raymond Yau
2014-07-31  7:32                   ` Patrick Shirkey [this message]
2014-07-31 13:38                     ` Raymond Yau
2014-07-31 18:25                       ` Patrick Shirkey
2014-08-01  7:19                         ` Raymond Yau
2014-08-01  9:07                           ` Patrick Shirkey
2014-08-01 10:04                             ` Raymond Yau
2014-08-01 10:33                               ` Patrick Shirkey
     [not found]       ` <53D1DC0B.1000905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-25  5:54         ` [PATCH v3 2/2] ASoC: fsl_asrc: Add ASRC ASoC CPU DAI and platform drivers Nicolin Chen
2014-07-25  6:17           ` Varka Bhadram
2014-07-25  6:09             ` Nicolin Chen
     [not found]     ` <f4ff79269a1680f9ce128e0e98fea926d3a41834.1406259578.git.nicoleotsuka-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-29  9:46       ` Mark Rutland
2014-07-29 10:13         ` Nicolin Chen

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=55293.86.107.254.57.1406791952.squirrel@boosthardware.com \
    --to=pshirkey@boosthardware.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 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).