From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from lelnx193.ext.ti.com ([198.47.27.77]:62396 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752114AbeDYJeR (ORCPT ); Wed, 25 Apr 2018 05:34:17 -0400 Subject: Re: [PATCH 5/7] omapfb: omapfb_dss.h: add stubs to build with COMPILE_TEST && DRM_OMAP To: Laurent Pinchart CC: Mauro Carvalho Chehab , Bartlomiej Zolnierkiewicz , Linux Media Mailing List , Mauro Carvalho Chehab , , References: <20180423170955.13421017@vento.lan> <70b5e60f-346e-4b34-8235-ce62de720a99@ti.com> <1818588.4EAHIaV2gL@avalon> From: Tomi Valkeinen Message-ID: Date: Wed, 25 Apr 2018 12:33:53 +0300 MIME-Version: 1.0 In-Reply-To: <1818588.4EAHIaV2gL@avalon> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org List-ID: On 25/04/18 12:03, Laurent Pinchart wrote: > Could we trim down omapfb to remove support for the devices supported by > omapdrm ? I was thinking about just that. But, of course, it's not quite straightforward either. We've got DSI manual update functionality in OMAP3-OMAP5 SoCs, which covers a lot of devices. And VRFB on OMAP2/3. Those need omapfb. Tomi -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki