From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Cc: Anna-Maria Gleixner
<anna-maria-WyZXDcvM26CzQB+pC5nmwQ@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Joseph Lo <josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM:tegra20-colibri-512.dts: Change tristate status for i2c pinmux
Date: Fri, 21 Jun 2013 10:24:33 -0600 [thread overview]
Message-ID: <51C47E41.6050609@wwwdotorg.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1306202302210.11096@dionysos>
On 06/20/2013 03:08 PM, Anna-Maria Gleixner wrote:
> The nvidia,tristate entry for the pinmux of i2c1 an i2c3 was set to
> tristate. This results in non working i2c, because the i2c pins are
> not actively driven. Set the entries to "driven".
Lucas, can you please comment on this patch? It sounds correct to me,
but I would have assumed you'd tested I2C already when you wrote the
original DT?
Oh actually, now that I look further, I see that tegra20-iris-512.dts
includes this file, and overrides some of the tristate values there.
What's the thinking behind that, and does this patch fit into it?
> diff --git a/arch/arm/boot/dts/tegra20-colibri-512.dtsi
> nvidia,pins = "rm";
> nvidia,function = "i2c1";
> nvidia,pull = <0>;
> - nvidia,tristate = <1>;
> + nvidia,tristate = <0>;
> };
> i2c3 {
> nvidia,pins = "dtf";
> nvidia,function = "i2c3";
> nvidia,pull = <0>;
> - nvidia,tristate = <1>;
> + nvidia,tristate = <0>;
> };
> i2cddc {
> nvidia,pins = "ddc";
next prev parent reply other threads:[~2013-06-21 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 21:08 [PATCH] ARM:tegra20-colibri-512.dts: Change tristate status for i2c pinmux Anna-Maria Gleixner
2013-06-21 16:24 ` Stephen Warren [this message]
[not found] ` <51C47E41.6050609-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-21 17:05 ` Lucas Stach
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=51C47E41.6050609@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=anna-maria-WyZXDcvM26CzQB+pC5nmwQ@public.gmane.org \
--cc=dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org \
--cc=josephl-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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