linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: khali@linux-fr.org, w.sang@pengutronix.de, ben-linux@fluff.org,
	swarren@wwwdotorg.org, olof@lixom.net
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org,
	Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 2/4] i2c: tegra: add PROTOCOL_MANGLING as supported functionality.
Date: Tue, 5 Jun 2012 18:39:58 +0530	[thread overview]
Message-ID: <1338901800-23968-3-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1338901800-23968-1-git-send-email-ldewangan@nvidia.com>

The Tegra i2c driver supports the I2C_M_IGNORE_NAK and hence
returning I2C_FUNC_PROTOCOL_MANGLING as supported functionality.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
 drivers/i2c/busses/i2c-tegra.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
index fa92396..36d8725 100644
--- a/drivers/i2c/busses/i2c-tegra.c
+++ b/drivers/i2c/busses/i2c-tegra.c
@@ -572,7 +572,8 @@ static int tegra_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg msgs[],
 
 static u32 tegra_i2c_func(struct i2c_adapter *adap)
 {
-	return I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL | I2C_FUNC_10BIT_ADDR;
+	return I2C_FUNC_I2C | I2C_FUNC_SMBUS_EMUL | I2C_FUNC_10BIT_ADDR |
+		I2C_FUNC_PROTOCOL_MANGLING;
 }
 
 static const struct i2c_algorithm tegra_i2c_algo = {
-- 
1.7.1.1

  parent reply	other threads:[~2012-06-05 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 13:09 [PATCH 0/4] i2c: tegra: Bug fixes, cleanups and M_NOSTART support Laxman Dewangan
2012-06-05 13:09 ` [PATCH 1/4] i2c: tegra: make sure register writes completes Laxman Dewangan
     [not found]   ` <1338901800-23968-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-12  7:54     ` Wolfram Sang
     [not found]       ` <20120612075422.GB9230-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-06-12 10:16         ` Laxman Dewangan
     [not found]           ` <4FD71709.9040208-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-12 16:07             ` Stephen Warren
2012-06-05 13:09 ` Laxman Dewangan [this message]
     [not found] ` <1338901800-23968-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-05 13:09   ` [PATCH 3/4] i2c: tegra: support for I2C_M_NOSTART functionality Laxman Dewangan
2012-06-05 16:14   ` [PATCH 0/4] i2c: tegra: Bug fixes, cleanups and M_NOSTART support Stephen Warren
     [not found]     ` <4FCE3078.1030008-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-05 17:07       ` Laxman Dewangan
     [not found]         ` <4FCE3CD8.8060502-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-12  8:50           ` Wolfram Sang
     [not found]             ` <20120612085040.GC9230-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-06-12 16:05               ` Stephen Warren
2012-06-05 13:10 ` [PATCH 4/4] i2c: tegra: make all resource allocation through devm_* Laxman Dewangan

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=1338901800-23968-3-git-send-email-ldewangan@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=ben-linux@fluff.org \
    --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@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;
as well as URLs for NNTP newsgroup(s).