linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: OMAP3: DSS questions
Date: Mon, 09 Jan 2017 08:17:07 +0000	[thread overview]
Message-ID: <94ec010a-b8e7-0d65-3bb3-ae39fbcee14d@ti.com> (raw)
In-Reply-To: <CAGm1_ktY3djv8yp3e+w-DmtFa_9HmEkXn-d1e4AKsPGnES_Rrw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1118 bytes --]


On 05/01/17 18:49, Tony Lindgren wrote:
> * Yegor Yefremov <yegorslists@googlemail.com> [170104 08:27]:
>> 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"?

acb was only for passive matrix panels, which have never even been
supported. So you can just ignore acb.

>> 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?

Depends. If you somehow rely on the custom ioctls from omapfb, then it
might be easiest to use that. However, it's no longer developed, so I
suggest at least trying to use omapdrm first.

>> 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?

With the endpoint's data-lines property. See, for example,
am437x-gp-evm.dts.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2017-01-09  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 16:25 OMAP3: DSS questions Yegor Yefremov
2017-01-05 16:49 ` Tony Lindgren
2017-01-09  8:17 ` Tomi Valkeinen [this message]

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=94ec010a-b8e7-0d65-3bb3-ae39fbcee14d@ti.com \
    --to=tomi.valkeinen@ti.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).