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=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 13916C47095 for ; Wed, 9 Jun 2021 09:30:23 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 85BDA6124C for ; Wed, 9 Jun 2021 09:30:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 85BDA6124C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=arndb.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 03F046E15D; Wed, 9 Jun 2021 09:30:22 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.134]) by gabe.freedesktop.org (Postfix) with ESMTPS id A51516E15D for ; Wed, 9 Jun 2021 09:30:19 +0000 (UTC) Received: from mail-wr1-f51.google.com ([209.85.221.51]) by mrelayeu.kundenserver.de (mreue011 [213.165.67.97]) with ESMTPSA (Nemesis) id 1MnJUy-1lRVwD33mG-00jLTx for ; Wed, 09 Jun 2021 11:30:17 +0200 Received: by mail-wr1-f51.google.com with SMTP id z8so24640706wrp.12 for ; Wed, 09 Jun 2021 02:30:17 -0700 (PDT) X-Gm-Message-State: AOAM532TEaYw+GA3FlNHBWJP92A/31803XoNGGnKsst6APCKZNTkaRjM ekYGK5LCzsm9C9agIjnD39bX+gnxOypKDqAWAac= X-Google-Smtp-Source: ABdhPJzSUnfxZ8LwqKlwrv2bklC04HJaA0aceSDDVOkdulM4vUlC4C4l0QpvA5YJj63Bv3ttsWTULoaeeZe1hMG9qiE= X-Received: by 2002:a5d:4050:: with SMTP id w16mr27202710wrp.99.1623231017160; Wed, 09 Jun 2021 02:30:17 -0700 (PDT) MIME-Version: 1.0 References: <20210608103833.598348-1-joel@jms.id.au> <3877ae18-dbda-242a-60b2-f73734f8ba03@xs4all.nl> In-Reply-To: <3877ae18-dbda-242a-60b2-f73734f8ba03@xs4all.nl> From: Arnd Bergmann Date: Wed, 9 Jun 2021 11:28:24 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] ARM: config: Refresh mutli v7 To: Hans Verkuil Content-Type: text/plain; charset="UTF-8" X-Provags-ID: V03:K1:EAc9wdmHgB18R6QJ9SdX9qrsIfdpkFry+Xdr57z51EzSA5hA9Yk Qqm6AUaxsIxxGDWanDUtmwF4NI8oVTimrNInPexgrg6gDZe1RJG+cvGQ09YuUzSaoIY3rc9 43FWu5TqPnmFb9WC9aj21MeTTp70M2dyZyrICxjUUv0LXfusauvdbUAvOsDKbXqrVye0vHf TefC8GCYPN6+52hHhbVAw== X-UI-Out-Filterresults: notjunk:1;V03:K0:gMq/S8QxKe8=:c8Q4qDJjbckW/3s8zIpdrg 4DQgCk6C4VxvOYMOvq4KaVLtSVPhTn9KQonD/e7TMEduqN4DiuEkNblZg/uz7NCwiqxIbjhUA 3drO18QRLLq28/Yq53XF5Oa+6qCfJuivGvMzgL5Z6OlB0BXONYUiAiPBP4FR3Sk+C5ilcFhmm +vY2sVhMLy1SNYo+gxTo6bdqVuYHryC2PCf8JfAv/RWA4BPH7crabiJHXT7nM+4g5oICoXVZ5 qNHW1BSpan5chQ2Wb8q/YZeShdeUAO9X70sK2g4p4hzImyE8TTSBQ3YeYM5egqCYaQBMBhIjk qvLJZY9R7twVZGG+1UO/neXMQQARHLkfJ74RBdLkZKkky77RnMw38gG5IXX86t2VpNh8PwAPH 5wzUQ2O+gisbnTmzlwCrv/u8p1qRmfKOWcI8EMUTTUOmfxL5J+2wEaNBHdmkZJULk5UwHobFX rt4X2y0NOjD6dZMW7sB/aAiPpEmZrDieJlAAmdMayV4nOpZrV9NAAqrroTL7AOwrrZu0mrZfd pPghQqVvIZqaBRkPrrGRK4= X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: dri-devel , Linux Fbdev development list , Joel Stanley , Linux ARM Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Tue, Jun 8, 2021 at 6:49 PM Hans Verkuil wrote: > On 08/06/2021 18:14, Arnd Bergmann wrote: > > Right now it is inherent to the driver. It is probably possible to drop support > for video overlay devices if CONFIG_FB=n, but it is not something I have time > for. It's just a test driver (albeit a very useful test driver), so it is no > big deal if it is disabled when CONFIG_FB=n. Ok, thanks for the reply, makes sense. I checked what other consequences there are if we disable CONFIG_FB and CONFIG_DRM_KMS_FB_HELPER=y in all the defconfigs now, as the patch from Kees did. It appears that the only other arm32 framebuffers that remain are FB_EFI=y, FB_WM8505=y, FB_MX3=m and FB_SIMPLE=y. On arm64, losing CONFIG_FB=y would disable FB_EFI=y, XEN_FBDEV_FRONTEND=y, and FB_MX3=m On x86, it's only CONFIG_FB_EFI It appears that FB_MX3 is orphaned since commit e1324ece2af4 ("ARM: imx: Remove i.MX35 board files") because all Armv6 or newer i.MX now use drivers/gpu/drm/mxsfb/mxsfb_drv.c, and FB_WM8505 is probably unused as well (we discussed removing the platform last winter, but decided to give it another year to see if new users come up, which has not happened). As long as simplefb, efifb and xenfb are needed though, we probably want CONFIG_FB=y anyway and leaving VIVID=m with the dependency does not cause problems until those are all turned into drm drivers. Arnd