From: Olivier MOYSAN <olivier.moysan@st.com>
To: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"robh@kernel.org" <robh@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
Arnaud POULIQUEN <arnaud.pouliquen@st.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ASoC: stm32: i2s: add master clock provider
Date: Tue, 3 Nov 2020 13:38:27 +0000 [thread overview]
Message-ID: <20ed825b-10b6-e71f-9da4-91df38a950de@st.com> (raw)
In-Reply-To: <20200911091952.14696-1-olivier.moysan@st.com>
Hi Mark,
Gentle reminder on this series, as it seems that there was no update
since Rob's "reviewed-by" for dt bindings, on 11/09.
BRs
Olivier
On 9/11/20 11:19 AM, Olivier Moysan wrote:
> Add master clock generation support in STM32 I2S driver.
>
> Olivier Moysan (2):
> ASoC: dt-bindings: add mclk provider support to stm32 i2s
> ASoC: stm32: i2s: add master clock provider
>
> .../bindings/sound/st,stm32-i2s.yaml | 4 +
> sound/soc/stm/stm32_i2s.c | 310 +++++++++++++++---
> 2 files changed, 270 insertions(+), 44 deletions(-)
>
next prev parent reply other threads:[~2020-11-03 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 9:19 [PATCH 0/2] ASoC: stm32: i2s: add master clock provider Olivier Moysan
2020-09-11 9:19 ` [PATCH 1/2] ASoC: dt-bindings: add mclk provider support to stm32 i2s Olivier Moysan
2020-09-22 22:40 ` Rob Herring
2020-09-11 9:19 ` [PATCH 2/2] ASoC: stm32: i2s: add master clock provider Olivier Moysan
2020-11-03 13:38 ` Olivier MOYSAN [this message]
2020-11-03 14:53 ` [PATCH 0/2] " 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=20ed825b-10b6-e71f-9da4-91df38a950de@st.com \
--to=olivier.moysan@st.com \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
/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).