From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marcel Behlau <marcel.behlau@elfin.de>
Cc: barebox@lists.infradead.org,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Usage of i2c_-Tools in Barebox
Date: Fri, 8 May 2015 07:12:42 +0200 [thread overview]
Message-ID: <20150508051242.GV6325@pengutronix.de> (raw)
In-Reply-To: <554B4B63.7020301@elfin.de>
On Thu, May 07, 2015 at 01:24:19PM +0200, Marcel Behlau wrote:
> Hi,
>
> many thanks for your help. I activated the i2c devices in the device
> tree, the pinctrl is already done in the imx6q.dtsi, which is
> included. The used pins are identically with the used pins on the
> SBC. devinfo told me, that the driver "i2c-fsl" is loaded. After
> rebuild barebox, it's possible to probe the bus, but the command
> only answered with an timeout:
>
> barebox@Phytec phyFLEX-i.MX6 Quad Carrier-Board:/ i2c_probe 1 83 83
> probing i2c range 0x53 - 0x53 :
> i2c2: <i2c_fsl_bus_busy> timeout waiting for I2C bus busy
I *think* this means that the levels on the bus do not properly follow
what the controller wants to do. Maybe pullup missing? An oscilloscope
might help here.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-05-08 5:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:56 Marcel Behlau
2015-05-05 15:54 ` Sascha Hauer
2015-05-06 7:12 ` Uwe Kleine-König
2015-05-07 11:24 ` Marcel Behlau
2015-05-08 5:12 ` Sascha Hauer [this message]
2015-05-20 6:34 ` Marcel Behlau
2015-05-22 6:41 ` Sascha Hauer
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=20150508051242.GV6325@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=marcel.behlau@elfin.de \
--cc=u.kleine-koenig@pengutronix.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