From: Olivier Moysan <olivier.moysan@st.com>
To: <lgirdwood@gmail.com>, <broonie@kernel.org>, <perex@perex.cz>,
<tiwai@suse.com>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@st.com>, <alsa-devel@alsa-project.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-kernel@vger.kernel.org>, <olivier.moysan@st.com>,
<arnaud.pouliquen@st.com>
Cc: benjamin.gaignard@st.com
Subject: [PATCH 0/3] ASoC: stm32: spdifrx: add some features
Date: Mon, 6 May 2019 14:44:03 +0200 [thread overview]
Message-ID: <1557146646-18150-1-git-send-email-olivier.moysan@st.com> (raw)
Update and add some features in STM32 SPDIFRX driver.
- pdate pcm hardware constraints
- change trace level on iec control
- add management of identification registers
Olivier Moysan (3):
ASoC: stm32: spdifrx: update pcm hardware constraints
ASoC: stm32: spdifrx: change trace level on iec control
ASoC: stm32: spdifrx: manage identification registers
sound/soc/stm/stm32_spdifrx.c | 42 ++++++++++++++++++++++++++++++++++++++----
1 file changed, 38 insertions(+), 4 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-05-06 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 12:44 Olivier Moysan [this message]
2019-05-06 12:44 ` [PATCH 1/3] ASoC: stm32: spdifrx: update pcm hardware constraints Olivier Moysan
2019-05-06 15:03 ` Applied "ASoC: stm32: spdifrx: update pcm hardware constraints" to the asoc tree Mark Brown
2019-05-06 12:44 ` [PATCH 2/3] ASoC: stm32: spdifrx: change trace level on iec control Olivier Moysan
2019-05-06 15:03 ` Applied "ASoC: stm32: spdifrx: change trace level on iec control" to the asoc tree Mark Brown
2019-05-06 12:44 ` [PATCH 3/3] ASoC: stm32: spdifrx: manage identification registers Olivier Moysan
2019-05-06 15:03 ` Applied "ASoC: stm32: spdifrx: manage identification registers" to the asoc tree Mark Brown
2019-05-07 2:28 ` Mark Brown
2019-05-07 2:30 ` Mark Brown
2019-05-07 2:32 ` 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=1557146646-18150-1-git-send-email-olivier.moysan@st.com \
--to=olivier.moysan@st.com \
--cc=alexandre.torgue@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=benjamin.gaignard@st.com \
--cc=broonie@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=mcoquelin.stm32@gmail.com \
--cc=perex@perex.cz \
--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