From: Masahiro Yamada <masahiroy@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Masahiro Yamada <masahiroy@kernel.org>
Subject: [PATCH 1/2] pinctrl: pinconf-generic: resize the pin config array directly
Date: Tue, 21 Nov 2023 07:28:31 +0900 [thread overview]
Message-ID: <20231120222832.4063882-2-masahiroy@kernel.org> (raw)
In-Reply-To: <20231120222832.4063882-1-masahiroy@kernel.org>
pinconf_generic_parse_dt_config() allocates memory that is large enough
to contain all the config parameters. Then, kmemdup() copies the found
configs to the memory with the exact size.
There is no need to allocate memory twice; you can directly resize the
initial memory using krealloc_array().
I also changed kcalloc() to kmalloc_array() to keep the consistency with
krealloc_array(). This change has no impact because you do not need to
zero out the 'cfg' array.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
drivers/pinctrl/pinconf-generic.c | 25 ++++++++-----------------
1 file changed, 8 insertions(+), 17 deletions(-)
diff --git a/drivers/pinctrl/pinconf-generic.c b/drivers/pinctrl/pinconf-generic.c
index 8313cb5f3b3c..ba4fe2466e78 100644
--- a/drivers/pinctrl/pinconf-generic.c
+++ b/drivers/pinctrl/pinconf-generic.c
@@ -247,7 +247,6 @@ int pinconf_generic_parse_dt_config(struct device_node *np,
{
unsigned long *cfg;
unsigned int max_cfg, ncfg = 0;
- int ret;
if (!np)
return -EINVAL;
@@ -256,7 +255,7 @@ int pinconf_generic_parse_dt_config(struct device_node *np,
max_cfg = ARRAY_SIZE(dt_params);
if (pctldev)
max_cfg += pctldev->desc->num_custom_params;
- cfg = kcalloc(max_cfg, sizeof(*cfg), GFP_KERNEL);
+ cfg = kmalloc_array(max_cfg, sizeof(*cfg), GFP_KERNEL);
if (!cfg)
return -ENOMEM;
@@ -266,30 +265,22 @@ int pinconf_generic_parse_dt_config(struct device_node *np,
parse_dt_cfg(np, pctldev->desc->custom_params,
pctldev->desc->num_custom_params, cfg, &ncfg);
- ret = 0;
-
/* no configs found at all */
if (ncfg == 0) {
+ kfree(cfg);
*configs = NULL;
*nconfigs = 0;
- goto out;
+ return 0;
}
- /*
- * Now limit the number of configs to the real number of
- * found properties.
- */
- *configs = kmemdup(cfg, ncfg * sizeof(unsigned long), GFP_KERNEL);
- if (!*configs) {
- ret = -ENOMEM;
- goto out;
- }
+ /* Now resize the array to store the real number of found properties. */
+ *configs = krealloc_array(cfg, ncfg, sizeof(unsigned long), GFP_KERNEL);
+ if (!*configs)
+ return -ENOMEM;
*nconfigs = ncfg;
-out:
- kfree(cfg);
- return ret;
+ return 0;
}
EXPORT_SYMBOL_GPL(pinconf_generic_parse_dt_config);
--
2.40.1
next prev parent reply other threads:[~2023-11-20 22:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:28 [PATCH 0/2] pinctrl: pinconf-generic: clean up pinconf_parse_dt_config() Masahiro Yamada
2023-11-20 22:28 ` Masahiro Yamada [this message]
2023-11-21 10:21 ` [PATCH 1/2] pinctrl: pinconf-generic: resize the pin config array directly Masahiro Yamada
2023-11-24 10:06 ` Linus Walleij
2023-11-24 11:24 ` Andy Shevchenko
2023-11-25 18:03 ` Masahiro Yamada
2023-11-20 22:28 ` [PATCH 2/2] pinctrl: pinconf-generic: remove the special handling for no config case Masahiro Yamada
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=20231120222832.4063882-2-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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