From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8C459C352A3 for ; Tue, 11 Feb 2020 16:27:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6B4E620708 for ; Tue, 11 Feb 2020 16:27:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729254AbgBKQ1Y (ORCPT ); Tue, 11 Feb 2020 11:27:24 -0500 Received: from muru.com ([72.249.23.125]:54676 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729133AbgBKQ1Y (ORCPT ); Tue, 11 Feb 2020 11:27:24 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id D85E180D4; Tue, 11 Feb 2020 16:28:06 +0000 (UTC) Date: Tue, 11 Feb 2020 08:27:19 -0800 From: Tony Lindgren To: Tomi Valkeinen Cc: Merlijn Wajer , Laurent Pinchart , Linux-OMAP , dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org, Thierry Reding , Jyri Sarha , Peter Ujfalusi , Aaro Koskinen , Sebastian Reichel Subject: Re: [PATCH 2/3] ARM: dts: am437x-gp/epos-evm: drop unused panel timings Message-ID: <20200211162719.GF64767@atomide.com> References: <20191211165331.GC43123@atomide.com> <45dae8f7-2f5e-6948-5a05-dc8a09ace1fa@ti.com> <20191212203550.GB4892@pendragon.ideasonboard.com> <20200211110712.GB28355@pendragon.ideasonboard.com> <3b4d10c6-7cb2-af53-3a39-31eef441bfdd@ti.com> <98da360f-880b-af56-b285-4d9b39f8a342@wizzup.org> <20200211160524.GE64767@atomide.com> <87b1111e-af06-1e2a-8baa-c3f9a15f1874@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87b1111e-af06-1e2a-8baa-c3f9a15f1874@ti.com> Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org * Tomi Valkeinen [200211 16:14]: > On 11/02/2020 18:05, Tony Lindgren wrote: > > * Merlijn Wajer [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