From: codekipper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
Marcus Cooper
<codekipper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/3] Enable SPDIF on the Beelink X2
Date: Fri, 27 Jan 2017 16:48:05 +0100 [thread overview]
Message-ID: <20170127154808.19229-1-codekipper@gmail.com> (raw)
From: Marcus Cooper <codekipper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi All,
here is the patchset required to get SPDIF working on the Beelink X2
which is a H3 based STB.
BR,
CK
Marcus Cooper (3):
ARM: dts: sun8i-h3: Add SPDIF TX pin to the H3
ARM: dts: sun8i-h3: Add the SPDIF block to the H3
ARM: dts: sun8i-h3: Add SPDIF to the Beelink X2
arch/arm/boot/dts/sun8i-h3-beelink-x2.dts | 24 ++++++++++++++++++++++++
arch/arm/boot/dts/sun8i-h3.dtsi | 18 ++++++++++++++++++
2 files changed, 42 insertions(+)
--
2.11.0
next reply other threads:[~2017-01-27 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 15:48 codekipper-Re5JQEeQqe8AvxtiuMwx3w [this message]
[not found] ` <20170127154808.19229-1-codekipper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-27 15:48 ` [PATCH 1/3] ARM: dts: sun8i-h3: Add SPDIF TX pin to the H3 codekipper-Re5JQEeQqe8AvxtiuMwx3w
2017-01-27 15:48 ` [PATCH 2/3] ARM: dts: sun8i-h3: Add the SPDIF block " codekipper-Re5JQEeQqe8AvxtiuMwx3w
2017-01-27 15:48 ` [PATCH 3/3] ARM: dts: sun8i-h3: Add SPDIF to the Beelink X2 codekipper-Re5JQEeQqe8AvxtiuMwx3w
2017-01-27 20:10 ` [PATCH 0/3] Enable SPDIF on " Maxime Ripard
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=20170127154808.19229-1-codekipper@gmail.com \
--to=codekipper-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.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).