linux-kernel - Re: [PATCH] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <502C9C4F.8090300@nvidia.com>
Date:	Thu, 16 Aug 2012 12:37:59 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>,
	"w.sang@...gutronix.de" <w.sang@...gutronix.de>
CC:	"khali@...ux-fr.org" <khali@...ux-fr.org>,
	Stephen Warren <swarren@...dia.com>,
	"olof@...om.net" <olof@...om.net>,
	"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH] i2c: tegra: I2_M_NOSTART functionality not supported
 in Tegra20

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@...dia.com>
>> Reported-by: Stephen Warren<swarren@...dia.com>
> Tested-by: Stephen Warren<swarren@...dotorg.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/