public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] fsl: sys_eeprom: Fix 'may be used uninitialized' warningп
Date: Tue, 1 Sep 2009 22:27:41 +0400	[thread overview]
Message-ID: <20090901182741.GA18171@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <4A9D6356.9090304@freescale.com>

On Tue, Sep 01, 2009 at 01:09:26PM -0500, Timur Tabi wrote:
> Anton Vorontsov wrote:
> 
> > -	for (i = 0, p = &e; i < sizeof(e); i += 8, p += 8) {
> > +	do {
> >  		ret = i2c_write(CONFIG_SYS_I2C_EEPROM_ADDR, i, CONFIG_SYS_I2C_EEPROM_ADDR_LEN,
> > -			p, min((sizeof(e) - i), 8));
> > +			(void *)&e + i, min((sizeof(e) - i), 8));
> >  		if (ret)
> >  			break;
> >  		udelay(5000);	/* 5ms write cycle timing */
> > -	}
> > +		i += 8;
> > +	} while (i < sizeof(e));
> 
> Or we could remove the loop altogether and just do the write in one shot.  Is there any reason to believe that any of Freescale's 8[356]xx boards can't handle a large I2C block write of about 50 bytes or so?

I guess "udelay(5000);	/* 5ms write cycle timing */" hints that
it's EEPROM chip dependant, so has nothing to do with i2c controller
capabilities.

Thanks,

-- 
Anton Vorontsov
email: cbouatmailru at gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2009-09-01 18:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 16:59 [U-Boot] [PATCH 2/2] fsl: sys_eeprom: Fix 'may be used uninitialized' warning Anton Vorontsov
2009-09-01 17:30 ` Kumar Gala
2009-09-01 17:38   ` Anton Vorontsov
2009-09-01 17:59     ` [U-Boot] invalid core multipliers? Kári Davíðsson
2009-09-04 20:57       ` Wolfgang Denk
2009-09-01 18:06     ` [U-Boot] [PATCH 2/2] fsl: sys_eeprom: Fix 'may be used uninitialized' warning Anton Vorontsov
2009-09-01 18:09       ` Timur Tabi
2009-09-01 18:27         ` Anton Vorontsov [this message]
2009-09-01 19:22       ` Wolfgang Denk
2009-09-01 18:16 ` Wolfgang Denk
2009-09-01 18:29   ` Anton Vorontsov
2009-09-01 19:42     ` Wolfgang Denk
2009-09-01 18:38 ` Timur Tabi

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=20090901182741.GA18171@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.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