From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>, w.sang@pengutronix.de
Cc: olof@lixom.net, khali@linux-fr.org, ben-linux@fluff.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 0/4] i2c: tegra: required clock support for controller
Date: Wed, 15 Aug 2012 10:58:04 -0600 [thread overview]
Message-ID: <502BD51C.4010204@wwwdotorg.org> (raw)
In-Reply-To: <5022A89F.8070604@wwwdotorg.org>
On 08/08/2012 11:57 AM, Stephen Warren wrote:
> On 08/08/2012 01:51 AM, Laxman Dewangan wrote:
>> The Tegra's i2c controller required two clock sources for proper
>> operation named as div-clk and fast-clk.
>>
>> Adding support to make sure that driver will get these clocks and
>> enable before any transfer and disable after transfer completed.
>
> This works fine on Cardhu and Ventana for me. I'll apply it once I get
> an ack from Wolfram to take the I2C driver patch through the Tegra tree.
I haven't heard from Wolfram, but since the I2C driver patch is pretty
trivial, and pretty much has to go through the Tegra tree due to
dependencies on other Tegra patches, I went ahead and applied this
series to Tegra's for-3.7/clock branch.
next prev parent reply other threads:[~2012-08-15 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 7:51 [PATCH 0/4] i2c: tegra: required clock support for controller Laxman Dewangan
2012-08-08 7:51 ` [PATCH 1/4] ARM: tegra: clock: add i2c fast clock entry in clock table Laxman Dewangan
2012-08-08 7:51 ` [PATCH 2/4] i2c: tegra: pass proper name for getting clock Laxman Dewangan
2012-08-08 7:51 ` [PATCH 3/4] ARM: tegra: clock: add connection name in i2c clock entry Laxman Dewangan
2012-08-08 7:51 ` [PATCH 4/4] ARM: tegra: clock: remove unused clock entry for i2c Laxman Dewangan
2012-08-08 10:11 ` [PATCH 0/4] i2c: tegra: required clock support for controller Laxman Dewangan
2012-08-08 17:57 ` Stephen Warren
2012-08-15 16:58 ` Stephen Warren [this message]
2012-08-16 8:22 ` Wolfram Sang
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=502BD51C.4010204@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=ben-linux@fluff.org \
--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=olof@lixom.net \
--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