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, 22 May 2015 08:41:08 +0200 [thread overview]
Message-ID: <20150522064108.GS6325@pengutronix.de> (raw)
In-Reply-To: <555C2AEF.206@elfin.de>
On Wed, May 20, 2015 at 08:34:23AM +0200, Marcel Behlau wrote:
> Hi,
>
> i found the problem. The Pad Mux Register (0x20E008C and 0x20E0090)
> are not initialised. In both registers is a 0x00000005 (reset
> value), instead of 0x00000016. I think, i must specify the value of
> the mux register in the device tree, too. How can i do this?
You have to add a pinctrl node, like this:
&iomuxc {
imx6s-riotboard {
pinctrl_i2c1_2: i2c1grp-2 {
fsl,pins = <
MX6QDL_PAD_EIM_EB2__I2C2_SCL 0x4001b8b1
MX6QDL_PAD_EIM_D16__I2C2_SDA 0x4001b8b1
>;
};
};
};
...
&i2c1 {
pinctrl-0 = <&pinctrl_i2c1_2>;
};
See dts/Bindings/pinctrl/fsl,imx-pinctrl.txt and
dts/Bindings/pinctrl/fsl,imx6q-pinctrl.txt for a documentation what the
0x4001b8b1 value means. In short bit30 is for the SION bit and the
remaing bits are for the PAD_CTL register.
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
prev parent reply other threads:[~2015-05-22 6:41 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
2015-05-20 6:34 ` Marcel Behlau
2015-05-22 6:41 ` Sascha Hauer [this message]
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=20150522064108.GS6325@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