From: Jan Weitzel <J.Weitzel@phytec.de>
To: andy.green@linaro.org
Cc: linux-omap@vger.kernel.org, patches@linaro.org, andy@warmcat.com,
tony@atomide.com, peter.maydell@linaro.org, ben-linux@fluff.org
Subject: Re: [PATCH] ARM: omap4: i2c reset regs postidle
Date: Mon, 16 May 2011 09:56:08 +0200 [thread overview]
Message-ID: <1305532568.11112.4.camel@lws-weitzel> (raw)
In-Reply-To: <4DB01F5B.5080607@linaro.org>
Am Donnerstag, den 21.04.2011, 13:13 +0100 schrieb Andy Green:
> On 04/21/2011 12:47 PM, Somebody in the thread at some point said:
> > Without OMAP_I2C_FLAG_RESET_REGS_POSTIDLE I got i2c controller
> > timeouts on each accsess after an NACK message.
> > Taking this flag fix it.
>
> Ahhh that will explain why if you accidentally configure LM75 system
> monitor support, which isn't there on Panda, the I2C controllers die
> slowly on boot. Good catch!
Can I get an Acked-by ?
Jan
next prev parent reply other threads:[~2011-05-16 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 11:47 [PATCH] ARM: omap4: i2c reset regs postidle Jan Weitzel
2011-04-21 12:13 ` Andy Green
2011-05-16 7:56 ` Jan Weitzel [this message]
2011-05-16 8:13 ` Andy Green
2011-05-16 9:18 ` [PATCH v2] " Jan Weitzel
2011-05-16 17:16 ` Cousson, Benoit
2011-05-17 9:26 ` [PATCH v3] " Jan Weitzel
2011-05-17 14:12 ` Kevin Hilman
2011-05-18 13:07 ` Jan Weitzel
2011-05-18 14:09 ` Kevin Hilman
2011-06-14 10:05 ` [RFC] ARM: OMAP2+ i2c NACK without STP Jan Weitzel
2011-06-14 10:24 ` Tony Lindgren
[not found] ` <20110614102409.GN3352-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2011-06-14 10:54 ` [PATCH] " Jan Weitzel
2011-12-27 14:48 ` T Krishnamoorthy, Balaji
[not found] ` <CANrkHUZ530H+0+YKy2QJPFbwUQ1zqD=OaSrF6ByTbpx6eU421Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-04 0:07 ` Kevin Hilman
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=1305532568.11112.4.camel@lws-weitzel \
--to=j.weitzel@phytec.de \
--cc=andy.green@linaro.org \
--cc=andy@warmcat.com \
--cc=ben-linux@fluff.org \
--cc=linux-omap@vger.kernel.org \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).