From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Helge Deller <deller@gmx.de>, Bert Karwatzki <spasswolf@web.de>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
Peter Jones <pjones@redhat.com>
Subject: Re: [PATCH 3/5] fbdev: Introduce devm_register_framebuffer()
Date: Fri, 30 Aug 2024 09:17:45 +0200 [thread overview]
Message-ID: <8b52669c-4c99-45e2-8b5e-9348e5e00f70@t-8ch.de> (raw)
In-Reply-To: <20240827-efifb-sysfs-v1-3-c9cc3e052180@weissschuh.net>
Hi everybody,
On 2024-08-27 17:25:14+0000, Thomas Weißschuh wrote:
> Introduce a device-managed variant of register_framebuffer() which
> automatically unregisters the framebuffer on device destruction.
> This can simplify the error handling and resource management in drivers.
Bert reported that this series broke his framebuffer ([0], [1]).
[0] https://lore.kernel.org/lkml/20240829224124.2978-1-spasswolf@web.de/
[1] https://lore.kernel.org/lkml/20240829230438.3226-1-spasswolf@web.de/
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> drivers/video/fbdev/core/fbmem.c | 24 ++++++++++++++++++++++++
> include/linux/fb.h | 1 +
> 2 files changed, 25 insertions(+)
>
> diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/fbmem.c
> index 4c4ad0a86a50..d17a2daa2483 100644
> --- a/drivers/video/fbdev/core/fbmem.c
> +++ b/drivers/video/fbdev/core/fbmem.c
> @@ -544,6 +544,30 @@ unregister_framebuffer(struct fb_info *fb_info)
[..]
> +/**
> + * devm_register_framebuffer - resource-managed frame buffer device registration
> + * @dev: device the framebuffer belongs to
> + * @fb_info: frame buffer info structure
> + *
> + * Registers a frame buffer device @fb_info to device @dev.
> + *
> + * Returns negative errno on error, or zero for success.
> + *
> + */
> +int
> +devm_register_framebuffer(struct device *dev, struct fb_info *fb_info)
> +{
> + return devm_add_action_or_reset(dev, devm_unregister_framebuffer, fb_info);
> +}
> +EXPORT_SYMBOL(devm_register_framebuffer);
This implementation is wrong, it never actually registers the
framebuffer. It should look like this:
int
devm_register_framebuffer(struct device *dev, struct fb_info *fb_info)
{
int ret;
ret = register_framebuffer(fb_info);
if (ret)
return ret;
return devm_add_action_or_reset(dev, devm_unregister_framebuffer, fb_info);
}
EXPORT_SYMBOL(devm_register_framebuffer);
Bert, could you test this?
Helge, do you want me to resend the series, minus the original patch 1?
next prev parent reply other threads:[~2024-08-30 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 15:25 [PATCH 0/5] fbdev: devm_register_framebuffer() and some fixes for efifb Thomas Weißschuh
2024-08-27 15:25 ` [PATCH 1/5] fbdev/efifb: Use stack memory for screeninfo structs Thomas Weißschuh
2024-08-28 17:42 ` Helge Deller
2024-08-29 7:52 ` Thomas Weißschuh
2024-08-27 15:25 ` [PATCH 2/5] fbdev/efifb: Register sysfs groups through driver core Thomas Weißschuh
2024-08-28 17:50 ` Helge Deller
2024-08-27 15:25 ` [PATCH 3/5] fbdev: Introduce devm_register_framebuffer() Thomas Weißschuh
2024-08-30 7:17 ` Thomas Weißschuh [this message]
2024-08-30 8:25 ` Bert Karwatzki
2024-08-30 8:44 ` Helge Deller
2024-08-27 15:25 ` [PATCH 4/5] fbdev/efifb: Use devm_register_framebuffer() Thomas Weißschuh
2024-08-27 15:25 ` [PATCH 5/5] fbdev/efifb: Use driver-private screen_info for sysfs Thomas Weißschuh
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=8b52669c-4c99-45e2-8b5e-9348e5e00f70@t-8ch.de \
--to=linux@weissschuh.net \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pjones@redhat.com \
--cc=spasswolf@web.de \
/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