From: Matt Flax <flatmax@flatmax.com>
To: Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org,
Brian Austin <brian.austin@cirrus.com>,
Paul Handrigan <Paul.Handrigan@cirrus.com>,
ckeepax@opensource.cirrus.com
Cc: Matt Flax <flatmax@flatmax.org>
Subject: [PATCH 1/3] ASoC: cs4265: SOC_SINGLE register value error fix
Date: Mon, 27 Aug 2018 08:55:09 +1000 [thread overview]
Message-ID: <20180826225511.13619-1-flatmax@flatmax.com> (raw)
From: Matt Flax <flatmax@flatmax.org>
The cs4265 driver declares the "MMTLR Data Switch" register setting with
a 0 register value rather then the 0x12 register (CS4265_SPDIF_CTL2).
This incorrect value causes alsamixer to fault with the output :
cannot load mixer controls: Input/output error
This patch corrects the register value. alsamixer now runs.
Signed-off-by: Matt Flax <flatmax@flatmax.org>
---
sound/soc/codecs/cs4265.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sound/soc/codecs/cs4265.c b/sound/soc/codecs/cs4265.c
index 275677de..15b4ae04 100644
--- a/sound/soc/codecs/cs4265.c
+++ b/sound/soc/codecs/cs4265.c
@@ -157,8 +157,7 @@ static const struct snd_kcontrol_new cs4265_snd_controls[] = {
SOC_SINGLE("Validity Bit Control Switch", CS4265_SPDIF_CTL2,
3, 1, 0),
SOC_ENUM("SPDIF Mono/Stereo", spdif_mono_stereo_enum),
- SOC_SINGLE("MMTLR Data Switch", 0,
- 1, 1, 0),
+ SOC_SINGLE("MMTLR Data Switch", CS4265_SPDIF_CTL2, 0, 1, 0),
SOC_ENUM("Mono Channel Select", spdif_mono_select_enum),
SND_SOC_BYTES("C Data Buffer", CS4265_C_DATA_BUFF, 24),
};
--
2.17.1
next reply other threads:[~2018-08-26 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 22:55 Matt Flax [this message]
2018-08-26 22:55 ` [PATCH 2/3] ASoC: cs4265: Add native 32bit I2S transport Matt Flax
2018-08-26 22:55 ` [PATCH 3/3] ASoC: cs4265: Add a SPDIF enable actl Matt Flax
2018-08-27 22:37 ` [EXTERNAL] [PATCH 1/3] ASoC: cs4265: SOC_SINGLE register value error fix Paul Handrigan
-- strict thread matches above, loose matches on Subject: below --
2018-08-26 22:58 Matt Flax
2018-08-27 8:30 ` Charles Keepax
2018-08-28 18:57 ` Mark Brown
2018-08-28 23:28 ` Matt Flax
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=20180826225511.13619-1-flatmax@flatmax.com \
--to=flatmax@flatmax.com \
--cc=Paul.Handrigan@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=brian.austin@cirrus.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=flatmax@flatmax.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).