From: Wolfram Sang <w.sang@pengutronix.de>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: khali@linux-fr.org, swarren@nvidia.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20
Date: Sun, 19 Aug 2012 08:33:14 +0200 [thread overview]
Message-ID: <20120819063314.GA2147@pengutronix.de> (raw)
In-Reply-To: <1345317467-22258-1-git-send-email-ldewangan@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Sun, Aug 19, 2012 at 12:47:46AM +0530, 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 support for Tegra20.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> Changes from V1:
> - make the hw feature structure as part of tegra device structure in
> place of copying the member.
> - Remove check for extra M_NOSTART flag if it is not supported in xfer function.
>
> Please note that this should go on tegra common clock source tree to avoid conflicts.
Looks good to me regarding the I2C part:
Reviewed-by: Wolfram Sang <w.sang@pengutronix.de>
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-19 6:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 19:17 [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20 Laxman Dewangan
[not found] ` <1345317467-22258-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-18 19:17 ` [PATCH V2 2/2] i2c: tegra: dynamically control fast clk Laxman Dewangan
2012-08-19 6:33 ` Wolfram Sang [this message]
2012-08-20 17:15 ` [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20 Stephen Warren
[not found] ` <503270B3.7000007-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-20 17:10 ` Laxman Dewangan
[not found] ` <50326F82.3050503-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-20 17:36 ` 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=20120819063314.GA2147@pengutronix.de \
--to=w.sang@pengutronix.de \
--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=swarren@nvidia.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).