Thread (4 messages) 4 messages, 2 authors, 2012-08-17

Re: [PATCH] i2c: tegra: dynamically control fast clk

From: Stephen Warren <hidden>
Date: 2012-08-17 19:08:02
Also in: linux-tegra, lkml

On 08/17/2012 12:45 PM, Laxman Dewangan wrote:
On Saturday 18 August 2012 12:11 AM, Stephen Warren wrote:
quoted
On 08/17/2012 01:48 AM, Laxman Dewangan wrote:
quoted
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<redacted>
---
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.
For any I2C-related changes I take through the Tegra tree, basing them
on top of for-3.7/drivers-i2c would be best. Feel free to send both
patches together again if that's easiest.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help