Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3296134pxj; Mon, 24 May 2021 03:28:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJynnwPaijZ7N9rdRDmfCt47KzO9sgPBUzAB8OR2M10vlo1nJlZVLd/AKopORws1B0vrySIn X-Received: by 2002:a17:906:5617:: with SMTP id f23mr21708346ejq.298.1621852097493; Mon, 24 May 2021 03:28:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621852097; cv=none; d=google.com; s=arc-20160816; b=fgVcfT4IASluGtcllZmKUmEU5UlLomK/mQY8jgQJNyiPrMX8M7mJm5TaZgPKms4K8o rYTwtXeg2Pjru0ZaMu+2jQ+I1HeThAmyxUHK5+Qy1Ck8WxIxXqwGBRSpxYcv3gtD6bfy fM+6RsGUnZzSsTXKRMFxxqDAEL7nD0+/LZozwnMKBLghDlviBSktcxbhLloBSuV5Bmm8 cSKa1QPI8nrgvlqXUgXhGthz4Bh7KqtuEldBQMm0CVEsV94r1wn6YzJfjQtMDVPQHYoX LOP1UFPxgQkUjLmBfxUuS8K/PUbOo58FUCeb1vmjTeEhEpVacqz7xEmnJfw0zX0fPGsL N/vQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=TYogtjy3pt5sf1a9SSZl8mSfe+jGtxLlx+TZLBzsGBc=; b=URrz9XwYvD/Jzpz2tg4NBX1xgzjLM5yryVtuZgMs0x3nFdpwg0nvBxPaYgLRRSanIC 8l6shZtROBmH4IhwVyguqhF14U5BHiult9KW4qHhl0Aqqp/H6QMNZZ9Y1AXPiSHu7nEG JeyXTQvKCBKHItVV0KqOYKcNklEcER9GbYimKzkXUsKYBx1YGmaN8CNnC14+XeKhmgOb lfJZRkZP7B6kYOy6ZMunqCZIX0gpgS6G1za3ED61kAbVQd02Oq8oJcyoF2Ejny6QiJUQ GSpJl9pNVDuYhS0H5hOPH0eXqOhGVLDRULvekzaroJScr3L4flzWdBQWmpLGkPYIuYvt anoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=pK5GXFlN; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gt38si11769271ejc.742.2021.05.24.03.27.54; Mon, 24 May 2021 03:28:17 -0700 (PDT) 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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=pK5GXFlN; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232599AbhEXK0P (ORCPT + 99 others); Mon, 24 May 2021 06:26:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:46612 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232422AbhEXK0M (ORCPT ); Mon, 24 May 2021 06:26:12 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 49374611CE; Mon, 24 May 2021 10:24:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1621851884; bh=5wBiRHHSXJ69cFUjecB+aszzqhwYw/MhJXDMzSU3aiY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=pK5GXFlN+YCuMLzRkryTFyUpVJAEwnP0vbi3xwjP6jH9zyZMvzC+0XT1/9n95bQrX 77LPElvDmRwpEyjQ+Vt2rM4mAftSlCmR3oAMqfvsLQcddtFOpEfI+5OzLlommq+unm c1z9WKpYVrqqyRfaU1taNHEmXE5BpBfWetH1DWWfEW/q/4tSC9ActrMFlHWvRG91xV Iqt+xObwQDaIb1/6PpcojSSUO5P/HgU3bRs4B/TiDYp2fpqk0zZEpP1wralYzG9VK/ 2jMz7BaHTQs3BvgixAc5+Jfiil5oTbuXt0An5RS7g5NDy1QAwgsgxn7CU3wRk9FYs+ Fyx6wyS0qENIw== Received: by mail-oo1-f48.google.com with SMTP id o14-20020a4a384e0000b029020ec48a2358so4146751oof.13; Mon, 24 May 2021 03:24:44 -0700 (PDT) X-Gm-Message-State: AOAM5305CscHqLDZLWklxsk/nRuxHxWqyccw+83WwnJVcMwnDKLYne6s Dobmb6w1TN0g+WOFIXBWEcMUuanYVKFf1MRQN9s= X-Received: by 2002:a4a:b202:: with SMTP id d2mr17739259ooo.13.1621851883493; Mon, 24 May 2021 03:24:43 -0700 (PDT) MIME-Version: 1.0 References: <20210521192907.3040644-1-javierm@redhat.com> In-Reply-To: <20210521192907.3040644-1-javierm@redhat.com> From: Ard Biesheuvel Date: Mon, 24 May 2021 12:24:32 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 0/2] allow the sysfb support to be used in non-x86 arches To: Javier Martinez Canillas Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Daniel Vetter , Peter Robinson , Thomas Zimmermann , David Airlie , Hans de Goede , Albert Ou , Borislav Petkov , Catalin Marinas , "H. Peter Anvin" , Ingo Molnar , Palmer Dabbelt , Paul Walmsley , Russell King , Thomas Gleixner , Will Deacon , linux-arm-kernel@lists.infradead.org, linux-efi@vger.kernel.org, linux-riscv@lists.infradead.org, x86@kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Javier, On Fri, 21 May 2021 at 21:29, Javier Martinez Canillas wrote: > > The x86 architecture platform has a Generic System Framebuffers (sysfb) > support, that register a system frambuffer platform devices. It either > registers a "simple-framebuffer" for the simple{fb,drm} drivers or legacy > VGA/EFI FB devices for the vgafb/efifb drivers. > > Besides this, the EFI initialization code used by other architectures such > as aarch64 and riscv, has similar logic but only register an EFI FB device. > > The sysfb is generic enough to be reused by other architectures and can be > moved out of the arch/x86 directory to drivers/firmware, allowing the EFI > logic used by non-x86 architectures to be folded into sysfb as well. > > Patch #1 in this series do the former while patch #2 the latter. This has > been tested on x86_64 and aarch64 machines using the efifb, simplefb and > simpledrm drivers. But more testing will be highly appreciated, to make > sure that no regressions are being introduced by these changes. > > Since this touches both arch/{x86,arm,arm64,riscv} and drivers/firmware, I > don't know how it should be merged. But I didn't find a way to split these. > We could merge this via the EFI tree without too much risk of conflicts, I think. However, I'd like to see a better explanation of why this is an improvement. The diffstat does not show a huge net win, and it does not enable anything we didn't already have before, right? > > Javier Martinez Canillas (2): > drivers/firmware: move x86 Generic System Framebuffers support > drivers/firmware: consolidate EFI framebuffer setup for all arches > > arch/arm/Kconfig | 1 + > arch/arm/include/asm/efi.h | 5 +- > arch/arm64/Kconfig | 1 + > arch/arm64/include/asm/efi.h | 5 +- > arch/riscv/Kconfig | 1 + > arch/riscv/include/asm/efi.h | 5 +- > arch/x86/Kconfig | 27 +----- > arch/x86/kernel/Makefile | 3 - > drivers/firmware/Kconfig | 30 +++++++ > drivers/firmware/Makefile | 2 + > drivers/firmware/efi/Makefile | 2 + > drivers/firmware/efi/efi-init.c | 90 ------------------- > .../firmware/efi}/sysfb_efi.c | 79 +++++++++++++++- > {arch/x86/kernel => drivers/firmware}/sysfb.c | 42 +++++---- > .../firmware}/sysfb_simplefb.c | 31 ++++--- > .../x86/include/asm => include/linux}/sysfb.h | 34 +++---- > 16 files changed, 182 insertions(+), 176 deletions(-) > rename {arch/x86/kernel => drivers/firmware/efi}/sysfb_efi.c (84%) > rename {arch/x86/kernel => drivers/firmware}/sysfb.c (70%) > rename {arch/x86/kernel => drivers/firmware}/sysfb_simplefb.c (82%) > rename {arch/x86/include/asm => include/linux}/sysfb.h (68%) > > -- > 2.31.1 >