From: codekipper@gmail.com (codekipper at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ASoC: Extended SPDIF support to Allwinner A31 SoCs
Date: Sat, 30 Jul 2016 16:27:14 +0200 [thread overview]
Message-ID: <20160730142716.29377-1-codekipper@gmail.com> (raw)
From: Marcus Cooper <codekipper@gmail.com>
This patch set extends the current support of the Allwinner SPDIF
transceiver to include the A31 SoC.
For now just the SPDIF transmitter has been tested on the Mele I7.
In order for this patch set to be functional then we require changes
to the clocks and the device tree. For those that are interested I've
pushed all the required patches here
https://github.com/codekipper/linux-sunxi/commits/a31-spdif
Thanks in advance,
CK
Marcus Cooper (2):
ASoC: sunxi: Add bindings for sun6i to SPDIF
ASoC: sunxi: compatibility for sun6i to SPDIF
.../devicetree/bindings/sound/sunxi,sun4i-spdif.txt | 3 +++
sound/soc/sunxi/sun4i-spdif.c | 17 ++++++++++++++++-
2 files changed, 19 insertions(+), 1 deletion(-)
--
2.9.2
next reply other threads:[~2016-07-30 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 14:27 codekipper at gmail.com [this message]
2016-07-30 14:27 ` [PATCH 1/2] ASoC: sunxi: Add bindings for sun6i to SPDIF codekipper at gmail.com
2016-07-30 15:17 ` Maxime Ripard
2016-07-30 15:34 ` Code Kipper
2016-07-30 15:40 ` Maxime Ripard
2016-07-30 14:27 ` [PATCH 2/2] ASoC: sunxi: compatibility " codekipper at gmail.com
2016-07-30 14:40 ` [linux-sunxi] " Julian Calaby
2016-07-30 15:21 ` Maxime Ripard
2016-07-30 14:52 ` Icenowy Zheng
2016-07-30 15:20 ` maxime.ripard at free-electrons.com
2016-07-30 15:23 ` Icenowy Zheng
2016-08-01 13:39 ` [linux-sunxi] " Chen-Yu Tsai
2016-08-01 15:02 ` Icenowy Zheng
2016-08-22 16:04 ` Maxime Ripard
2016-07-30 15:19 ` Maxime Ripard
2016-08-12 12:29 ` Applied "ASoC: sunxi: compatibility for sun6i to SPDIF" 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=20160730142716.29377-1-codekipper@gmail.com \
--to=codekipper@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).