All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot warnings on Nokia N900
Date: Thu, 15 Jan 2015 10:18:01 +0100	[thread overview]
Message-ID: <201501151018.01750@pali> (raw)
In-Reply-To: <201501151007.05140@pali>

On Thursday 15 January 2015 10:07:05 Pali Roh?r wrote:
> Hello,
> 
> when starting U-Boot (from git master) on Nokia N900 it show
> lot of these lines on N900 screen:
> 
> Timed out in wait_for_event: status=0000
> Check if pads/pull-ups of bus 1 are properly configured
> Timed out in wait_for_event: status=0000
> Check if pads/pull-ups of bus 1 are properly configured
> ...
> i2c_read (addr phase): pads on bus 1 probably not configured
> (status=0x10)
> i2c_write: timeout writing last byte!
> 
> But booting linux kernel working without problem. What above
> warning messages means? They were not in U-Boot 2013.04
> version.

Ok, these warning/error lines are generated by this code:

	/* reset lp5523 led */
	i2c_set_bus_num(1);
	state = 0xff;
	i2c_write(0x32, 0x3d, 1, &state, 1);
	i2c_set_bus_num(0);

in function misc_init_r() in file board/nokia/rx51/rx51.c

Above code worked fine in U-Boot 2013.04 and now in U-Boot from 
git master it generates warnings/errors. Why?

-- 
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150115/bd4980ad/attachment.pgp>

  reply	other threads:[~2015-01-15  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  9:07 [U-Boot] U-Boot warnings on Nokia N900 Pali Rohár
2015-01-15  9:18 ` Pali Rohár [this message]
2015-01-20 21:37   ` 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=201501151018.01750@pali \
    --to=pali.rohar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.