From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] am335x: i2c: bus 2 issue
Date: Wed, 26 Mar 2014 08:00:43 -0400 [thread overview]
Message-ID: <5332C16B.5030408@ti.com> (raw)
In-Reply-To: <5332B5C1.2040005@compulab.co.il>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/26/2014 07:10 AM, Ilya Ledvich wrote:
> Hello, Recently I've found a problem with I2C bus 2 on AM335X based
> devices. Executing the command "i2c dev 2" in the u-boot CLI causes
> CPU reset. The issue is found on v2013.10, v2014.01 and
> v2014.04-rc1 and appears on BeagleBone and CM-T335 devices. Please
> see the log taken from BeagleBone:
The clocks aren't being enabled for i2c2 and at least on
beaglebone/etc neither is the pinmux, just i2c0/i2c1.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJTMsFrAAoJENk4IS6UOR1WNXsP/Rz9tLZbw91SBfSVWrf6Fjvk
hQf5OS6zYPAbPXO9L81ZeARXPsNmsC5tn7UANrr+AFwTw+7nUKjALNu5bygE4JRy
QxSn8JHaMounLgXy1Gp5VLQYY0dqqq6C8EuLCWbYsg8l0fIdciJae4br8+pHYcnh
/4wLigMuP4hbihLw7Zx3BYofgzlM/KNqF/Csrqy/UXPn9vKVzyimZRAOdSeLrEkP
rEO1In5s1hu6QkGepIb1pwIOdDYYZKJnAhhHFPZdb8U/sYFr5znEV6KtFQk3MrKy
QpUC4H0mdl1u87C+z071OX63Ubiclve455CGA94JtFoBAMLJIXGrY7mgu9o+Invz
a4lrfbrLeduhPtTpMO3ht0k833as/ok7jSgdz4xtzI8r5SoJOb9cO3Oj/gtFhbwu
29DWSGCfQWjWNspMncTbH9bcb/aXOjbRPbyYiv5af5hY0qIexi2Zn1cnPvsst+qh
SCZda5DSRbc9sGLl/xVhWoWfe6eFFUZbDD40RQk9LI6oQdYWeJp/MdCVhg8ukQwo
lJgUIyadbGG/HQ6hcZtapErhXRpBSB1nvc4t4UDihMFBbMZe5Q1O75mF0xbKe2xi
aH/rnrYomSBmnChm+3DVatheSLill06x01gExGfqySQHhm+ASBKltVmR3pjpLf9/
seu0MaggJ+KimuhOLSYL
=1b6v
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-03-26 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 11:10 [U-Boot] am335x: i2c: bus 2 issue Ilya Ledvich
2014-03-26 12:00 ` Tom Rini [this message]
2014-03-27 7:37 ` Ilya Ledvich
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=5332C16B.5030408@ti.com \
--to=trini@ti.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