From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>,
"w.sang@pengutronix.de" <w.sang@pengutronix.de>
Cc: "khali@linux-fr.org" <khali@linux-fr.org>,
Stephen Warren <swarren@nvidia.com>,
"olof@lixom.net" <olof@lixom.net>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20
Date: Thu, 16 Aug 2012 12:37:59 +0530 [thread overview]
Message-ID: <502C9C4F.8090300@nvidia.com> (raw)
In-Reply-To: <502A817C.4000601@wwwdotorg.org>
On Tuesday 14 August 2012 10:19 PM, Stephen Warren wrote:
> On 08/14/2012 03:19 AM, Laxman Dewangan wrote:
>> Tegra20 i2c controller does not support the continue transfer
>> which implements the I2C_M_NOSTART functionality of i2c
>> protocol mangling.
>> Removing the I2C_M_NOSTART functionality for Tegra20.
>>
>> Signed-off-by: Laxman Dewangan<ldewangan@nvidia.com>
>> Reported-by: Stephen Warren<swarren@nvidia.com>
> Tested-by: Stephen Warren<swarren@wwwdotorg.org>
>
> Note that if I take Laxman's I2C driver clock patches through the Tegra
> tree, and Wolfram takes this patch through the I2C tree, there will be a
> very slight conflict, since adjacent lines are touched. However, the
> resolution is simple and obvious, so I think that's fine.
Stephen/Wolfram,
I have 2 more change to implement runtime PM and dynamic clock control
for fast clock which I have planned for 3.7.
I think it will be better if this also goes on same tree where the clock
related change are available to avoid the merge conflict.
next prev parent reply other threads:[~2012-08-16 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 9:19 Laxman Dewangan
2012-08-14 16:49 ` Stephen Warren
2012-08-16 7:07 ` Laxman Dewangan [this message]
2012-08-16 21:16 ` Stephen Warren
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=502C9C4F.8090300@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=w.sang@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
Powered by JetHome