From: Jerome Brunet <jbrunet@baylibre.com>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: [PATCH 0/4] ASoC: meson: axg-tdm: i2s format fixups
Date: Thu, 13 Jun 2019 13:42:29 +0200 [thread overview]
Message-ID: <20190613114233.21130-1-jbrunet@baylibre.com> (raw)
The patchset fixes a few mistakes regarding the format on the i2s bus
on the Amlogic axg tdm drivers.
Jerome Brunet (4):
ASoC: meson: axg-tdmin: right_j is not supported
ASoC: meson: axg-tdmout: right_j is not supported
ASoC: meson: axg-tdm: fix sample clock inversion
ASoC: meson: axg-tdm: consistently use SND_SOC_DAIFMT defines
sound/soc/meson/axg-tdm-interface.c | 4 ++--
sound/soc/meson/axg-tdm.h | 2 +-
sound/soc/meson/axg-tdmin.c | 1 -
sound/soc/meson/axg-tdmout.c | 1 -
4 files changed, 3 insertions(+), 5 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-13 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 11:42 Jerome Brunet [this message]
2019-06-13 11:42 ` [PATCH 1/4] ASoC: meson: axg-tdmin: right_j is not supported Jerome Brunet
2019-06-13 19:06 ` Applied "ASoC: meson: axg-tdmin: right_j is not supported" to the asoc tree Mark Brown
2019-06-13 11:42 ` [PATCH 2/4] ASoC: meson: axg-tdmout: right_j is not supported Jerome Brunet
2019-06-13 19:06 ` Applied "ASoC: meson: axg-tdmout: right_j is not supported" to the asoc tree Mark Brown
2019-06-13 11:42 ` [PATCH 3/4] ASoC: meson: axg-tdm: fix sample clock inversion Jerome Brunet
2019-06-13 19:06 ` Applied "ASoC: meson: axg-tdm: fix sample clock inversion" to the asoc tree Mark Brown
2019-06-13 11:42 ` [PATCH 4/4] ASoC: meson: axg-tdm: consistently use SND_SOC_DAIFMT defines Jerome Brunet
2019-06-13 19:06 ` Applied "ASoC: meson: axg-tdm: consistently use SND_SOC_DAIFMT defines" to the asoc tree 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=20190613114233.21130-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-amlogic@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).