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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B281EC433F5 for ; Tue, 19 Apr 2022 13:30:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243957AbiDSNdJ (ORCPT ); Tue, 19 Apr 2022 09:33:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243950AbiDSNdI (ORCPT ); Tue, 19 Apr 2022 09:33:08 -0400 Received: from mail-oi1-f182.google.com (mail-oi1-f182.google.com [209.85.167.182]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3AA1B644D; Tue, 19 Apr 2022 06:30:26 -0700 (PDT) Received: by mail-oi1-f182.google.com with SMTP id q129so18094920oif.4; Tue, 19 Apr 2022 06:30:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=dC+9aknP1RLhEpg+1+Hw55vZvp/iuvE//q1Eib/rSk8=; b=vmVG8Cqxn4GufyT0NtNX/I9k44Vh1qMOeeg+6wHWDktZbKWan97MwiPo/4wV6IeR2C DdTL2FpuuNYhDOpG8n+FNvAygolMSln9GwFjq8c45reVt8k7gbvzX8CG+1RfyNSvnhP+ 4j/zm/xM5dGdQOSA/0V66ODBYHNcLhFdIRJ1onXaEuCDhP3cFKN9wEnkezjvUg1V/83F UV355ngXHAQXg7KzSWSEar77gEcrQ3J6Iqz4y2glL6OMx4dSk6tXlOfz1Xz6fq7kRU/4 N6O82g/VC1+NjVChKxwLiCCImXhIa5VfonHBAshEk+3qQINb+EPdhMBQUk1jAmQdqNFr LYUA== X-Gm-Message-State: AOAM532SnLFsi+Gc8+S1PpI19vnj4D8qV288bRfK5mBDQ3NncSpNaTL3 jz87DjqXDk/Zt1UGycSkpg== X-Google-Smtp-Source: ABdhPJz3NesdMOUrwAzr/eSC8Mx3RfAIAeIJyoJkAIHJpN1mFId4zSJtG69YtVQ1IuW9xS8FsHja1w== X-Received: by 2002:aca:1903:0:b0:322:68f1:79ca with SMTP id l3-20020aca1903000000b0032268f179camr6634474oii.189.1650375025388; Tue, 19 Apr 2022 06:30:25 -0700 (PDT) Received: from robh.at.kernel.org (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id k8-20020a544688000000b002f90678740esm5102226oic.37.2022.04.19.06.30.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 Apr 2022 06:30:24 -0700 (PDT) Received: (nullmailer pid 2377875 invoked by uid 1000); Tue, 19 Apr 2022 13:30:23 -0000 Date: Tue, 19 Apr 2022 08:30:23 -0500 From: Rob Herring To: Thomas Zimmermann Cc: frowand.list@gmail.com, daniel@ffwll.ch, deller@gmx.de, sam@ravnborg.org, linux@roeck-us.net, mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org, javierm@redhat.com, devicetree@vger.kernel.org, linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH v2 1/2] of: Create platform devices for OF framebuffers Message-ID: References: <20220419100405.12600-1-tzimmermann@suse.de> <20220419100405.12600-2-tzimmermann@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220419100405.12600-2-tzimmermann@suse.de> Precedence: bulk List-ID: X-Mailing-List: linux-fbdev@vger.kernel.org On Tue, Apr 19, 2022 at 12:04:04PM +0200, Thomas Zimmermann wrote: > Create a platform device for each OF-declared framebuffer and have > offb bind to these devices. Allows for real hot-unplugging and other > drivers besides offb. > > Originally, offb created framebuffer devices while initializing its > module by parsing the OF device tree. No actual Linux device was set > up. This tied OF framebuffers to offb and makes writing other drivers > for the OF framebuffers complicated. The absence of a Linux device > further prevented real hot-unplugging. Adding a distinct platform > device for each OF framebuffer solves both problems. Specifically, a > DRM driver can now provide graphics output for modern userspace. > > Some of the offb init code is now located in the OF initialization. > There's now also an implementation of of_platform_default_populate_init(), > which was missing before. The OF side creates different devices for > either OF display nodes or BootX displays as they require different > handling by the driver. The offb drivers picks up each type of device > and runs the appropriate fbdev initialization. > > Tested with OF display nodes on qemu's ppc64le target. > > v2: > * run PPC code as part of existing initialization (Rob) > * add a few more error warnings (Javier) > > Signed-off-by: Thomas Zimmermann > Reviewed-by: Javier Martinez Canillas > --- > drivers/of/platform.c | 88 ++++++++++++++++++++++++++-------- > drivers/video/fbdev/offb.c | 98 +++++++++++++++++++++++++------------- > 2 files changed, 132 insertions(+), 54 deletions(-) > > diff --git a/drivers/of/platform.c b/drivers/of/platform.c > index a16b74f32aa9..738ba2e2838c 100644 > --- a/drivers/of/platform.c > +++ b/drivers/of/platform.c > @@ -507,7 +507,6 @@ int of_platform_default_populate(struct device_node *root, > } > EXPORT_SYMBOL_GPL(of_platform_default_populate); > > -#ifndef CONFIG_PPC > static const struct of_device_id reserved_mem_matches[] = { > { .compatible = "qcom,rmtfs-mem" }, > { .compatible = "qcom,cmd-db" }, > @@ -520,33 +519,81 @@ static const struct of_device_id reserved_mem_matches[] = { > > static int __init of_platform_default_populate_init(void) > { > - struct device_node *node; > - As both if/else clauses need 'node', I'd keep this declared here. > device_links_supplier_sync_state_pause(); > > if (!of_have_populated_dt()) > return -ENODEV; > > - /* > - * Handle certain compatibles explicitly, since we don't want to create > - * platform_devices for every node in /reserved-memory with a > - * "compatible", > - */ > - for_each_matching_node(node, reserved_mem_matches) > - of_platform_device_create(node, NULL, NULL); > + if (IS_ENABLED(CONFIG_PPC)) { > + struct device_node *boot_display = NULL; > + struct device_node *node; > + struct platform_device *dev; > + int ret; > + > + /* Check if we have a MacOS display without a node spec */ > + if (of_get_property(of_chosen, "linux,bootx-noscreen", NULL)) { > + /* > + * The old code tried to work out which node was the MacOS > + * display based on the address. I'm dropping that since the > + * lack of a node spec only happens with old BootX versions > + * (users can update) and with this code, they'll still get > + * a display (just not the palette hacks). > + */ > + dev = platform_device_alloc("bootx-noscreen", 0); > + if (WARN_ON(!dev)) > + return -ENOMEM; > + ret = platform_device_add(dev); > + if (WARN_ON(ret)) { > + platform_device_put(dev); > + return ret; > + } > + } > > - node = of_find_node_by_path("/firmware"); > - if (node) { > - of_platform_populate(node, NULL, NULL, NULL); > - of_node_put(node); > - } > + /* > + * For OF framebuffers, first create the device for the boot display, > + * then for the other framebuffers. Only fail for the boot display; > + * ignore errors for the rest. > + */ > + for_each_node_by_type(node, "display") { > + if (!of_get_property(node, "linux,opened", NULL) || > + !of_get_property(node, "linux,boot-display", NULL)) > + continue; > + dev = of_platform_device_create(node, "of-display", NULL); > + if (WARN_ON(!dev)) > + return -ENOMEM; > + boot_display = node; > + break; > + } > + for_each_node_by_type(node, "display") { > + if (!of_get_property(node, "linux,opened", NULL) || node == boot_display) > + continue; > + of_platform_device_create(node, "of-display", NULL); > + } > > - node = of_get_compatible_child(of_chosen, "simple-framebuffer"); > - of_platform_device_create(node, NULL, NULL); > - of_node_put(node); > + } else { > + struct device_node *node; > + > + /* > + * Handle certain compatibles explicitly, since we don't want to create > + * platform_devices for every node in /reserved-memory with a > + * "compatible", > + */ > + for_each_matching_node(node, reserved_mem_matches) > + of_platform_device_create(node, NULL, NULL); > > - /* Populate everything else. */ > - of_platform_default_populate(NULL, NULL, NULL); > + node = of_find_node_by_path("/firmware"); > + if (node) { > + of_platform_populate(node, NULL, NULL, NULL); > + of_node_put(node); > + } > + > + node = of_get_compatible_child(of_chosen, "simple-framebuffer"); > + of_platform_device_create(node, NULL, NULL); > + of_node_put(node); In v1, you supported "simple-framebuffer" on PPC. Don't we want to allow that? Maybe no one cares ATM, but that could change. Either way: Reviewed-by: Rob Herring > + > + /* Populate everything else. */ > + of_platform_default_populate(NULL, NULL, NULL); > + } > > return 0; > } > @@ -558,7 +605,6 @@ static int __init of_platform_sync_state_init(void) > return 0; > } > late_initcall_sync(of_platform_sync_state_init); > -#endif > > int of_platform_device_destroy(struct device *dev, void *data) > {