From: Lucas Stach <l.stach@pengutronix.de>
To: Timur Tabi <timur@kernel.org>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Angus Ainslie <angus@akkea.ca>,
NXP Linux Team <linux-imx@nxp.com>,
kernel@pengutronix.de, patchwork-lst@pengutronix.de
Subject: [PATCH 0/3] i.MX8M support for FSL SAI
Date: Wed, 17 Jul 2019 12:56:32 +0200 [thread overview]
Message-ID: <20190717105635.18514-1-l.stach@pengutronix.de> (raw)
Hi all,
those are the changes that are absolutely needed to support the i.MX8M
SAI block. The most noticable difference is the moved register layout,
due to the hardware guys adding two version registers at the start of
the register map and considerable bigger FIFO sizes.
Downstream has a lot more changes to support new features, but those
3 patches at least allows me to play back audio on i.MX8M based
systems.
Regards,
Lucas
Lucas Stach (3):
ASoC: fsl_sai: add of_match data
ASoC: fsl_sai: derive TX FIFO watermark from FIFO depth
ASoC: fsl_sai: add i.MX8M support
.../devicetree/bindings/sound/fsl-sai.txt | 2 +-
sound/soc/fsl/fsl_sai.c | 45 +++++++++++++++----
sound/soc/fsl/fsl_sai.h | 8 +++-
3 files changed, 44 insertions(+), 11 deletions(-)
--
2.20.1
next reply other threads:[~2019-07-17 10:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 10:56 Lucas Stach [this message]
2019-07-17 10:56 ` [PATCH 1/3] ASoC: fsl_sai: add of_match data Lucas Stach
2019-07-17 13:42 ` Angus Ainslie
2019-07-17 14:17 ` Daniel Baluta
2019-07-22 12:22 ` Applied "ASoC: fsl_sai: add of_match data" to the asoc tree Mark Brown
2019-07-17 10:56 ` [PATCH 2/3] ASoC: fsl_sai: derive TX FIFO watermark from FIFO depth Lucas Stach
2019-07-17 13:43 ` Angus Ainslie
2019-07-22 12:22 ` Applied "ASoC: fsl_sai: derive TX FIFO watermark from FIFO depth" to the asoc tree Mark Brown
2019-07-17 10:56 ` [PATCH 3/3] ASoC: fsl_sai: add i.MX8M support Lucas Stach
2019-07-17 13:45 ` Angus Ainslie
2019-07-22 10:39 ` Daniel Baluta
2019-07-22 13:41 ` Angus Ainslie
2019-07-17 14:16 ` Daniel Baluta
2019-07-17 14:33 ` Lucas Stach
2019-07-17 15:06 ` Daniel Baluta
2019-07-17 15:15 ` Angus Ainslie
2019-07-18 8:35 ` Daniel Baluta
2019-07-18 19:11 ` Cezary Rojewski
2019-07-18 19:22 ` Daniel Baluta
2019-07-18 20:19 ` Cezary Rojewski
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=20190717105635.18514-1-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=angus@akkea.ca \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=nicoleotsuka@gmail.com \
--cc=patchwork-lst@pengutronix.de \
--cc=timur@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.