From: Yegor Yefremov <yegorslists@googlemail.com>
To: linux-fbdev@vger.kernel.org
Subject: OMAP3: DSS questions
Date: Wed, 04 Jan 2017 16:25:30 +0000 [thread overview]
Message-ID: <CAGm1_ktY3djv8yp3e+w-DmtFa_9HmEkXn-d1e4AKsPGnES_Rrw@mail.gmail.com> (raw)
I'm trying to get my am3517 board working with 4.10 (porting from
2.6.37). An LCD screen is attached to OMAP DSS using 24 bits. Display
config looks like this in [1].
What DTS options reflectes ".acb = 0x0"?
Btw. I just need a frame buffer device and will use it with Embedded
Qt. Should I nevertheless use DRM flavor as it already provides frame
buffer driver?
drivers/gpu/drm/omapdrm/displays/panel-dpi.c performs either platform
or OF initialization. Platform flavor contains data_lines info, OF -
not. As I'm using OF flavor, how do I get proper data_lines info?
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id™2ee64af66f05e16aa70b475f9ad3047f801185
Yegor
next reply other threads:[~2017-01-04 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 16:25 Yegor Yefremov [this message]
2017-01-05 16:49 ` OMAP3: DSS questions Tony Lindgren
2017-01-09 8:17 ` Tomi Valkeinen
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=CAGm1_ktY3djv8yp3e+w-DmtFa_9HmEkXn-d1e4AKsPGnES_Rrw@mail.gmail.com \
--to=yegorslists@googlemail.com \
--cc=linux-fbdev@vger.kernel.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).