From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org, Borislav Petkov <bp@suse.de>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 2/5] firmware: sysfb: Add helpers to unregister a pdev and disable registration
Date: Mon, 25 Apr 2022 10:24:23 +0200 [thread overview]
Message-ID: <7a512b4f-2327-b0c3-2f3c-60dc5be3c443@suse.de> (raw)
In-Reply-To: <20220420085303.100654-3-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 6247 bytes --]
Hi
Am 20.04.22 um 10:53 schrieb Javier Martinez Canillas:
> These can be used by subsystems to unregister a platform device registered
> by sysfb and also to disable future platform device registration in sysfb.
>
> Suggested-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
>
> (no changes since v2)
>
> Changes in v2:
> - Add kernel-doc comments and include in other_interfaces.rst (Daniel Vetter).
>
> .../driver-api/firmware/other_interfaces.rst | 6 ++
> drivers/firmware/sysfb.c | 73 +++++++++++++++++--
> include/linux/sysfb.h | 19 +++++
> 3 files changed, 92 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/driver-api/firmware/other_interfaces.rst b/Documentation/driver-api/firmware/other_interfaces.rst
> index b81794e0cfbb..06ac89adaafb 100644
> --- a/Documentation/driver-api/firmware/other_interfaces.rst
> +++ b/Documentation/driver-api/firmware/other_interfaces.rst
> @@ -13,6 +13,12 @@ EDD Interfaces
> .. kernel-doc:: drivers/firmware/edd.c
> :internal:
>
> +Generic System Framebuffers Interface
> +-------------------------------------
> +
> +.. kernel-doc:: drivers/firmware/sysfb.c
> + :export:
> +
> Intel Stratix10 SoC Service Layer
> ---------------------------------
> Some features of the Intel Stratix10 SoC require a level of privilege
> diff --git a/drivers/firmware/sysfb.c b/drivers/firmware/sysfb.c
> index b032f40a92de..a50d2858ce4d 100644
> --- a/drivers/firmware/sysfb.c
> +++ b/drivers/firmware/sysfb.c
> @@ -34,21 +34,78 @@
> #include <linux/screen_info.h>
> #include <linux/sysfb.h>
>
> +static struct platform_device *pd;
You could have multiple instances of simple-framebuffer because you
don't know what the firmware set up. It originated from DT and EFI/VESA
is really just an afterthought. If there is more than 1 instance, your
entire unregistering breaks down.
(I've been told that such multi-output cases exist in the context of OF
framebuffers. Something similar could exist for simple-frambuffer as well.)
Best regards
Thomas
> +static DEFINE_MUTEX(load_lock);
> +static bool disabled;
> +
> +/**
> + * sysfb_disable() - disable the Generic System Framebuffers support
> + *
> + * This disables the registration of system framebuffer devices that match the
> + * generic drivers that make use of the system framebuffer set up by firmware.
> + *
> + * Context: The function can sleep. A @load_lock mutex is acquired to serialize
> + * against sysfb_init(), that registers a system framebuffer device and
> + * sysfb_try_unregister(), that tries to unregister framebuffer devices.
> + */
> +void sysfb_disable(void)
> +{
> + mutex_lock(&load_lock);
> + disabled = true;
> + mutex_unlock(&load_lock);
> +}
> +EXPORT_SYMBOL_GPL(sysfb_disable);
> +
> +/**
> + * sysfb_try_unregister() - attempt to unregister a system framebuffer device
> + * @dev: device to unregister
> + *
> + * This tries to unregister a system framebuffer device if this was registered
> + * by the Generic System Framebuffers. The device will only be unregistered if
> + * it was registered by sysfb_init(), otherwise it will not be unregistered.
> + *
> + * Context: The function can sleep. a @load_lock mutex is acquired to serialize
> + * against sysfb_init(), that registers a simple framebuffer device and
> + * sysfb_disable(), that disables the Generic System Framebuffers support.
> + *
> + * Return:
> + * * true - the device was unregistered successfully
> + * * false - the device was not unregistered
> + */
> +bool sysfb_try_unregister(struct device *dev)
> +{
> + bool ret = true;
> +
> + mutex_lock(&load_lock);
> + if (!pd || pd != to_platform_device(dev))
> + return false;
> +
> + platform_device_unregister(to_platform_device(dev));
> + pd = NULL;
> + mutex_unlock(&load_lock);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(sysfb_try_unregister);
> +
> static __init int sysfb_init(void)
> {
> struct screen_info *si = &screen_info;
> struct simplefb_platform_data mode;
> - struct platform_device *pd;
> const char *name;
> bool compatible;
> - int ret;
> + int ret = 0;
> +
> + mutex_lock(&load_lock);
> + if (disabled)
> + goto unlock_mutex;
>
> /* try to create a simple-framebuffer device */
> compatible = sysfb_parse_mode(si, &mode);
> if (compatible) {
> pd = sysfb_create_simplefb(si, &mode);
> if (!IS_ERR(pd))
> - return 0;
> + goto unlock_mutex;
> }
>
> /* if the FB is incompatible, create a legacy framebuffer device */
> @@ -60,8 +117,10 @@ static __init int sysfb_init(void)
> name = "platform-framebuffer";
>
> pd = platform_device_alloc(name, 0);
> - if (!pd)
> - return -ENOMEM;
> + if (!pd) {
> + ret = -ENOMEM;
> + goto unlock_mutex;
> + }
>
> sysfb_apply_efi_quirks(pd);
>
> @@ -73,9 +132,11 @@ static __init int sysfb_init(void)
> if (ret)
> goto err;
>
> - return 0;
> + goto unlock_mutex;
> err:
> platform_device_put(pd);
> +unlock_mutex:
> + mutex_unlock(&load_lock);
> return ret;
> }
>
> diff --git a/include/linux/sysfb.h b/include/linux/sysfb.h
> index 708152e9037b..e8c0313fac8f 100644
> --- a/include/linux/sysfb.h
> +++ b/include/linux/sysfb.h
> @@ -55,6 +55,25 @@ struct efifb_dmi_info {
> int flags;
> };
>
> +#ifdef CONFIG_SYSFB
> +
> +void sysfb_disable(void);
> +bool sysfb_try_unregister(struct device *dev);
> +
> +#else /* CONFIG_SYSFB */
> +
> +static inline void sysfb_disable(void)
> +{
> +
> +}
> +
> +static inline bool sysfb_try_unregister(struct device *dev)
> +{
> + return false;
> +}
> +
> +#endif /* CONFIG_SYSFB */
> +
> #ifdef CONFIG_EFI
>
> extern struct efifb_dmi_info efifb_dmi_list[];
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-04-25 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 8:52 [PATCH v3 0/5] Fix some race conditions that exists between fbmem and sysfb Javier Martinez Canillas
2022-04-20 8:52 ` [PATCH v3 1/5] firmware: sysfb: Make sysfb_create_simplefb() return a pdev pointer Javier Martinez Canillas
2022-04-25 8:02 ` Thomas Zimmermann
2022-04-20 8:53 ` [PATCH v3 2/5] firmware: sysfb: Add helpers to unregister a pdev and disable registration Javier Martinez Canillas
2022-04-25 8:24 ` Thomas Zimmermann [this message]
2022-04-20 8:53 ` [PATCH v3 3/5] fbdev: Restart conflicting fb removal loop when unregistering devices Javier Martinez Canillas
2022-04-25 8:27 ` Thomas Zimmermann
2022-04-25 8:37 ` Javier Martinez Canillas
2022-04-20 8:53 ` [PATCH v3 4/5] fbdev: Fix some race conditions between fbmem and sysfb Javier Martinez Canillas
2022-04-25 8:30 ` Thomas Zimmermann
2022-04-22 15:17 ` [PATCH v3 0/5] Fix some race conditions that exists " Greg Kroah-Hartman
2022-04-25 8:54 ` Thomas Zimmermann
2022-04-25 9:15 ` Thomas Zimmermann
2022-04-25 9:49 ` Javier Martinez Canillas
2022-04-29 7:47 ` Daniel Vetter
2022-04-29 8:06 ` Javier Martinez Canillas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a512b4f-2327-b0c3-2f3c-60dc5be3c443@suse.de \
--to=tzimmermann@suse.de \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®