From: Johan Jonker <jbx6244@gmail.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Tom Rini <trini@konsulko.com>
Cc: Kever Yang <kever.yang@rock-chips.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Simon Glass <sjg@chromium.org>, Heiko Schocher <hs@denx.de>,
Alexey Romanov <avromanov@salutedevices.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Sean Anderson <seanga2@gmail.com>,
Quentin Schulz <quentin.schulz@cherry.de>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/3] rockchip: block: simplify rkmtd driver
Date: Fri, 18 Oct 2024 15:33:01 +0200 [thread overview]
Message-ID: <4aef209c-cbed-4fac-b48a-4101e27e64f8@gmail.com> (raw)
In-Reply-To: <20241018013015.127620-2-heinrich.schuchardt@canonical.com>
On 10/18/24 03:30, Heinrich Schuchardt wrote:
> By using blk_create_devicef() instead of blk_create_devicef() the driver
> can be simplified and brought into line with other block device drivers.
>
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> drivers/block/rkmtd.c | 21 ++-------------------
> 1 file changed, 2 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/block/rkmtd.c b/drivers/block/rkmtd.c
> index c55f052e51b..f84cacd7ead 100644
> --- a/drivers/block/rkmtd.c
> +++ b/drivers/block/rkmtd.c
> @@ -794,36 +794,19 @@ int rkmtd_init_plat(struct udevice *dev)
> return 0;
> }
>
> -static void rkmtd_blk_kmalloc_release(struct udevice *dev, void *res)
> -{
> - /* noop */
> -}
> -
> static int rkmtd_bind(struct udevice *dev)
> {
> struct rkmtd_dev *plat = dev_get_plat(dev);
> - char dev_name[30], *str;
> struct blk_desc *desc;
> struct udevice *bdev;
> int ret;
>
> - snprintf(dev_name, sizeof(dev_name), "%s.%s", dev->name, "blk");
> -
> - str = devres_alloc(rkmtd_blk_kmalloc_release, strlen(dev_name) + 1, GFP_KERNEL);
Hi Heinrich, Simon,
The function strdup() is not an exact replacement for the devres_alloc() function in relation to a device.
It is in use for memory leak detection / device resource management.
Not sure what the status of that devres project currently is? Also tracking in general in relation to EFI and blk-class.
https://source.denx.de/u-boot/u-boot/-/blob/master/drivers/block/blk-uclass.c?ref_type=heads#L739
https://source.denx.de/u-boot/u-boot/-/blob/master/drivers/block/rkmtd.c?ref_type=heads#L812
Test for this driver are based on work done by Simon.
https://source.denx.de/u-boot/u-boot/-/blob/master/test/dm/host.c?ref_type=heads#L71
This rkmtd driver makes use of devm_kzalloc(). All the memory that rkmtd reserves is freed.
But if I remember well somehow I was not able to free all memory on unbind and was not able to find the source, so I didn't include that last test.
https://elixir.bootlin.com/u-boot/v2024.10/source/test/dm/rkmtd.c#L84
Johan
> - if (unlikely(!str))
> - return -ENOMEM;
> -
> - strcpy(str, dev_name);
> -
> - ret = blk_create_device(dev, "rkmtd_blk", str, UCLASS_RKMTD,
> - -1, 512, LBA, &bdev);
> + ret = blk_create_devicef(dev, "rkmtd_blk", "blk", UCLASS_RKMTD,
> + -1, 512, LBA, &bdev);
> if (ret) {
> - free(str);
> return log_msg_ret("blk", ret);
> }
>
> - devres_add(dev, str);
> -
> desc = dev_get_uclass_plat(bdev);
> sprintf(desc->vendor, "0x%.4x", 0x2207);
> memcpy(desc->product, "RKMTD", sizeof("RKMTD"));
next prev parent reply other threads:[~2024-10-18 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 1:30 [PATCH 0/3] block: make blk_create_device() static Heinrich Schuchardt
2024-10-18 1:30 ` [PATCH 1/3] rockchip: block: simplify rkmtd driver Heinrich Schuchardt
2024-10-18 13:33 ` Johan Jonker [this message]
2024-10-19 11:50 ` Simon Glass
2024-10-21 13:35 ` Heinrich Schuchardt
2024-10-22 19:58 ` Johan Jonker
2024-10-18 1:30 ` [PATCH 2/3] efi_driver: use blk_create_devicef() Heinrich Schuchardt
2024-10-18 14:57 ` Simon Glass
2024-10-18 1:30 ` [PATCH 3/3] block: make blk_create_device() static Heinrich Schuchardt
2024-10-18 14:52 ` Simon Glass
2024-10-21 10:49 ` Ilias Apalodimas
2024-10-24 20:42 ` (subset) [PATCH 0/3] " Tom Rini
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=4aef209c-cbed-4fac-b48a-4101e27e64f8@gmail.com \
--to=jbx6244@gmail.com \
--cc=avromanov@salutedevices.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=hs@denx.de \
--cc=ilias.apalodimas@linaro.org \
--cc=kever.yang@rock-chips.com \
--cc=michael@amarulasolutions.com \
--cc=quentin.schulz@cherry.de \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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