From: Matt Flax <flatmax@flatmax.org>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: cs4265 : alsactl store and "C data buffer" fails
Date: Tue, 7 May 2019 11:06:28 +1000 [thread overview]
Message-ID: <bdc0a30f-c6f3-8ccb-f556-1d1a6a68f3b9@flatmax.org> (raw)
Hi,
When alsactl store is run with a cs4265 chip, the following error occurs
(from https://github.com/Audio-Injector/Ultra/issues/25) :
$ sudo alsactl store
alsactl: get_control:256: Cannot read control '2,0,0,C Data Buffer,0':
Input/output error
Upon commenting out the C data buffer control it works :
https://github.com/torvalds/linux/blob/master/sound/soc/codecs/cs4265.c#L163
Can you suggest a suitable method for fixing this bug ?
thanks
Matt
next reply other threads:[~2019-05-07 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 1:06 Matt Flax [this message]
2019-05-07 6:08 ` cs4265 : alsactl store and "C data buffer" fails Clemens Ladisch
2019-05-08 6:34 ` 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=bdc0a30f-c6f3-8ccb-f556-1d1a6a68f3b9@flatmax.org \
--to=flatmax@flatmax.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.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).