From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: James Ogletree <jogletre@opensource.cirrus.com>
Cc: <dmitry.torokhov@gmail.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<lee@kernel.org>, <broonie@kernel.org>, <jeff@labundy.com>,
<patches@opensource.cirrus.com>, <linux-sound@vger.kernel.org>,
<linux-input@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v8 1/5] firmware: cs_dsp: Add write sequencer interface
Date: Wed, 21 Feb 2024 09:22:45 +0000 [thread overview]
Message-ID: <ZdXA5cNFd+hvw//F@ediswmail9.ad.cirrus.com> (raw)
In-Reply-To: <20240221003630.2535938-2-jogletre@opensource.cirrus.com>
On Wed, Feb 21, 2024 at 12:36:26AM +0000, James Ogletree wrote:
> A write sequencer is a sequence of register addresses
> and values executed by some Cirrus DSPs following
> power state transitions.
>
> Add support for Cirrus drivers to update or add to a
> write sequencer present in firmware.
>
> Signed-off-by: James Ogletree <jogletre@opensource.cirrus.com>
> ---
Think this one looks good to me:
Reviewed-by: Charles Keepax <ckeepax@opensource.cirrus.com>
Thanks,
Charles
next prev parent reply other threads:[~2024-02-21 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 0:36 [PATCH v8 0/5] Add support for CS40L50 James Ogletree
2024-02-21 0:36 ` [PATCH v8 1/5] firmware: cs_dsp: Add write sequencer interface James Ogletree
2024-02-21 9:22 ` Charles Keepax [this message]
2024-02-21 0:36 ` [PATCH v8 2/5] dt-bindings: input: cirrus,cs40l50: Add initial DT binding James Ogletree
2024-02-21 0:36 ` [PATCH v8 3/5] mfd: cs40l50: Add support for CS40L50 core driver James Ogletree
2024-03-01 9:17 ` Lee Jones
2024-03-01 16:36 ` James Ogletree
2024-03-05 9:58 ` Lee Jones
2024-03-05 10:20 ` Charles Keepax
2024-03-05 20:55 ` James Ogletree
2024-02-21 0:36 ` [PATCH v8 4/5] Input: cs40l50 - Add support for the CS40L50 haptic driver James Ogletree
2024-02-21 0:36 ` [PATCH v8 5/5] ASoC: cs40l50: Support I2S streaming to CS40L50 James Ogletree
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=ZdXA5cNFd+hvw//F@ediswmail9.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff@labundy.com \
--cc=jogletre@opensource.cirrus.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=robh+dt@kernel.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