From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Joseph Wang <joequant@gmail.com>
Cc: KCHSU0@nuvoton.com, alsa-devel@alsa-project.org, CTLIN0@nuvoton.com
Subject: Re: Cherry trail and Nau 88l24 codec
Date: Wed, 7 Dec 2016 08:19:19 -0600 [thread overview]
Message-ID: <ddbc8fcf-024d-fe34-ba9c-c580c521baa2@linux.intel.com> (raw)
In-Reply-To: <CAPoeEY_QV8inYz=rAf5sveTtB5636sNwGyy0Uf==mPWuq0DZPg@mail.gmail.com>
On 12/7/16 3:21 AM, Joseph Wang wrote:
> Two new items:
>
> 1) The firmware time outs happen when I try to turn on all of the switches
> in alsa mixer and set the volumes and gains of everything to 100%, It
> doesn't like that.
>
> 2) In pulseaudio, I'm only seeing the output device "Headphones". Not sure
> where this is getting set.
>
> But it looks like things are working up until the mixer, and it's a matter
> of finding the right magic configurations for those.
Don't try random settings and 100% volume, you're going to lose your
hearing or speakers, or both.
start from the mixer values used here for the dsp
https://github.com/plbossart/UCM/blob/master/bytcr-rt5640/HiFi
remove everything related to rt5640 and add the modes for each
input/output supported by your codec, starting from low volume until you
find a setting that seems fine.
you really want to copy paste this directory and rename as needed, and
copy the files in /usr/share/alsa/ucm.
next prev parent reply other threads:[~2016-12-07 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 1:16 Cherry trail and Nau 88l24 codec Joseph Wang
2016-12-04 3:13 ` Pierre-Louis Bossart
2016-12-04 14:19 ` Joseph Wang
2016-12-05 7:29 ` KCHSU0
2016-12-05 3:43 ` KCHSU0
2016-12-05 6:45 ` Joseph Wang
2016-12-05 8:58 ` KCHSU0
2016-12-05 18:10 ` Pierre-Louis Bossart
2016-12-07 8:01 ` Joseph Wang
2016-12-07 9:21 ` Joseph Wang
2016-12-07 14:19 ` Pierre-Louis Bossart [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-09 14:14 Joseph Wang
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=ddbc8fcf-024d-fe34-ba9c-c580c521baa2@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=joequant@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;
as well as URLs for NNTP newsgroup(s).