From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Merlijn Wajer <merlijn@wizzup.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Jyri Sarha <jsarha@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH 2/3] ARM: dts: am437x-gp/epos-evm: drop unused panel timings
Date: Tue, 11 Feb 2020 08:27:19 -0800 [thread overview]
Message-ID: <20200211162719.GF64767@atomide.com> (raw)
In-Reply-To: <87b1111e-af06-1e2a-8baa-c3f9a15f1874@ti.com>
* Tomi Valkeinen <tomi.valkeinen@ti.com> [200211 16:14]:
> On 11/02/2020 18:05, Tony Lindgren wrote:
> > * Merlijn Wajer <merlijn@wizzup.org> [200211 12:54]:
> > > Hi,
> > >
> > > On 11/02/2020 12:08, Tomi Valkeinen wrote:
> > > > On 11/02/2020 13:07, Laurent Pinchart wrote:
> > > >
> > > > > > Hopefully soon (in five years? =) we can say that omapdrm supports all
> > > > > > the boards, and we can deprecate omapfb.
> > > > >
> > > > > I'd love to send a patch to remove omapfb, but I'll let you do the
> > > > > honours :-)
> > > >
> > > > Not before we add DSI support to omapdrm...
> >
> > Hmm do your mean RFBI? The DSI support we already have :)
>
> Oh, I didn't even remember RFBI... But it is not supported in omapfb either,
> so it's not blocking removal of omapfb.
Oh OK.
> We are still missing DSI command mode support, and moving it to the common DRM model.
Nope, DSI command mode support has been working just fine for
a while now :) And Sebastian has a WIP git tree of the common DRM
model changes for it. I don't think we have devices with DSI
command mode working for omapfb but not for omapdrm?
What got missed for v5.6-rc1 is the LCD backlight patch though,
I think the only issue there is default-brightness vs more common
default-brightness-value usage if you have any input to that.
> > > This is probably known, but for devices that would like use PowerVR SGX,
> > > there sometimes is only userspace available that works with omap(l)fb,
> > > and not with DRM. The Nokia N900 is such an example.
> > >
> > > There might be a newer release of (closed) userspace coming for the
> > > aging device(s), but as it stands, I don't think it's possible to do 3D
> > > with PowerVR SGX on omapdrm currently.
> > >
> > > But I might be wrong...
> >
> > Yes SGX is a bottleneck currently for omap3 users. And I think
> > RFBI is blocking n8x0 from moving to omapdrm and finally leaving
> > drivers/video/fbdev/omap2 behind.
> >
> > With those blockers fixed, I'd also be happy to just get rid of
> > drivers/video/fbdev/omap2 as there should be no reason to
> > keep using it.
>
> I don't know what to do about SGX, but if someone sends patches to omapdrm
> to allow using SGX, I'll review =).
OK so then the only blocker seems to be the lack of SGX blobs
for omap3 devices which seems to be in process of getting fixed.
Regards,
Tony
next prev parent reply other threads:[~2020-02-11 16:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 9:39 [PATCH 0/3] drm/omap: fix am4 evm lcd Tomi Valkeinen
2019-11-14 9:39 ` [PATCH 1/3] ARM: dts: am437x-gp/epos-evm: fix panel compatible Tomi Valkeinen
2019-12-02 13:01 ` Laurent Pinchart
2019-12-11 16:51 ` Tony Lindgren
2019-11-14 9:39 ` [PATCH 2/3] ARM: dts: am437x-gp/epos-evm: drop unused panel timings Tomi Valkeinen
2019-12-02 13:04 ` Laurent Pinchart
2019-12-11 16:53 ` Tony Lindgren
2019-12-12 9:37 ` Tomi Valkeinen
2019-12-12 20:35 ` Laurent Pinchart
2020-01-13 12:01 ` Tomi Valkeinen
2020-02-11 10:01 ` Tomi Valkeinen
2020-02-11 11:07 ` Laurent Pinchart
2020-02-11 11:08 ` Tomi Valkeinen
2020-02-11 11:10 ` Laurent Pinchart
2020-02-14 0:33 ` Sebastian Reichel
2020-02-11 12:54 ` Merlijn Wajer
2020-02-11 16:05 ` Tony Lindgren
2020-02-11 16:13 ` Tomi Valkeinen
2020-02-11 16:27 ` Tony Lindgren [this message]
2020-02-11 17:22 ` Tomi Valkeinen
2020-02-13 21:57 ` Sebastian Reichel
2019-11-14 9:39 ` [PATCH 3/3] drm/panel: simple: fix osd070t1718_19ts sync drive edge Tomi Valkeinen
2019-12-02 13:07 ` Laurent Pinchart
2020-01-13 12:04 ` Tomi Valkeinen
2020-02-10 8:15 ` Tomi Valkeinen
2020-02-14 21:39 ` Sam Ravnborg
2020-02-21 10:43 ` Tomi Valkeinen
2020-02-22 12:16 ` Sam Ravnborg
2019-11-27 12:59 ` [PATCH 0/3] drm/omap: fix am4 evm lcd Tomi Valkeinen
2019-11-27 15:45 ` Tony Lindgren
2019-11-28 7:03 ` Tomi Valkeinen
2019-12-02 13:13 ` Laurent Pinchart
2019-12-02 13:24 ` Adam Ford
2019-12-03 21:27 ` Laurent Pinchart
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=20200211162719.GF64767@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=peter.ujfalusi@ti.com \
--cc=sre@kernel.org \
--cc=thierry.reding@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 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).