public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sf: Stop leaking memory
Date: Thu, 3 Jul 2014 23:04:28 +0200	[thread overview]
Message-ID: <201407032304.28511.marex@denx.de> (raw)
In-Reply-To: <CAD6G_RRigetbSOutvvbvNn0cNacT39Q-7LWK7prefcEo_kN_xg@mail.gmail.com>

On Thursday, July 03, 2014 at 10:24:44 PM, Jagan Teki wrote:
> On Fri, Jun 13, 2014 at 2:23 AM, Marek Vasut <marex@denx.de> wrote:
> > It's usually a common pattern to free() the memory that we allocated.
> > Implement this here to stop leaking memory. Also, add a debug output
> > when BAR configuration fails to follow suit.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Michal Simek <michal.simek@xilinx.com>
> > Cc: Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
> > ---
> > 
> >  drivers/mtd/spi/sf_ops.c | 7 +++++--
> >  1 file changed, 5 insertions(+), 2 deletions(-)
> > 
> > NOTE: I think we can do without the memory allocation here altogether.
> > 
> >       Is there any upper limit on the number of dummy bytes that can
> >       go with a SF command? If so, we can just allocate that buffer on
> >       a stack and be done with it.
> > 
> > diff --git a/drivers/mtd/spi/sf_ops.c b/drivers/mtd/spi/sf_ops.c
> > index ef91b92..29a7867 100644
> > --- a/drivers/mtd/spi/sf_ops.c
> > +++ b/drivers/mtd/spi/sf_ops.c
> > @@ -398,8 +398,10 @@ int spi_flash_cmd_read_ops(struct spi_flash *flash,
> > u32 offset,
> > 
> >  #endif
> >  #ifdef CONFIG_SPI_FLASH_BAR
> >  
> >                 bank_sel = spi_flash_bank(flash, read_addr);
> > 
> > -               if (bank_sel < 0)
> > -                       return ret;
> > +               if (bank_sel < 0) {
> > +                       debug("SF: bank select failed\n");
> > +                       break;
> > +               }
> 
> This may not require, as definition have it already when fail to set bank.

Feel free to drop this when applying.

Btw. the information printing is quite inconsistent in this stuff.

Best regards,
Marek Vasut

  reply	other threads:[~2014-07-03 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 20:53 [U-Boot] [PATCH] sf: Stop leaking memory Marek Vasut
2014-07-03 20:24 ` Jagan Teki
2014-07-03 21:04   ` Marek Vasut [this message]
2014-07-13 14:43     ` Jagan Teki

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=201407032304.28511.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