Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp3189967pxb; Tue, 12 Jan 2021 08:26:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJzcETPTmJU7csCvHkF58xtZtu2sC4ilTwy8KGvpIA4zXjCPO2MzXXPNuDAnGCBGdqx57Q26 X-Received: by 2002:a17:906:1a14:: with SMTP id i20mr1442247ejf.548.1610468812224; Tue, 12 Jan 2021 08:26:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610468812; cv=none; d=google.com; s=arc-20160816; b=K2sFOmtoEhpIs+aMOvA+l1r8MBQRj04HVuIiDed8rFO3eZz/++zRHrVKaJD9ddwE0F OMufwraHCS3fYCVn/s9+K4yHbic+Y5p9pGzwHqofuVhjB4KLN7yEIcRlbbMzQajVZ6ut 8ZjvYueq6u2yFl6JlF3prHqX5fIPxOwd0nTIAAjNZxXF4TjzStmN/+P0+hqrKVXeJpxG JeCq9hNMU6bsRRMfPDNEdt7VnhkvLGuSZlGmsG57Bml+D7vcecKDqBY59s1kLYqD1iL7 7jsRfATUmTVs18Qk2vUjwYT1jdCVtA5M6IIImjIM+h0KQF9v33yucesButlj4iCbEyEK 41og== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=23VbNDE04SH4l/Uk1cYBTvy87MnBGqce5HruGxxTxZg=; b=BGY2WmqxwP8yUzfAoQ0oWQW86cQhiGJtR706VsrMi+yPlOikgC1Jz5hGDCiZdDVnKk Lc/Vm17509S7bYy4QUgTE28Xdd409vX5w/2s9qOrOOkwfIri2GYp/5UfaCDTgLEspAA7 BDSz0xzg7jAzfsBU7KoKT4XeIdbi1OEr/SAO1F7Gas7mACZ3GufMjwpcTLqWehcFDWJu 2Lg5Nq66I1BwQY38+Yx/ettWyopv5qXAIHwZ9aeRC5ByJyXvdSOSdSqCztMRijKG1tBs wlEImHxVz9o8dK66rC7nGnoch0fzeqpuTsduG8J0Rff0vu+C2kG2+jDH/ZJr4maqXPJZ hZKA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g4si1555091edn.483.2021.01.12.08.26.28; Tue, 12 Jan 2021 08:26:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=collabora.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406866AbhALQZj (ORCPT + 99 others); Tue, 12 Jan 2021 11:25:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33700 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2406170AbhALQZj (ORCPT ); Tue, 12 Jan 2021 11:25:39 -0500 Received: from bhuna.collabora.co.uk (bhuna.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e3e3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E666DC061794; Tue, 12 Jan 2021 08:24:58 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: sre) with ESMTPSA id 4AFFF1F45463 Received: by earth.universe (Postfix, from userid 1000) id DE9713C0C94; Tue, 12 Jan 2021 17:24:54 +0100 (CET) Date: Tue, 12 Jan 2021 17:24:54 +0100 From: Sebastian Reichel To: Tomi Valkeinen Cc: Sam Ravnborg , linux-fbdev@vger.kernel.org, Bartlomiej Zolnierkiewicz , Tomi Valkeinen , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Laurent Pinchart , kernel@collabora.com Subject: omapfb removal (was: Re: [PATCHv1] video: omapfb2: Make standard and custom DSI command mode panel driver mutually exclusive) Message-ID: <20210112162454.hfzj5bxy7e6zlccl@earth.universe> References: <20210108122540.657501b2@canb.auug.org.au> <20210108112441.14609-1-sebastian.reichel@collabora.com> <20210108195839.GA1429715@ravnborg.org> <20210112120246.ujhjyylrlgfrfvig@earth.universe> <4b39c036-fb70-4a5b-ddda-08ce2f0a6db5@kernel.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ogcdqsrw7fdsgqmh" Content-Disposition: inline In-Reply-To: <4b39c036-fb70-4a5b-ddda-08ce2f0a6db5@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --ogcdqsrw7fdsgqmh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [dropped linux-next from Cc] Hi, On Tue, Jan 12, 2021 at 03:10:56PM +0200, Tomi Valkeinen wrote: > >> But why is it it we need omapfb at all when we have omapdrm? > >=20 > > I think there are two reasons omapfb has not been killed yet. One > > reason was missing support for manually updated DSI panels, which > > have been working since 1 or 2 kernel releases now. The other reason > > is some people using it in combination with an out-of-tree PowerVR > > kernel driver. There is currently work going on to use a more recent > > PowerVR driver based on omapdrm driven by Maemo Leste people. >=20 > omapfb also has a custom sysfs API, so applications that depend on it > would not work anymore. I don't know if there are such applications, thou= gh. >=20 > >> Can we sunset all or some parts of omap support in video/? > >> If not, what is missing to do so. > >=20 > > IDK the exact status of the PowerVR work and have not been using > > omapfb myself for years. I don't think there is a reason to rush > > this, so my suggestion is removing it in 3 steps giving people > > the chance to complain: > >=20 > > 1. Add 'depends on EXPERT' to 'FB_OMAP2' and add deprecation notice > > referencing omapdrm in help text in 5.12 > > 2. Add 'depends on BROKEN' in 5.13 > > 3. Drop drivers/video/fbdev/omap2 afterwards >=20 > I'd love to remove omapfb, but I also fear that there are still people > using it. We can try the above sequence, but it's probably better to go > slower, as people may not be using the latest kernels. I thought about this again and I think the best option is to rename CONFIG_FB_OMAP2 to something like CONFIG_FB_OMAP2_DEPRECATED and update the help text. That way anyone with CONFIG_FB_OMAP2 in their .config will definitely notice the change when upgrading to a newer kernel, but can easily fix it temporarily. Help text could be "This driver will be removed in 2022, please switch to omapdrm." and no other intermediate steps are required that way :) But while looking through CONFIG_FB_OMAP2 references I noticed there is also a V4L2 driver (CONFIG_VIDEO_OMAP2_VOUT), which seems to only work with omapfb. IIUIC that driver provides display overlays to V4L. I guess on omapdrm V4L can use DRM planes instead and no driver is needed (i.e. this driver could just go away with omapfb)? -- Sebastian --ogcdqsrw7fdsgqmh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAl/9zU8ACgkQ2O7X88g7 +pr9vQ//Wurb5B8uHiEeZ7CYL8PnEnfSM/2qv06cU38Yqn0Ci4kZGvcZtyfWaKHn XZ918kT3MzG8Y5qI8VH67fLF8LbUct0mqNm4sKsTdGy72C8Tw4iaQaWkBLWW7yVc Cjti9FbljkYfBI36x1Kj6AMQBAkb0Zfi5vBmCFv0OQs7HnsEO4uD6yeD4b4rXRvl 4mm8naWndQCKD0yP+YDRfENg1guZuOinGIJBBfMpX4hf6WM31zjclLTBoC5hcY7G ZPWjnqFZO0D0gP9opnmfnn3OlQKWO07Cu2CVmD1jikF6eD1KXjMl+eP1vTYdxH/x TFrFEcTnNCPqrm0CILZr3xBEG1qeetAnaf16QcqWHMusZFvNLL+f2ltKnhiQ8CUI JwjnxVADyCg2185R++ByYfDidGDxW+2Fdx1Ylg17XlSObIX0cMxk+O9v6vBz2K9c GAVMWRrE8q+OO5brhPvY9VtqAdyKuGpRrcpFWlVAJK44xo4P0Q8L7+pquANe+PVw wINsAPNHp52AewrnCZjnM8QxpTtq+n4gL6c0UhWFrZdyQLxpfTVfNr0dOfTRn6xs Aj5wvJ6bSe90PH1XvXzOPIWZdY3G92XoY6op2eZHIewEarlimifMrjFRGgXUww2c mjyrTqqhzdRU5UwmtiR4E84Lpdha4nHZ16WgPdZZFDcj/h5FdI0= =mgmT -----END PGP SIGNATURE----- --ogcdqsrw7fdsgqmh--