From: Simon Trimmer <simont@opensource.cirrus.com>
To: 'Mark Brown' <broonie@kernel.org>,
'Charles Keepax' <ckeepax@opensource.cirrus.com>
Cc: <lgirdwood@gmail.com>, <linux-sound@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: RE: [PATCH 2/3] spi: cs42l43: Add speaker id support to the bridge configuration
Date: Tue, 18 Jun 2024 17:44:50 +0100 [thread overview]
Message-ID: <00dd01dac19e$d6a6cc60$83f46520$@opensource.cirrus.com> (raw)
In-Reply-To: <3bcb0b44-8885-40f9-938d-07b44116f3bf@sirena.org.uk>
On Tue, Jun 18, 2024 at 5:06 PM Mark Brown wrote:
> On Tue, Jun 11, 2024 at 02:25:55PM +0100, Charles Keepax wrote:
> > From: Simon Trimmer <simont@opensource.cirrus.com>
> >
> > OEMs can connect a number of types of speakers to the sidecar cs35l56
> > amplifiers and a different speaker requires a different firmware
> > configuration.
>
> This doesn't apply against current code, please check and resend.
I'll catchup with Charles about this tomorrow (hopefully) - the snag seems to be that an ancestor has been taken for integration via the linux-spi tree
https://lore.kernel.org/all/171778072618.80456.1164637774989487170.b4-ty@kernel.org/
-Simon
next prev parent reply other threads:[~2024-06-18 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 13:25 [PATCH 1/3] spi: cs42l43: Refactor accessing the SDCA extension properties Charles Keepax
2024-06-11 13:25 ` [PATCH 2/3] spi: cs42l43: Add speaker id support to the bridge configuration Charles Keepax
2024-06-18 16:06 ` Mark Brown
2024-06-18 16:44 ` Simon Trimmer [this message]
2024-06-11 13:25 ` [PATCH 3/3] ASoC: cs35l56: Attempt to read from cirrus,speaker-id device property first Charles Keepax
2024-06-12 17:09 ` (subset) [PATCH 1/3] spi: cs42l43: Refactor accessing the SDCA extension properties Mark Brown
2024-06-19 12:50 ` Mark Brown
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='00dd01dac19e$d6a6cc60$83f46520$@opensource.cirrus.com' \
--to=simont@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@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).