From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Kever Yang <kever.yang@rock-chips.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Cc: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
LKML <linux-kernel@vger.kernel.org>,
Jagan Teki <jagan@amarulasolutions.com>
Subject: siimple-framebuffer rockchip persistent logo
Date: Sun, 12 Jan 2020 18:16:30 +0100 [thread overview]
Message-ID: <CAOf5uwmPMRq4v9=5-Z=XLH7hATC-AhXQWthfy_uvYTXSo6V+CA@mail.gmail.com> (raw)
Hi Kever
Trying to have a persistent banner from uboot to linux-kernel. I'm
right now working on linux-rockchip kernel but I think that the
problem is even on mainline
+ framebuffer: framebuffer@7f800000 {
+ compatible = "rockchip,simple-framebuffer",
+ "simple-framebuffer";
+ reg = <0x7f800000 (1920 * 1080 * 4)>;
+ width = <1920>;
+ height = <1080>;
+ stride = <(1920 * 4)>;
+ format = "a8b8g8r8";
+ clocks = <&cru PCLK_HDMI_CTRL>, <&cru SCLK_HDMI_HDCP>,
+ <&cru SRST_LCDC0_AXI>, <&cru
SRST_LCDC0_AHB>, <&cru SRST_LCDC0_DCLK>,
+ <&cru ACLK_VOP0>, <&cru HCLK_VOP0>;
+ status = "okay";
+ };
Seems that it get off before I reach the drm registration
[ 2.077495] simple-framebuffer 7f800000.framebuffer: framebuffer at
0x7f800000, 0x7e9000 bytes, mapped to 0xf0900000
[ 2.077519] simple-framebuffer 7f800000.framebuffer:
format=a8b8g8r8, mode=1920x1080x32, linelength=7680
[ 2.161225] simple-framebuffer 7f800000.framebuffer: fb0: simplefb
registered!
[ 3.433847] fb: switching to rockchip-drm-fb from simple
I don't find all the clocks and if those are the only think that I
need to stay on. Any suggestion?
Michael
next reply other threads:[~2020-01-12 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 17:16 Michael Nazzareno Trimarchi [this message]
2020-02-07 19:14 ` siimple-framebuffer rockchip persistent logo Michael Nazzareno Trimarchi
2020-02-12 11:49 ` Michael Nazzareno Trimarchi
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='CAOf5uwmPMRq4v9=5-Z=XLH7hATC-AhXQWthfy_uvYTXSo6V+CA@mail.gmail.com' \
--to=michael@amarulasolutions.com \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=philipp.tomsich@theobroma-systems.com \
/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).