From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Dietrich Subject: Re: [PATCH 1/3] ARM: tegra: paz00: add support for the embeddedcontroller Date: Tue, 25 Oct 2011 21:11:10 +0200 Message-ID: <1635238.5A42oCQuz5@ax5200p> References: <74CDBE0F657A3D45AFBB94109FB122FF173E1B4187@HQMAIL01.nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173E1B4187-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Stephen Warren Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Olof Johansson , Colin Cross , Laxman Dewangan List-Id: linux-tegra@vger.kernel.org On Monday 24 October 2011 22:06:46 Stephen Warren wrote: > Marc Dietrich wrote at Saturday, October 22, 2011 2:17 PM: > > This adds support for the embedded controller known as NVEC. The driver > > lives currently in the staging tree and we aim to promote it one level > > higher in the near future. > > > > The NVEC driver uses the I2C resources of the master controller for now > > until slave support is added to the i2c-tegra driver. > > I'm in two minds about this: > > The fact that the nvec driver accesses the I2C HW directly is a hack; that > should all happen in the I2C driver, and the nvec code should /just/ handle > the protocol to talk to the microcontroller. > > To that end, we're starting to bring on some more engineers internally who > will aim to upstream more of our downstream kernel. Part of this includes > upstreaming the I2C slave support in a more palatable fashion. I know those > engineers are keen in general to get started, but I can't yet estimate a > timescale for when this particular change will be ready. yeah, we just found out by chance that there exists a slave implementation at NVIDIA since last year :-( but it doesn't seem to be upstream ready yet (maybe should be merged with i2c- tegra driver).