From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] ARM: dts: sunxi: Fix simplefb not working in 4.7-rc1
Date: Sat, 4 Jun 2016 20:05:23 +0200 [thread overview]
Message-ID: <1465063524-4925-1-git-send-email-hdegoede@redhat.com> (raw)
Hi Maxime,
While testing 4.7-rc1 / linux-sunxi/sunxi-next on a A10s I noticed that
hdmi out is no longer working (screen goes black when the kernel turns
of unused clocks).
This is caused by the dtsi for sun4i / sun5i / sun7i based boards now
listing pll3, without pll3 being added to the clocks list for the
simplefb nodes.
For sun5i-r8 this does not happen because it lists the de_be and
tcon_ch#_clk in the framebuffer node's clocks which will in turn keep
ppl3 (and pll5) alive.
With this commit:
https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?h=sunxi/for-next&id=eadc0660c2bca3a2a6d2c15fe04bc2aaa2709cef
This is also fixed for A13 based devices, but it still is a problem for
A10s, hence this patch, which sits on top of the commit I just linked too.
Note that we've the same problem in 4.7-rc1 for A10 / A20, this is fixed
by these 2 commits:
https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?id=5a7f2310cc847a73852e70bc720a61ca9bf986a6
https://git.kernel.org/cgit/linux/kernel/git/mripard/linux.git/commit/?id=c79255ca4d7b67cce4eac4dd532e097ce49f3679
This also means that we must send all 3 linked commits + the patch I'm
sending now to 4.7 as fixes, to avoid regressing in 4.7.
Regards,
Hans
next reply other threads:[~2016-06-04 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 18:05 Hans de Goede [this message]
2016-06-04 18:05 ` [PATCH] ARM: dts: sun5i: Move display blocks to sun5i.dtsi Hans de Goede
2016-06-08 15:28 ` Peter Korsgaard
2016-06-09 7:46 ` [PATCH 0/1] ARM: dts: sunxi: Fix simplefb not working in 4.7-rc1 Maxime Ripard
2016-06-09 10:47 ` Hans de Goede
2016-06-13 8:01 ` Maxime Ripard
2016-06-13 8:30 ` Hans de Goede
2016-06-20 7:46 ` Maxime Ripard
2016-06-20 20:56 ` Hans de Goede
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=1465063524-4925-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat.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).