From: Thomas Zimmermann <tzimmermann@suse.de>
To: Javier Martinez Canillas <javierm@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Miaoqian Lin <linmq006@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, Johan Hovold <johan@kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH v3 1/5] firmware: sysfb: Make sysfb_create_simplefb() return a pdev pointer
Date: Mon, 25 Apr 2022 10:02:20 +0200 [thread overview]
Message-ID: <586da154-5494-aaab-aa07-30f77daebbc2@suse.de> (raw)
In-Reply-To: <20220420085303.100654-2-javierm@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 4662 bytes --]
Am 20.04.22 um 10:52 schrieb Javier Martinez Canillas:
> This function just returned 0 on success or an errno code on error, but it
> could be useful for sysfb_init() callers to have a pointer to the device.
>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
>
> (no changes since v2)
>
> Changes in v2:
> - Rebase on top of latest drm-misc-next and fix conflicts (Daniel Vetter).
>
> drivers/firmware/sysfb.c | 4 ++--
> drivers/firmware/sysfb_simplefb.c | 16 ++++++++--------
> include/linux/sysfb.h | 10 +++++-----
> 3 files changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/firmware/sysfb.c b/drivers/firmware/sysfb.c
> index 2bfbb05f7d89..b032f40a92de 100644
> --- a/drivers/firmware/sysfb.c
> +++ b/drivers/firmware/sysfb.c
> @@ -46,8 +46,8 @@ static __init int sysfb_init(void)
> /* try to create a simple-framebuffer device */
> compatible = sysfb_parse_mode(si, &mode);
> if (compatible) {
> - ret = sysfb_create_simplefb(si, &mode);
> - if (!ret)
> + pd = sysfb_create_simplefb(si, &mode);
> + if (!IS_ERR(pd))
> return 0;
> }
>
> diff --git a/drivers/firmware/sysfb_simplefb.c b/drivers/firmware/sysfb_simplefb.c
> index bda8712bfd8c..a353e27f83f5 100644
> --- a/drivers/firmware/sysfb_simplefb.c
> +++ b/drivers/firmware/sysfb_simplefb.c
> @@ -57,8 +57,8 @@ __init bool sysfb_parse_mode(const struct screen_info *si,
> return false;
> }
>
> -__init int sysfb_create_simplefb(const struct screen_info *si,
> - const struct simplefb_platform_data *mode)
> +__init struct platform_device *sysfb_create_simplefb(const struct screen_info *si,
> + const struct simplefb_platform_data *mode)
> {
> struct platform_device *pd;
> struct resource res;
> @@ -76,7 +76,7 @@ __init int sysfb_create_simplefb(const struct screen_info *si,
> base |= (u64)si->ext_lfb_base << 32;
> if (!base || (u64)(resource_size_t)base != base) {
> printk(KERN_DEBUG "sysfb: inaccessible VRAM base\n");
> - return -EINVAL;
> + return ERR_PTR(-EINVAL);
> }
>
> /*
> @@ -93,7 +93,7 @@ __init int sysfb_create_simplefb(const struct screen_info *si,
> length = mode->height * mode->stride;
> if (length > size) {
> printk(KERN_WARNING "sysfb: VRAM smaller than advertised\n");
> - return -EINVAL;
> + return ERR_PTR(-EINVAL);
> }
> length = PAGE_ALIGN(length);
>
> @@ -104,11 +104,11 @@ __init int sysfb_create_simplefb(const struct screen_info *si,
> res.start = base;
> res.end = res.start + length - 1;
> if (res.end <= res.start)
> - return -EINVAL;
> + return ERR_PTR(-EINVAL);
>
> pd = platform_device_alloc("simple-framebuffer", 0);
> if (!pd)
> - return -ENOMEM;
> + return ERR_PTR(-ENOMEM);
>
> sysfb_apply_efi_quirks(pd);
>
> @@ -124,10 +124,10 @@ __init int sysfb_create_simplefb(const struct screen_info *si,
> if (ret)
> goto err_put_device;
>
> - return 0;
> + return pd;
>
> err_put_device:
> platform_device_put(pd);
>
> - return ret;
> + return ERR_PTR(ret);
> }
> diff --git a/include/linux/sysfb.h b/include/linux/sysfb.h
> index b0dcfa26d07b..708152e9037b 100644
> --- a/include/linux/sysfb.h
> +++ b/include/linux/sysfb.h
> @@ -72,8 +72,8 @@ static inline void sysfb_apply_efi_quirks(struct platform_device *pd)
>
> bool sysfb_parse_mode(const struct screen_info *si,
> struct simplefb_platform_data *mode);
> -int sysfb_create_simplefb(const struct screen_info *si,
> - const struct simplefb_platform_data *mode);
> +struct platform_device *sysfb_create_simplefb(const struct screen_info *si,
> + const struct simplefb_platform_data *mode);
>
> #else /* CONFIG_SYSFB_SIMPLE */
>
> @@ -83,10 +83,10 @@ static inline bool sysfb_parse_mode(const struct screen_info *si,
> return false;
> }
>
> -static inline int sysfb_create_simplefb(const struct screen_info *si,
> - const struct simplefb_platform_data *mode)
> +static inline struct platform_device *sysfb_create_simplefb(const struct screen_info *si,
> + const struct simplefb_platform_data *mode)
> {
> - return -EINVAL;
> + return ERR_PTR(-EINVAL);
> }
>
> #endif /* CONFIG_SYSFB_SIMPLE */
--
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:02 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 [this message]
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
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=586da154-5494-aaab-aa07-30f77daebbc2@suse.de \
--to=tzimmermann@suse.de \
--cc=bp@suse.de \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--cc=johan@kernel.org \
--cc=linmq006@gmail.com \
--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