linux-kernel - Re: [PATCH] i2c: tegra: dynamically control fast clk

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 for Android: free password hash cracker in your pocket

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

Message-ID: <502E914A.1030906@nvidia.com>
Date:	Sat, 18 Aug 2012 00:15:30 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	"khali@...ux-fr.org" <khali@...ux-fr.org>,
	"ben-linux@...ff.org" <ben-linux@...ff.org>,
	"w.sang@...gutronix.de" <w.sang@...gutronix.de>,
	Stephen Warren <swarren@...dia.com>,
	"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: dynamically control fast clk

On Saturday 18 August 2012 12:11 AM, Stephen Warren wrote:
> On 08/17/2012 01:48 AM, Laxman Dewangan wrote:
>> Tegra I2C driver enables the fast clock during initialization
>> and does not disable till driver removed.
>> Enable this clock before transfer and disable after transfer done.
>>
>> Signed-off-by: Laxman Dewangan<ldewangan@...dia.com>
>> ---
>> This patch is on top of the clock chnages which is in Tegra sub system and
>> based on
>>   i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20
>> So recommend to go on tegra sub-system.
> What exactly is this patch based on? I checked out Tegra's
> for-3.7/drivers-i2c, cherry-picked the M_NOSTART patch you mentioned,
> and attempted to apply this patch. It doesn't apply. Same if I don't
> cherry-pick the M_NOSTART patch, and same for next-20120816 with/without
> the M_NOSTART patch.

Then It seems I need to create the patch again and send it.  The 
M_NOSTART patch was on tot before clock related change and that is the 
reason it is not applying.
Should I re-send these two patches together as 1/2 and 2/2 to maintain 
sequence?
I can create based on your clock tree.


--
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/