All of lore.kernel.org
 help / color / mirror / Atom feed
From: rah@settrans.net (Bob Ham)
To: linux-arm-kernel@lists.infradead.org
Subject: Allwinner A31 framebuffer fails with new CCU clock bindings
Date: Mon, 13 Feb 2017 21:41:37 +0000	[thread overview]
Message-ID: <1487022097.7145.43.camel@settrans.net> (raw)
In-Reply-To: <20170213095207.tsqcigfhyftm5ohk@lukather>

On Mon, 2017-02-13 at 10:52 +0100, Maxime Ripard wrote:
> On Sat, Feb 11, 2017 at 12:08:40PM +0000, Bob Ham wrote:
> > On IRC, MoeIcenowy requested the contents
> > of /sys/kernel/debug/clk/clk_summary.  I don't know how useful it will
> > be but I've put up two versions, one from the bad commit and another
> > from the previous, good commit in the bisect:
> > 
> > http://settrans.net/~rah/misc/sun6i-a31-bad-fb-clk_summary-good.txt
> > http://settrans.net/~rah/misc/sun6i-a31-bad-fb-clk_summary-bad.txt
> 
> Are you sure the good one works? None of the display clocks are
> enabled.

Definitely.  Here's clk_summary from an even earlier kernel from Debian,
4.7.8-1:

http://settrans.net/~rah/misc/sun6i-a31-bad-fb-clk_summary-good-4.7.8-1.txt

And to make super sure, he's a *screenshot* of a terminal in X running
on that kernel, showing every line with "0" in the second column:

http://settrans.net/~rah/misc/sun6i-a31-bad-fb-clk_summary-good-4.7.8-1.png

Does this imply something odd in this hardware or a problem with the
kernel?


> Could you add "clk_ignore_unused" to the kernel boot parameters and
> see if it works?

That does indeed work.  On the same kernel which produced
sun6i-a31-bad-fb-clk_summary-bad.txt, with clk_ignore_unused added to
the boot parameters, the console continues to show output all through
booting and X runs fine.  Here is the clk_summary:

http://settrans.net/~rah/misc/sun6i-a31-bad-fb-clk_summary-clk_ignore_unused.txt

Can I ask what clk_ignore_unused does that might have fixed this?


Thanks,

Bob

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170213/0eb4a29c/attachment.sig>

  reply	other threads:[~2017-02-13 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11 12:08 Allwinner A31 framebuffer fails with new CCU clock bindings Bob Ham
2017-02-13  9:52 ` Maxime Ripard
2017-02-13 21:41   ` Bob Ham [this message]
2017-02-14  2:01     ` [linux-sunxi] " Chen-Yu Tsai

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=1487022097.7145.43.camel@settrans.net \
    --to=rah@settrans.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.