public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "khali@linux-fr.org" <khali@linux-fr.org>,
	"w.sang@pengutronix.de" <w.sang@pengutronix.de>,
	"ben-linux@fluff.org" <ben-linux@fluff.org>,
	"olof@lixom.net" <olof@lixom.net>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 0/4] i2c: tegra: Bug fixes, cleanups and M_NOSTART support
Date: Tue, 5 Jun 2012 22:37:36 +0530	[thread overview]
Message-ID: <4FCE3CD8.8060502@nvidia.com> (raw)
In-Reply-To: <4FCE3078.1030008@wwwdotorg.org>

On Tuesday 05 June 2012 09:44 PM, Stephen Warren wrote:
> On 06/05/2012 07:09 AM, Laxman Dewangan wrote:
>> This patch series having the:
>> - Handling of late register write due to Tegra PPSB design.
>> - support for I2C_M_NOSTART
>> - Use devm_* for all allocation.
> The series,
>
> Acked-by: Stephen Warren<swarren@wwwdotorg.org>
>
> Note that patch 4 touches context adjacent to Prashant's "i2c: tegra:
> Add clk_prepare/clk_unprepare" patch, which I hope to take through the
> Tegra tree since it's a requirement for the Tegra common clock
> conversion. I don't think this will cause any significant conflict, but
> perhaps it's worth resolving it explicitly.
>
> Wolfram, perhaps we should put these 4 patches and Prashan'ts into their
> own topic branch so that you can merge it into the I2C tree, and I can
> merge it into the Tegra tree too? Or, I can take everything through
> Tegra if you want, and ack it.
>
> Laxman, do you expect any more I2C-related changes this kernel cycle?
I have two more changes in plan:
-I2c controller require two clock source and the fixes towards that. 
This can go on Tegra tree as changes are require in 
mach-tegra/tegra30_clock.c, tegra20_clock.c files also.

- Run time PM support but can be done later.








  reply	other threads:[~2012-06-05 17:15 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
2012-06-12  7:54   ` Wolfram Sang
2012-06-12 10:16     ` Laxman Dewangan
2012-06-12 16:07       ` Stephen Warren
2012-06-05 13:09 ` [PATCH 2/4] i2c: tegra: add PROTOCOL_MANGLING as supported functionality Laxman Dewangan
2012-06-05 13:09 ` [PATCH 3/4] i2c: tegra: support for I2C_M_NOSTART functionality Laxman Dewangan
2012-06-05 13:10 ` [PATCH 4/4] i2c: tegra: make all resource allocation through devm_* Laxman Dewangan
2012-06-05 16:14 ` [PATCH 0/4] i2c: tegra: Bug fixes, cleanups and M_NOSTART support Stephen Warren
2012-06-05 17:07   ` Laxman Dewangan [this message]
2012-06-12  8:50     ` Wolfram Sang
2012-06-12 16:05       ` Stephen Warren

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=4FCE3CD8.8060502@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