From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org, dri-devel@lists.freedesktop.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: OMAPDSS: panel-sharp-ls037v7dw01: update to use gpiod
Date: Thu, 14 Jan 2016 08:45:16 -0800 [thread overview]
Message-ID: <20160114164516.GM12777@atomide.com> (raw)
In-Reply-To: <569751E5.40204@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [160113 23:45]:
> On 14/01/16 01:22, Tony Lindgren wrote:
> > Tomi, do we really need two copies of the the same panels
> > files in kernel?
> >
> > For example:
> >
> > $ find . -name panel-sharp-ls037v7dw01.c
> > ./drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c
> > ./drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c
>
> Strictly no, but I think this is the best way forward. Longer story:
> http://comments.gmane.org/gmane.comp.video.dri.devel/143151
OK. Something that may help is to move the panels to live under
their control bus (i2c, spi) where they probe and just register
with omapdrm or omapfb.
> > Seems like we can just remove the check for -ENOENT here.
>
> Yep. Writing a patch for this and the other panel-sharp-ls037v7dw01
> error Dan reported is on my todo.
OK thanks,
Tony
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-01-14 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151224072926.GE29642@mwanda>
2016-01-13 23:22 ` OMAPDSS: panel-sharp-ls037v7dw01: update to use gpiod Tony Lindgren
2016-01-14 7:44 ` Tomi Valkeinen
2016-01-14 16:45 ` Tony Lindgren [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=20160114164516.GM12777@atomide.com \
--to=tony@atomide.com \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
--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 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).