From: Lubomir Rintel <lkundrak@v3.sk>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] drm/panel: Add support for Innolux LS075AT011
Date: Wed, 19 Aug 2020 12:12:04 +0200 [thread overview]
Message-ID: <20200819101206.633253-1-lkundrak@v3.sk> (raw)
Hi,
Please take a look at the patches chanied to this message and consider
applying them. They add description of the display panel found on OLPC
laptops to the simple panel driver.
There is no datasheet for the hardware and thus the timings were
determined on a best effort basis. The clock range is gotten from the
data sheet of the display controller [1] and the other timings are what
OLPC laptops actually use. The panel seems to cope with different sync
timings, but I'm not sure wherher there's any value in attempting to
figure out what range is actually permissible.
I could not figure out the right definitions for the connector and the
bus format. I'm not sure how necessary they are, but at least the
drm-panel driver insists on connector type being defined so I picked
LVDS because that seems to be used for internal laptop screens.
The signalling is not actually differential. It uses TTL levels with
data sampled on rising and falling clock edges; sort of like this (taken
from [1], P.20):
__
FSTH / \_______________________________________
____ ____ ____ ____ __
FCLK / \____/ \____/ \____/ \____/
____ ____ ____ ____ ____ ____ ____
FD00 ........X____X____X____X____X____X____X____
____ ____ ____ ____ ____ ____ ____
FD01 ........X____X____X____X____X____X____X____
____ ____ ____ ____ ____ ____ ____
FD10 ........X____X____X____X____X____X____X____
____ ____ ____ ____ ____ ____ ____
FD11 ........X____X____X____X____X____X____X____
____ ____ ____ ____ ____ ____ ____
FD20 ........X____X____X____X____X____X____X____
____ ____ ____ ____ ____ ____ ____
FD21 ........X____X____X____X____X____X____X____
| | | |
data 1 data 2 ...
(2x6bit) (2x6bit)
I believe the data just carries brightness because each pixel on the
panel has a fixed color; with the red, green and blue pixels organized
in a pattern [2]. (The HX8837 that drives the color does the conversion
from RGB).
Tested on an OLPC XO-1.75 laptop. XO-1 and XO-1.5 use the same hardware,
but their display controllers are not supported by DRM at the moment.
[1] http://wiki.laptop.org/images/0/09/DCON_datasheet_HX8837-A.pdf
[2] http://wiki.laptop.org/go/Display
Thank you!
Lubo
next reply other threads:[~2020-08-19 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 10:12 Lubomir Rintel [this message]
2020-08-19 10:12 ` [PATCH 1/2] dt-bindings: display: simple: add Innolux LS075AT011 Lubomir Rintel
2020-08-25 21:53 ` Rob Herring
2020-08-19 10:12 ` [PATCH 2/2] drm/panel: simple: Add support for " Lubomir Rintel
2020-10-17 8:07 ` Sam Ravnborg
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=20200819101206.633253-1-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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).