From: Matt Flax <flatmax@flatmax.org>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/3] ASoC: cs4265: SOC_SINGLE register value error fix
Date: Wed, 29 Aug 2018 09:28:09 +1000 [thread overview]
Message-ID: <d108bb37-fd8f-b0d8-fc4a-883cd6d8da07@flatmax.org> (raw)
In-Reply-To: <20180828185756.GK2414@sirena.org.uk>
On 29/08/18 04:57, Mark Brown wrote:
> On Mon, Aug 27, 2018 at 08:58:42AM +1000, Matt Flax wrote:
>> 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
> How is this patch series different to the apparently identical three
> patch series you sent a few minutes earlier?
>
The identical patch series were sent from the wrong email address and
didn't go through to the list - because of moderation.
I apologise for the first mistake.
Matt
next prev parent reply other threads:[~2018-08-28 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 22:58 [PATCH 1/3] ASoC: cs4265: SOC_SINGLE register value error fix Matt Flax
2018-08-26 22:58 ` [PATCH 2/3] ASoC: cs4265: Add native 32bit I2S transport Matt Flax
2018-08-27 8:28 ` Charles Keepax
2018-08-27 9:51 ` Matt Flax
2018-08-28 18:56 ` Mark Brown
2018-08-28 23:31 ` Matt Flax
2018-08-29 0:26 ` Matt Flax
2018-08-29 8:22 ` Charles Keepax
2018-08-26 22:58 ` [PATCH 3/3] ASoC: cs4265: Add a SPDIF enable actl Matt Flax
2018-08-27 8:24 ` Charles Keepax
2018-08-27 9:52 ` Matt Flax
2018-08-27 8:30 ` [PATCH 1/3] ASoC: cs4265: SOC_SINGLE register value error fix Charles Keepax
2018-08-28 18:57 ` Mark Brown
2018-08-28 23:28 ` Matt Flax [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-26 22:55 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=d108bb37-fd8f-b0d8-fc4a-883cd6d8da07@flatmax.org \
--to=flatmax@flatmax.org \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.