The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Lizhi Hou <lizhi.hou@amd.com>,
	dri-devel@lists.freedesktop.org, Oded Gabbay <ogabbay@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	George Yang <George.Yang@amd.com>,
	king.tam@amd.com, Max Zhen <max.zhen@amd.com>,
	Min Ma <min.ma@amd.com>,
	Narendra Gutta <VenkataNarendraKumar.Gutta@amd.com>,
	Sonal Santan <sonal.santan@amd.com>
Subject: Re: [PATCH V2 01/10] accel/amdxdna: Add a new driver for AMD AI Engine
Date: Wed, 7 Aug 2024 13:06:39 +0200	[thread overview]
Message-ID: <d7b4ea8a-74c5-40db-bf11-f8345f570ef5@web.de> (raw)
In-Reply-To: <20240805173959.3181199-2-lizhi.hou@amd.com>

If you temporarily find the circumstances too challenging for applications
of scope-based resource management, I suggest to use the following statements instead
(so that a bit of redundant code can be avoided).



…
> +++ b/drivers/accel/amdxdna/aie2_pci.c
> @@ -0,0 +1,182 @@
> +static int aie2_init(struct amdxdna_dev *xdna)
> +{
> +	release_firmware(fw);
> +	return 0;

	ret = 0;
	goto release_fw;

…
> +release_fw:
> +	release_firmware(fw);
> +
> +	return ret;
> +}
…


Otherwise (in case further collateral evolution will become more desirable):
…
> +static int aie2_init(struct amdxdna_dev *xdna)
> +{
> +	const struct firmware *fw;

I propose to take another software design option better into account.

* You may reduce the scope of such a local variable.

* How do you think about to use the attribute “__free(firmware)”?
  https://elixir.bootlin.com/linux/v6.11-rc2/source/include/linux/firmware.h#L214> +	ret = request_firmware(&fw, ndev->priv->fw_path, &pdev->dev);
…


Regards,
Markus

  reply	other threads:[~2024-08-07 11:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 17:39 [PATCH V2 00/10] AMD XDNA driver Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 01/10] accel/amdxdna: Add a new driver for AMD AI Engine Lizhi Hou
2024-08-07 11:06   ` Markus Elfring [this message]
2024-08-07 16:07     ` Lizhi Hou
2024-08-09 15:24   ` Carl Vanderlip
2024-08-12 15:58     ` Lizhi Hou
2024-08-09 16:11   ` Jeffrey Hugo
2024-08-14 18:16     ` Lizhi Hou
2024-08-14 18:46       ` Jeffrey Hugo
2024-08-14 20:24         ` Lizhi Hou
2024-08-14 21:53           ` Jeffrey Hugo
2024-08-14 21:59             ` Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 02/10] accel/amdxdna: Support hardware mailbox Lizhi Hou
2024-08-09 16:32   ` Jeffrey Hugo
2024-08-14 21:05     ` Lizhi Hou
2024-08-14 22:02       ` Jeffrey Hugo
2024-08-05 17:39 ` [PATCH V2 03/10] accel/amdxdna: Add hardware resource solver Lizhi Hou
2024-08-09 16:36   ` Jeffrey Hugo
2024-08-05 17:39 ` [PATCH V2 04/10] accel/amdxdna: Add hardware context Lizhi Hou
2024-08-08 21:34   ` Alex Deucher
2024-08-08 22:15     ` Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 05/10] accel/amdxdna: Add GEM buffer object management Lizhi Hou
2024-08-09 16:39   ` Jeffrey Hugo
2024-08-05 17:39 ` [PATCH V2 06/10] accel/amdxdna: Add command execution Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 07/10] accel/amdxdna: Add suspend and resume Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 08/10] accel/amdxdna: Add error handling Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 09/10] accel/amdxdna: Add query functions Lizhi Hou
2024-08-09 16:42   ` Jeffrey Hugo
2024-08-19 19:50     ` Lizhi Hou
2024-08-05 17:39 ` [PATCH V2 10/10] accel/amdxdna: Add firmware debug buffer support Lizhi Hou
2024-08-06  8:05 ` [PATCH V2 00/10] AMD XDNA driver Markus Elfring
2024-08-06 17:18   ` Lizhi Hou
2024-08-06 18:56     ` Markus Elfring
2024-08-09 15:21 ` Jeffrey Hugo
2024-08-12 18:16   ` Lizhi Hou
2024-08-14 18:49     ` Jeffrey Hugo
2024-08-14 20:06       ` Lizhi Hou
2024-09-03 17:50         ` Lizhi Hou

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=d7b4ea8a-74c5-40db-bf11-f8345f570ef5@web.de \
    --to=markus.elfring@web.de \
    --cc=George.Yang@amd.com \
    --cc=VenkataNarendraKumar.Gutta@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=king.tam@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=max.zhen@amd.com \
    --cc=min.ma@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=sonal.santan@amd.com \
    /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