From: Rob Herring <robh@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, broonie@kernel.org
Subject: Re: [PATCH 4/5] ASoC: dt-bindings: cs35l45: Cirrus Logic CS35L45 Smart Amp
Date: Mon, 28 Mar 2022 18:35:10 -0500 [thread overview]
Message-ID: <YkJGLo/dAAO3QMq5@robh.at.kernel.org> (raw)
In-Reply-To: <20220318162943.1578102-5-rf@opensource.cirrus.com>
On Fri, 18 Mar 2022 16:29:42 +0000, Richard Fitzgerald wrote:
> This adds the schema binding for the Cirrus Logic CS35L45 Smart Amp
> and associated header file.
>
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> ---
> .../bindings/sound/cirrus,cs35l45.yaml | 75 +++++++++++++++++++
> MAINTAINERS | 2 +
> include/dt-bindings/sound/cs35l45.h | 20 +++++
> 3 files changed, 97 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/cirrus,cs35l45.yaml
> create mode 100644 include/dt-bindings/sound/cs35l45.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-03-28 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 16:29 [PATCH 0/5] ASoC: Add a driver for the Cirrus Logic CS35L45 Smart Amplifier Richard Fitzgerald
2022-03-18 16:29 ` [PATCH 1/5] ASoC: soc.h: Add SOC_SINGLE_S_TLV() macro Richard Fitzgerald
2022-03-18 16:29 ` [PATCH 2/5] ASoC: soc-utils: Add helper to calculate BCLK from TDM info Richard Fitzgerald
2022-03-18 16:29 ` [PATCH 3/5] ASoC: soc-utils: Add kunit test for snd_soc_tdm_params_to_bclk() Richard Fitzgerald
2022-03-18 16:29 ` [PATCH 4/5] ASoC: dt-bindings: cs35l45: Cirrus Logic CS35L45 Smart Amp Richard Fitzgerald
2022-03-28 23:35 ` Rob Herring [this message]
2022-03-18 16:29 ` [PATCH 5/5] ASoC: cs35l45: Add driver for " Richard Fitzgerald
2022-04-05 13:51 ` Richard Fitzgerald
2022-04-06 13:28 ` [PATCH 0/5] ASoC: Add a driver for the Cirrus Logic CS35L45 Smart Amplifier 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=YkJGLo/dAAO3QMq5@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@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