From: codekipper@gmail.com (codekipper at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi][PATCH v2 0/5] Add tested digital audio blocks to A64
Date: Mon, 29 Jan 2018 10:18:58 +0100 [thread overview]
Message-ID: <20180129091903.12319-1-codekipper@gmail.com> (raw)
From: Marcus Cooper <codekipper@gmail.com>
Hi All,
this patch series adds the digital audio blocks to the A64 SoC. No block
changes are necessary.
BR,
CK
---
v2 changes compared to v1 are:
- Added SoC specific compatiables
- moved spdif default pins to dtsi
- Added i2s2 block for HDMI as it has now been tested.
---
Marcus Cooper (5):
arm64: allwinner: a64: Add the SPDIF block and pin
arm64: allwinner: a64: Add SPDIF to the A64
arm64: allwinner: a64: Add SPDIF to the Pine64
arm64: allwinner: a64: Add DAI nodes
arm64: allwinner: a64: Add DAI node for HDMI
.../arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 5 ++
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 81 ++++++++++++++++++++++
2 files changed, 86 insertions(+)
--
2.16.1
next reply other threads:[~2018-01-29 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 9:18 codekipper at gmail.com [this message]
2018-01-29 9:18 ` [linux-sunxi][PATCH v2 1/5] arm64: allwinner: a64: Add the SPDIF block and pin codekipper at gmail.com
2018-01-29 9:19 ` [linux-sunxi][PATCH v2 2/5] arm64: allwinner: a64: Add SPDIF to the A64 codekipper at gmail.com
2018-01-29 9:19 ` [linux-sunxi][PATCH v2 3/5] arm64: allwinner: a64: Add SPDIF to the Pine64 codekipper at gmail.com
2018-01-29 9:19 ` [linux-sunxi][PATCH v2 4/5] arm64: allwinner: a64: Add DAI nodes codekipper at gmail.com
2018-01-29 9:19 ` [linux-sunxi][PATCH v2 5/5] arm64: allwinner: a64: Add DAI node for HDMI codekipper at gmail.com
2018-01-29 10:09 ` [linux-sunxi][PATCH v2 0/5] Add tested digital audio blocks to A64 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=20180129091903.12319-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).