From: Priit Laes <plaes@plaes.org>
To: "Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Russell King" <linux@arm.linux.org.uk>,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Emilio López" <emilio@elopez.com.ar>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
Priit Laes <plaes@plaes.org>
Subject: [PATCH 0/2] ARM: dts: sunxi: Add display clocks to sun[47]i.dtsi
Date: Tue, 10 May 2016 22:24:05 +0300 [thread overview]
Message-ID: <1462908247-10474-1-git-send-email-plaes@plaes.org> (raw)
Enable the display and TCON clocks that are needed to drive the display
engine, tcon and TV encoders.
Please note that currently the parent handling for clocks using
'allwinner,sun4i-a10-display-clk' compatible with number of parents !=4
is broken (like de_[bf]e[01]_clk clocks present in patches).
Priit Laes (2):
ARM: sun4i: A10: Add display and TCON clocks
ARM: sun7i: A20: Add display and TCON clocks
arch/arm/boot/dts/sun4i-a10.dtsi | 91 ++++++++++++++++++++++++++++++++++++----
arch/arm/boot/dts/sun7i-a20.dtsi | 85 ++++++++++++++++++++++++++++++++++---
2 files changed, 164 insertions(+), 12 deletions(-)
--
2.8.2
next reply other threads:[~2016-05-10 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 19:24 Priit Laes [this message]
2016-05-10 19:24 ` [PATCH 1/2] ARM: sun4i: A10: Add display and TCON clocks Priit Laes
2016-05-10 19:24 ` [PATCH 2/2] ARM: sun7i: A20: " Priit Laes
2016-05-11 19:12 ` [PATCH 0/2] ARM: dts: sunxi: Add display clocks to sun[47]i.dtsi 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=1462908247-10474-1-git-send-email-plaes@plaes.org \
--to=plaes@plaes.org \
--cc=devicetree@vger.kernel.org \
--cc=emilio@elopez.com.ar \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®