From: Tony Lindgren <tony@atomide.com>
To: Joachim Eastwood <manabian@gmail.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>, linux-omap@vger.kernel.org
Subject: Re: OMAPDSS and panel-dpi
Date: Thu, 17 Apr 2014 12:22:16 -0700 [thread overview]
Message-ID: <20140417192215.GA24931@atomide.com> (raw)
In-Reply-To: <CAGhQ9VzL5fLHCNZ=y-exBAds03f8Bw_hO+KjYnwO4MgRWOfpuw@mail.gmail.com>
* Joachim Eastwood <manabian@gmail.com> [140417 11:05]:
> Hi Tomi,
>
> My VAR-DVK-OM44 (OMAP4460) has both a HDMI and a LCD panel. As HDMI is
> now working (thanks) I also taken a look at panel-dpi.
>
> I found the DT patch for panel-dpi on the mailing list.
> OMAPDSS: panel-dpi: Add DT support:
> http://marc.info/?l=devicetree&m=139030201815380&w=2
>
> And I got my display working with DT :)
> So you add can my: Tested-by: Joachim Eastwood <manabian@gmail.com>
>
> Could you upstream the panel-dpi DT support and the HDMI connector
> gpio hpd patch in 3.16?
> I hope it's easier to upstream the stuff when it gets some users in DT.
Good to hear. The DPI panel support should use gpio-backlight
driver as discussed in the DPI thread. Did you have to patch
anything for the timings etc?
If you have the board working, care to take a look at making
the gpio-backlight change?
Otherwise we'll be creating unncessary churn and maintainer
headaches with patching half a dozen DPI using boards to change
them over to use gpio-backlight.
Regards,
Tony
next prev parent reply other threads:[~2014-04-17 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 18:04 OMAPDSS and panel-dpi Joachim Eastwood
2014-04-17 19:22 ` Tony Lindgren [this message]
2014-04-17 20:51 ` Joachim Eastwood
2014-04-17 22:50 ` Tony Lindgren
2014-04-18 2:50 ` Tony Lindgren
2014-04-18 11:05 ` Joachim Eastwood
2014-04-18 15:40 ` Tony Lindgren
2014-04-18 16:43 ` Joachim Eastwood
2014-04-22 13:28 ` Tomi Valkeinen
2014-04-22 13:15 ` 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=20140417192215.GA24931@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.