From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Brian Austin <brian.austin@cirrus.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>
Cc: "Gregory Clément" <gregory.clement@free-electrons.com>,
"Lior Amsalem" <alior@marvell.com>,
alsa-devel@alsa-project.org,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>
Subject: Regression caused by "ASoC: core: Rework SOC_DOUBLE_R_SX_TLV add SOC_SINGLE_SX_TLV"
Date: Thu, 30 Jan 2014 14:48:07 +0100 [thread overview]
Message-ID: <20140130144807.5b102b28@skate> (raw)
Brian, Liam, Mark,
I am currently bringing up audio support on the Marvell Armada 370 ARM
SoC, for which the development board uses the CS42L51 audio codec.
It turns out that the commit 1d99f2436d0d1c7741d6dfd9d27b5376cdbbca40
("ASoC: core: Rework SOC_DOUBLE_R_SX_TLV add SOC_SINGLE_SX_TLV") causes
a problem here, and reverting this commit gets things back to normal.
Basically, when this commit is applied, the "PCM", "Analog" and "ADC
Mixer" volume controls in alsamixer cannot be changed to any other
value than 60 or 61. The volume control doesn't allow to go above 61
and below 60. If I remember correctly, at the codec level, the values
configured for PCM in registers 0x10 and 0x11 are either 0x0 or 0x1
depending on whether you select 60 or 61 in alsamixer.
Reverting the commit mentioned above makes alsamixer behave normally:
the volume can be adjusted between 0 and 100 as expected, the values in
register 0x10 and 0x11 are meaningful, and the behavior is as expected:
with a volume to 0, I hear nothing in my headphones, with a volume set
to 100, the volume is maximum, with a nice progressive volume increase
in-between.
Therefore, I believe that the commit has a problem. I haven't yet
investigated where the problem is, maybe just the values passed to
SOC_DOUBLE_R_SX_TLV(), or maybe in the implementation of the volume
control functions themselves. I can certainly start investigating, but
maybe the author of the commit will immediately realize where the
problem could be.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2014-01-30 13:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 13:48 Thomas Petazzoni [this message]
2014-01-30 14:59 ` Regression caused by "ASoC: core: Rework SOC_DOUBLE_R_SX_TLV add SOC_SINGLE_SX_TLV" Brian Austin
2014-01-30 15:05 ` Thomas Petazzoni
2014-01-30 15:23 ` Brian Austin
2014-01-30 15:37 ` Brian Austin
2014-01-30 16:56 ` Thomas Petazzoni
2014-01-30 17:13 ` Brian Austin
2014-01-30 17:16 ` Thomas Petazzoni
2014-01-30 17:23 ` Brian Austin
2014-02-10 14:22 ` Thomas Petazzoni
2014-02-14 20:17 ` Mark Brown
2014-02-17 13:14 ` Thomas Petazzoni
2014-02-17 14:59 ` Michael Trimarchi
2014-02-17 15:03 ` Michael Trimarchi
2014-02-17 15:16 ` Thomas Petazzoni
2014-03-19 15:31 ` Brian Austin
2014-03-19 16:46 ` Thomas Petazzoni
2014-03-19 16:50 ` Mark Brown
2014-03-19 17:45 ` Thomas Petazzoni
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=20140130144807.5b102b28@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=alior@marvell.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=broonie@kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=liam.r.girdwood@linux.intel.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