From: "Cousson, Benoit" <b-cousson@ti.com>
To: Jan Weitzel <j.weitzel@phytec.de>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"andy.green@linaro.org" <andy.green@linaro.org>,
"patches@linaro.org" <patches@linaro.org>,
"andy@warmcat.com" <andy@warmcat.com>,
"tony@atomide.com" <tony@atomide.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"ben-linux@fluff.org" <ben-linux@fluff.org>
Subject: Re: [PATCH v2] ARM: omap4: i2c reset regs postidle
Date: Mon, 16 May 2011 19:16:05 +0200 [thread overview]
Message-ID: <4DD15BD5.9010303@ti.com> (raw)
In-Reply-To: <1305537524-24753-1-git-send-email-j.weitzel@phytec.de>
Hi Jan,
On 5/16/2011 11:18 AM, Jan Weitzel wrote:
> Without OMAP_I2C_FLAG_RESET_REGS_POSTIDLE I got i2c controller
> timeouts on each accsess after an NACK message.
> Taking this flag fix it.
>
> This patch is on top of the i2c feature implementation flags
> patches
Could you please give us more information and potentially provide a link
to the patches you are referring to?
It will help us assessing the need for such flag in the hwmod data.
Please note that the changelog will stay forever in the GIT tree, so you
should avoid using "the patch" or making reference to something that is
not an existing commit id or email archive.
You should fix as well the typo.
Thanks,
Benoit
next prev parent reply other threads:[~2011-05-16 17:16 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
2011-05-16 8:13 ` Andy Green
2011-05-16 9:18 ` [PATCH v2] " Jan Weitzel
2011-05-16 17:16 ` Cousson, Benoit [this message]
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=4DD15BD5.9010303@ti.com \
--to=b-cousson@ti.com \
--cc=andy.green@linaro.org \
--cc=andy@warmcat.com \
--cc=ben-linux@fluff.org \
--cc=j.weitzel@phytec.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.