Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Shixiong Ou <oushixiong1025@163.com>, Timur Tabi <timur@kernel.org>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Shixiong Ou <oushixiong@kylinos.cn>
Subject: Re: [PATCH v2] fbdev: fsl-diu-fb: add missing device_remove_file()
Date: Sun, 9 Mar 2025 20:42:46 +0100	[thread overview]
Message-ID: <0a15e04f-bd6d-4c2b-a8e1-708880fa433c@gmx.de> (raw)
In-Reply-To: <20250309081607.27784-1-oushixiong1025@163.com>

On 3/9/25 09:16, Shixiong Ou wrote:
> From: Shixiong Ou <oushixiong@kylinos.cn>
>
> Call device_remove_file() when driver remove.
>
> Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>
> ---
> v1->v2:
> 	add has_sysfs_attrs flag.
>
>   drivers/video/fbdev/fsl-diu-fb.c | 6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/drivers/video/fbdev/fsl-diu-fb.c b/drivers/video/fbdev/fsl-diu-fb.c
> index 5ac8201c3533..57f7fe6a4c76 100644
> --- a/drivers/video/fbdev/fsl-diu-fb.c
> +++ b/drivers/video/fbdev/fsl-diu-fb.c
> @@ -384,6 +384,7 @@ struct fsl_diu_data {
>   	__le16 next_cursor[MAX_CURS * MAX_CURS] __aligned(32);
>   	uint8_t edid_data[EDID_LENGTH];
>   	bool has_edid;
> +	bool has_dev_attr;
>   } __aligned(32);
>
>   /* Determine the DMA address of a member of the fsl_diu_data structure */
> @@ -1809,6 +1810,7 @@ static int fsl_diu_probe(struct platform_device *pdev)
>   			data->dev_attr.attr.name);
>   	}
>
> +	data->has_dev_attr = true;
>   	dev_set_drvdata(&pdev->dev, data);
>   	return 0;
>
> @@ -1827,6 +1829,10 @@ static void fsl_diu_remove(struct platform_device *pdev)
>   	int i;
>
>   	data = dev_get_drvdata(&pdev->dev);
> +
> +	if (data->has_dev_attr)

Looking at other drivers (e.g. drivers/net/can/usb/esd_usb.c) it seems
that device_remove_file() is ok even if it's not fully initialized...

I think you can drop those extra checks.

Helge


> +		device_remove_file(&pdev->dev, &data->dev_attr);
> +
>   	disable_lcdc(&data->fsl_diu_info[0]);
>
>   	free_irq(data->irq, data->diu_reg);


  reply	other threads:[~2025-03-09 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09  8:16 [PATCH v2] fbdev: fsl-diu-fb: add missing device_remove_file() Shixiong Ou
2025-03-09 19:42 ` Helge Deller [this message]
2025-03-11  7:48   ` Shixiong Ou

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=0a15e04f-bd6d-4c2b-a8e1-708880fa433c@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oushixiong1025@163.com \
    --cc=oushixiong@kylinos.cn \
    --cc=timur@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