From: Jerome Brunet <jbrunet@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] ASoC: es7134: add support for the es7154
Date: Mon, 02 Jul 2018 12:15:28 +0200 [thread overview]
Message-ID: <1530526528.2900.145.camel@baylibre.com> (raw)
In-Reply-To: <20180702100533.GD18211@sirena.org.uk>
On Mon, 2018-07-02 at 11:05 +0100, Mark Brown wrote:
> On Fri, Jun 29, 2018 at 05:09:24PM +0200, Jerome Brunet wrote:
>
> > { .compatible = "everest,es7134", .data = &es7134_chip },
> > { .compatible = "everest,es7144", .data = &es7134_chip },
> > + { .compatible = "everest,es7154", .data = &es7154_chip },
> > { }
>
> This needs to be added to the DT documentation.
I believe I added this in patch 3 of this serie, which I'll resubmit.
Shall I resubmit this patch along with it ?
next prev parent reply other threads:[~2018-07-02 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 15:09 [PATCH 0/5] ASoC: es7134: driver updates Jerome Brunet
2018-06-29 15:09 ` [PATCH 1/5] ASoC: es7134: remove 64kHz rate from the supported rates Jerome Brunet
2018-07-02 10:09 ` Applied "ASoC: es7134: remove 64kHz rate from the supported rates" to the asoc tree Mark Brown
2018-06-29 15:09 ` [PATCH 2/5] ASoC: es7134: check if mclk rate is valid Jerome Brunet
2018-07-02 10:09 ` Applied "ASoC: es7134: check if mclk rate is valid" to the asoc tree Mark Brown
2018-06-29 15:09 ` [PATCH 3/5] ASoC: es7134: update DT binding with new compatible and supplies Jerome Brunet
2018-07-02 10:04 ` Mark Brown
2018-07-02 10:11 ` Jerome Brunet
2018-06-29 15:09 ` [PATCH 4/5] ASoC: es7134: Add VDD and AVDD power supplies Jerome Brunet
2018-07-02 10:09 ` Applied "ASoC: es7134: Add VDD and AVDD power supplies" to the asoc tree Mark Brown
2018-06-29 15:09 ` [PATCH 5/5] ASoC: es7134: add support for the es7154 Jerome Brunet
2018-07-02 10:05 ` Mark Brown
2018-07-02 10:15 ` Jerome Brunet [this message]
2018-07-02 10:21 ` 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=1530526528.2900.145.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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