From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8] imx: i2c: Zap unnecessary malloc() calls
Date: Tue, 16 Dec 2014 18:00:27 +0100 [thread overview]
Message-ID: <201412161800.27572.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ1FrYpKN7ssN8apG61TP=nzqP8-jKcrZaQdWbDM4DfU8Q@mail.gmail.com>
On Tuesday, December 16, 2014 at 05:27:53 PM, Simon Glass wrote:
> Hi Marek,
>
> On 16 December 2014 at 06:09, Marek Vasut <marex@denx.de> wrote:
> > The malloc() calls are unnecessary, just allocate the stuff on stack.
> > While at it, reorder the code a little, so that only one variable is
> > used for the text, use snprintf() instead of sprintf() and use %01d
> > as a formatting string to avoid any possible overflows.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Igor Grinberg <grinberg@compulab.co.il>
> > Cc: Nikita Kiryanov <nikita@compulab.co.il>
> > Cc: Sean Cross <xobs@kosagi.com>
> > Cc: Simon Glass <sjg@chromium.org>
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Tim Harvey <tharvey@gateworks.com>
> > ---
> >
> > arch/arm/imx-common/i2c-mxv7.c | 24 ++++++++----------------
> > 1 file changed, 8 insertions(+), 16 deletions(-)
> >
> > diff --git a/arch/arm/imx-common/i2c-mxv7.c
> > b/arch/arm/imx-common/i2c-mxv7.c index 34f5387..1a632e7 100644
> > --- a/arch/arm/imx-common/i2c-mxv7.c
> > +++ b/arch/arm/imx-common/i2c-mxv7.c
> > @@ -73,26 +73,21 @@ static void * const i2c_bases[] = {
> >
> > int setup_i2c(unsigned i2c_index, int speed, int slave_addr,
> >
> > struct i2c_pads_info *p)
> >
> > {
> >
> > - char *name1, *name2;
> > + char name[9];
> >
> > int ret;
> >
> > if (i2c_index >= ARRAY_SIZE(i2c_bases))
> >
> > return -EINVAL;
> >
> > - name1 = malloc(9);
> > - name2 = malloc(9);
> > - if (!name1 || !name2)
> > - return -ENOMEM;
> > -
> > - sprintf(name1, "i2c_sda%d", i2c_index);
> > - sprintf(name2, "i2c_scl%d", i2c_index);
> > - ret = gpio_request(p->sda.gp, name1);
> > + snprintf(name, sizeof(name), "i2c_sda%01d", i2c_index);
> > + ret = gpio_request(p->sda.gp, name);
>
> Does this board use driver model? If not it should be easy to convert
> since one MX6 board supports it. With driver model there is
> gpio_requestf("i2c_sda%01d", i2c_index);
No, not yet, but it's in the pipeline. I am already keeping an eye on a few
conversion patches to get this done.
next prev parent reply other threads:[~2014-12-16 17:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 13:09 [U-Boot] [PATCH 1/8] imx: i2c: Zap unnecessary malloc() calls Marek Vasut
2014-12-16 13:09 ` [U-Boot] [PATCH 2/8] arm: mx6: gw_ventana: Define CONFIG_SYS_MALLOC_F_LEN Marek Vasut
2014-12-30 13:35 ` Stefano Babic
2014-12-16 13:09 ` [U-Boot] [PATCH 3/8] arm: mx6: novena: " Marek Vasut
2014-12-30 13:35 ` Stefano Babic
2014-12-16 13:09 ` [U-Boot] [PATCH 4/8] arm: mx6: novena: Minor coding style fix Marek Vasut
2014-12-30 13:35 ` Stefano Babic
2014-12-16 13:09 ` [U-Boot] [PATCH 5/8] arm: mx6: novena: Minor config file fix Marek Vasut
2014-12-30 13:35 ` Stefano Babic
2014-12-16 13:09 ` [U-Boot] [PATCH 6/8] arm: mx6: novena: Pull GPIO definitions into header Marek Vasut
2014-12-30 13:35 ` Stefano Babic
2014-12-16 13:09 ` [U-Boot] [PATCH 7/8] arm: mx6: novena: Pull video handling into separate file Marek Vasut
2014-12-30 13:36 ` Stefano Babic
2014-12-16 13:09 ` [U-Boot] [PATCH 8/8] arm: mx6: novena: Add proper LVDS display support Marek Vasut
2014-12-16 16:22 ` Simon Glass
2014-12-16 16:59 ` Marek Vasut
2014-12-30 13:37 ` Stefano Babic
2014-12-16 15:34 ` [U-Boot] [PATCH 1/8] imx: i2c: Zap unnecessary malloc() calls Christian Gmeiner
2014-12-16 16:27 ` Simon Glass
2014-12-16 17:00 ` Marek Vasut [this message]
2014-12-30 13:34 ` Stefano Babic
2014-12-30 15:34 ` Marek Vasut
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=201412161800.27572.marex@denx.de \
--to=marex@denx.de \
--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