From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>, w.sang@pengutronix.de
Cc: khali@linux-fr.org, swarren@nvidia.com, olof@lixom.net,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20
Date: Tue, 14 Aug 2012 10:49:00 -0600 [thread overview]
Message-ID: <502A817C.4000601@wwwdotorg.org> (raw)
In-Reply-To: <1344935949-26709-1-git-send-email-ldewangan@nvidia.com>
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.
next prev parent reply other threads:[~2012-08-14 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 9:19 [PATCH] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20 Laxman Dewangan
2012-08-14 9:19 ` Laxman Dewangan
2012-08-14 16:49 ` Stephen Warren [this message]
[not found] ` <502A817C.4000601-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-16 7:07 ` Laxman Dewangan
2012-08-16 7:07 ` Laxman Dewangan
[not found] ` <502C9C4F.8090300-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-16 21:16 ` Stephen Warren
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=502A817C.4000601@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=khali@linux-fr.org \
--cc=ldewangan@nvidia.com \
--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=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 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.