From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: fsl, imx-parallel-display Question
Date: Tue, 02 May 2017 16:15:56 +0200 [thread overview]
Message-ID: <1493734556.13947.26.camel@pengutronix.de> (raw)
In-Reply-To: <CAHCN7xLNgy77ocUM04--11vUBsL198+3_g_ur+Yj8jTtj3SNNQ@mail.gmail.com>
Am Dienstag, den 02.05.2017, 08:55 -0500 schrieb Adam Ford:
> I am trying to use a parallel LCD with an i.MX6Q board using the
> device tree, but I was hoping to do it in the device tree itself
> instead of modifying the "panel-simple" driver that most imx6q devices
> appear to use. I have an omap product with the LCD, and I was hoping
> to just re-use the panel timings, etc.
>
> I found imx6q-tx6q-1010-comtft.dts didn't use "panel-simple", but
> using that as an example doesn't work, for me yet I can get it working
> with "panel-simple"
>
> Looking at the driver for parallel-display.c, I states that "port at 1"
> is the output port which is consistent with most of the boards that
> use "panel-simple" but imx6q-tx6q-1010-comtft.dts does not have this.
> The other thing I noticed is that "panel-simple" devices have an gpio
> enable which I need, but but imx6q-tx6q-1010-comtft.dts does not have
> this either.
>
> Is "panel-simple" the only solution, or is there a way to integrate
> the display info into the device tree and keep the enable-gpios stuff?
Please use the panel-simple option. It's the agreed solution to describe
the panels in DT and is the only option that is acceptable if you ever
try to upstream your DT.
> Is imx6q-tx6q-1010-comtft.dts doing something wrong?
It's using the deprecated way of describing the attached panel, by
putting the timings in the DT. This is not acceptable for new DTs, so
please don't try to replicate this.
Regards,
Lucas
prev parent reply other threads:[~2017-05-02 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 13:55 fsl, imx-parallel-display Question Adam Ford
2017-05-02 14:15 ` Lothar Waßmann
2017-05-02 14:15 ` Lucas Stach [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=1493734556.13947.26.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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 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).