From: Rob Herring <robh@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Mark Brown <broonie@kernel.org>,
Vincent Knecht <vincent.knecht@mailoo.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [RFC PATCH 1/2] ASoC: dt-bindings: codecs: Add bindings for nxp, tfa989x
Date: Mon, 17 May 2021 20:09:41 -0500 [thread overview]
Message-ID: <20210518010941.GA3571094@robh.at.kernel.org> (raw)
In-Reply-To: <20210513104129.36583-1-stephan@gerhold.net>
On Thu, 13 May 2021 12:41:28 +0200, Stephan Gerhold wrote:
> NXP/Goodix TFA989X (TFA1) amplifiers are controlled via an I2C bus.
> Add simple device tree bindings that describe how to set them up
> in the device tree.
>
> Right now only nxp,tfa9895 is supported but this will be extended
> to at least nxp,tfa9897 in the near future.
>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> .../bindings/sound/nxp,tfa989x.yaml | 54 +++++++++++++++++++
> 1 file changed, 54 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/nxp,tfa989x.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-05-18 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 10:41 [RFC PATCH 1/2] ASoC: dt-bindings: codecs: Add bindings for nxp,tfa989x Stephan Gerhold
2021-05-13 10:41 ` [RFC PATCH 2/2] ASoC: codecs: Add driver for NXP/Goodix TFA989x (TFA1) amplifiers Stephan Gerhold
2021-05-18 1:09 ` Rob Herring [this message]
2021-05-24 11:59 ` [PATCH RFC 1/2] ASoC: dt-bindings: codecs: Add bindings for nxp, tfa989x 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=20210518010941.GA3571094@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=vincent.knecht@mailoo.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).