From: Mark Brown <broonie@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
Jonathan Albrieux <jonathan.albrieux@gmail.com>
Subject: Re: [PATCH 2/2] ASoC: codecs: Add Awinic AW8738 audio amplifier driver
Date: Tue, 1 Mar 2022 12:47:10 +0000 [thread overview]
Message-ID: <Yh4VziYJ2M2aenjz@sirena.org.uk> (raw)
In-Reply-To: <20220301123742.72146-3-stephan@gerhold.net>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Tue, Mar 01, 2022 at 01:37:42PM +0100, Stephan Gerhold wrote:
> From: Jonathan Albrieux <jonathan.albrieux@gmail.com>
>
> The Awinic AW8738 is a simple audio amplifier using an enable GPIO.
> The main difference to simple-amplifier is that there is a "one-wire
> pulse control" that allows configuring the amplifier to one of a few
> pre-defined modes.
I only have this patch, nothing else from the rest of the series.
What's the story with dependencies?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-03-01 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 12:37 [PATCH 0/2] ASoC: codecs: Add Awinic AW8738 audio amplifier driver Stephan Gerhold
2022-03-01 12:37 ` [PATCH 1/2] ASoC: dt-bindings: Add schema for "awinic,aw8738" Stephan Gerhold
2022-03-01 13:36 ` Mark Brown
2022-03-01 13:54 ` Stephan Gerhold
2022-03-01 14:05 ` Mark Brown
2022-03-02 18:26 ` Rob Herring
2022-03-01 12:37 ` [PATCH 2/2] ASoC: codecs: Add Awinic AW8738 audio amplifier driver Stephan Gerhold
2022-03-01 12:47 ` Mark Brown [this message]
2022-03-01 12:53 ` Stephan Gerhold
2022-03-01 13:26 ` Mark Brown
2022-03-01 13:45 ` Mark Brown
2022-03-01 14:13 ` Stephan Gerhold
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=Yh4VziYJ2M2aenjz@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan.albrieux@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--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