public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Ulricht <david.ulricht434@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: CS8409 Macbook Pro 2016 2017
Date: Sat, 04 Aug 2018 08:48:10 +0200	[thread overview]
Message-ID: <s5h7el6vd91.wl-tiwai@suse.de> (raw)
In-Reply-To: <CALbf9MzcxBqkBP4mbUKht72Ga6VnTubeiHcTr2joEf7i-enxFQ@mail.gmail.com>

On Sat, 04 Aug 2018 04:07:43 +0200,
David Ulricht wrote:
> 
> Hello,
> 
> Macbook pro models containing CS8409 for sure are:
> MBP131 MBP141.I own MBP 14,1 e.g. 2017 model.
> 
> I'm attaching working sound configuration from Windows 10 registry (note
> that the cs420x might need to be ignored or might be important i don't
> really know). I believe what is really used is in the PinConfigOverride
> section.

Comparing between BIOS default (init_pin_cfg in alsa-info.sh output)
and your override (user_pin_cfg), there aren't so many changes.
All changes are pretty minor, and I guess it won't influence on the
driver behavior.

> Interesting thing to note is that sound in MacOS is much louder than
> Bootcamp Windows, would be nice to hear how loud is on linux.

This is possibly with some vendor-specific GPIO or COEF verbs.
Or it's some direct I2C control.  The INI file mentions it.
And that's above HD-audio driver's responsibility.

> I did convert PinConfigOverride HEX strings to [pincfg] format in the
> attached hda-jack-retask.fw thanks to Takashi's guidance.
> 
> I'm attaching also alsamixer ASCII. Only PCM, no Master ?

It's because the codec chip has no output amplifier at all.
So there can be neither output volume nor mute control on this chip.

> What I have tried is execute:
> hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_MASK 0x@@
> hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DIRECTION 0x@@
> hda-verb /dev/snd/hwC0D0 0x01 SET_GPIO_DATA 0x@@
> putting @@ from 0x00 to 0x50

There are eight GPIOs, so you'd need to test each bit, i.e. 0x01,
0x02, 0x04, 0x08, ... 0x80.

And how is the current situation?  You can't play *and* record
anything from any inputs / outputs?


Takashi

  parent reply	other threads:[~2018-08-04  6:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04  2:07 CS8409 Macbook Pro 2016 2017 David Ulricht
2018-08-04  2:18 ` David Ulricht
2018-08-04  6:48 ` Takashi Iwai [this message]
     [not found]   ` <CALbf9Mw=Y5ddFZDZQ4_mfYCHxKb9XFHN3v5ge0JaTca7NLMM7A@mail.gmail.com>
2018-08-04 16:26     ` Takashi Iwai
     [not found]       ` <CALbf9MwN4pEk26R9c2-UMxzvLXQ3OOBTcqgdSvXeFb-dw7-Wnw@mail.gmail.com>
2018-08-04 17:13         ` Takashi Iwai
2018-08-04 20:30           ` David Ulricht
2018-08-05 18:05             ` Takashi Iwai
2018-08-05 18:58               ` David Ulricht
2018-11-16 14:02               ` David Ulricht
2018-11-16 14:36                 ` Takashi Iwai
2018-11-16 16:50                   ` David Ulricht
2018-11-16 17:31                     ` Takashi Iwai
2018-11-19 17:30                       ` David Ulricht
2018-11-19 18:47                         ` Takashi Iwai
2018-11-23 17:26                           ` David Ulricht
2018-11-27  2:42                             ` David Ulricht
2018-08-05 19:32             ` Lukas Wunner

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=s5h7el6vd91.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.ulricht434@gmail.com \
    /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