public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: Tegra board file deprecation schedule
Date: Mon, 30 Apr 2012 09:58:02 -0600	[thread overview]
Message-ID: <4F9EB68A.3080309@wwwdotorg.org> (raw)
In-Reply-To: <2573129.rORKuOVVxu@fb07-iapwap2>

On 04/30/2012 02:58 AM, Marc Dietrich wrote:
> Am Sonntag, 29. April 2012, 13:16:38 schrieb Stephen Warren:
...
>> The correct approach here is to remove all the I2C logic from the NVEC
>> driver and add I2C slave support to the real I2C driver. Then, NVEC
>> becomes just a protocol driver for the slave transactions. Then, there
>> is no clock to deal with.
> 
> you are absolutely right, but there is no i2c slave controller driver in 
> mainline yet and I don't want to submit the one nvidia already wrote [1]. 
> Maybe you can ask around if someone is willing to do this.

Someone has been assigned to work on this, but other priorities are in
the way. Unfortunately, I don't have any realistic ETA I can give right now.

  reply	other threads:[~2012-04-30 15:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 21:24 Tegra board file deprecation schedule Stephen Warren
2012-04-27 21:39 ` Olof Johansson
2012-04-27 21:53   ` Stephen Warren
2012-04-27 22:00     ` Fabio Estevam
2012-04-27 22:20       ` Stephen Warren
2012-04-28 16:09   ` Marc Dietrich
2012-04-28 21:34     ` Russell King - ARM Linux
2012-04-29 18:11       ` Marc Dietrich
2012-04-29 18:56         ` Russell King - ARM Linux
2012-04-29 19:16         ` Stephen Warren
2012-04-30  8:58           ` Marc Dietrich
2012-04-30 15:58             ` Stephen Warren [this message]
2012-04-30 16:51               ` Marc Dietrich
2012-04-29 19:21     ` Stephen Warren
2012-04-30  9:00       ` Marc Dietrich
2012-04-28 21:26 ` Lucas Stach
2012-04-29 19:25   ` 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=4F9EB68A.3080309@wwwdotorg.org \
    --to=swarren@wwwdotorg$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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