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: Fri, 1 Aug 2014 19:07:08 +1000 (EST)	[thread overview]
Message-ID: <61402.86.107.254.57.1406884028.squirrel@boosthardware.com> (raw)
In-Reply-To: <CAN8cciYrj25NfmjD86ndzJd5r=D0bMNHE55JuEKichznAkAUHA@mail.gmail.com>


On Fri, August 1, 2014 5:19 pm, Raymond Yau wrote:
>

alsa-info:

retask and apply
http://boosthardware.com/alsa-info1.txt

store and reboot
http://boosthardware.com/alsa-info2.txt



>
> Do you mean the plugging of subwoofer cannot be detected
>
> hda-jack-sense-test -c 1 -a
>

prior to latest changes with hdajackretask:

# python alsa-jack-sense-test.py -c 1 -a
Pin 0x12 (Internal Mic): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black HP Out): present = No
Pin 0x16 (Not connected): present = No
Pin 0x18 (Black Mic): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Black SPDIF Out): present = No
Pin 0x1f (Not connected): present = No

headset connected:

# python alsa-jack-sense-test.py -c 1 -a
Pin 0x12 (Internal Mic): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black HP Out): present = Yes
Pin 0x16 (Not connected): present = No
Pin 0x18 (Black Mic): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Black SPDIF Out): present = No
Pin 0x1f (Not connected): present = No

after latest reboot (alsa-info2.txt):

# python alsa-jack-sense-test.py -c 1 -a
Pin 0x12 (Internal Mic): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black HP Out): present = No
Pin 0x16 (Not connected): present = No
Pin 0x18 (Black Mic): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Black SPDIF Out): present = No
Pin 0x1f (Not connected): present = No

headset connected:

# python alsa-jack-sense-test.py -c 1 -a
Pin 0x12 (Internal Mic): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black HP Out): present = Yes
Pin 0x16 (Not connected): present = No
Pin 0x18 (Black Mic): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Black SPDIF Out): present = No
Pin 0x1f (Not connected): present = No



>
> The graph don't contain enough into for debugg
>
> Post output of alsa-info.sh after retasked
>
> Seem headphone is more important than multichannel speaker when evaluating
> the badness of config
>
> You may need to configure alsa driver --with-debug=verbose to produce more
> information in system log about how it evaluate the badness
>

Easier said than done.  I have to build a custom kernel in order to get
custom alsa-drivers to build on this machine so at the moment I am stuck
with whatever I got in 3.14.1.  From the list above can you make a
recommendation for the best options to test?

According to hdajackretask the pins I can retask for output are the
following:

Pin 0x14 (Internal Speaker): present = No
Pin 0x15 (Black HP Out): present = No
Pin 0x16 (Not connected): present = No
Pin 0x18 (Black Mic): present = No
Pin 0x19 (Not connected): present = No
Pin 0x1a (Not connected): present = No


- The other pins present just a few options for input ex, mic, line in,
spdif.




--
Patrick Shirkey
Boost Hardware Ltd

  reply	other threads:[~2014-08-01  9:07 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
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 [this message]
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=61402.86.107.254.57.1406884028.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).