On Fri, Feb 12, 2010 at 2:49 AM, Tony Lindgren t...@atomide.com wrote:
* Tony Lindgren t...@atomide.com [100211 12:43]:
* Vimal Singh vimal.neww...@gmail.com [100210 21:16]:
From: Vimal Singh vimalsi...@ti.com
This patch adds 'board-zoom-flash.c', which could be utilized
by boards
-Original Message-
From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
Sent: Friday, February 12, 2010 4:14 PM
To: ext Tony Lindgren
Cc: ext Mike Rapoport; Hiremath, Vaibhav; linux-omap@vger.kernel.org
Subject: Re: Moving board patches from DSS2 to linux-omap
On Thu,
-Original Message-
From: Weng, Wending [mailto:ww...@rheinmetall.ca]
Sent: Friday, February 12, 2010 9:51 PM
To: Hiremath, Vaibhav
Cc: linux-omap@vger.kernel.org
Subject: omap3 camera interface driver
Hi Hiremath,
I used to work with BSP from TI, there is driver
-Original Message-
From: Hiremath, Vaibhav
Sent: Saturday, February 13, 2010 4:04 PM
To: 'Tomi Valkeinen'; ext Tony Lindgren
Cc: ext Mike Rapoport; linux-omap@vger.kernel.org
Subject: RE: Moving board patches from DSS2 to linux-omap
-Original Message-
From: Tomi
From: Vaibhav Hiremath hvaib...@ti.com
This series of patchset adds platform hook-up interface for I2C based
devices to AM3517 -
- Real Time Clock (S35390A)
- I2C GPIO Expander (TCA6416)
Changes from last submission (V2) -
- Added seperate function for RTC init, to handle
From: Vaibhav Hiremath hvaib...@ti.com
Add platform hook-up interface to support I2C based GPIo expander
(TCA6416).
There are 3 instances of I2C Expander on AM3517EVM,
- One is over I2C-2 mounted on Base board
- Two are over I2C3 mounted on UI Card
Signed-off-by: Vaibhav
From: Vaibhav Hiremath hvaib...@ti.com
Add platform hook-up interface to support RTC driver (S35390A).
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
---
arch/arm/mach-omap2/board-am3517evm.c | 39 +
1 files changed, 39 insertions(+), 0 deletions(-)
diff
On Mon, Feb 8, 2010 at 5:57 PM, Tomi Valkeinen tomi.valkei...@nokia.com wrote:
Here are a bunch of patches that change the DSS2 driver's driver model a bit.
This change was triggered by trying to support new hardware, and realizing
that
the current model just won't work.
Currently the
The ADS7846/TSC2046 touchscreen controllers can (and usually are)
connected to various regulators for power, so add regulator support.
Valid regulator will now be required, so boards without complete
regulator setup should either disable regulator framework or enable
CONFIG_REGULATOR_DUMMY.
On Sat, Feb 13, 2010 at 06:31:54PM +0200, Grazvydas Ignotas wrote:
The ADS7846/TSC2046 touchscreen controllers can (and usually are)
connected to various regulators for power, so add regulator support.
Valid regulator will now be required, so boards without complete
regulator setup should
Just one nitpicking comment below:
On Sat, Feb 13, 2010 at 6:31 PM, Grazvydas Ignotas nota...@gmail.com wrote:
The ADS7846/TSC2046 touchscreen controllers can (and usually are)
connected to various regulators for power, so add regulator support.
Valid regulator will now be required, so boards
On Sat, Feb 13, 2010 at 09:40:26PM +0200, Mike Rapoport wrote:
On Sat, Feb 13, 2010 at 6:31 PM, Grazvydas Ignotas nota...@gmail.com wrote:
+ ts-reg = regulator_get(spi-dev, vcc);
vcc is way too generic name. What about vcc-ts or vcc-touch?
This should be OK as-is - the general style
On Thu, Feb 11, 2010 at 7:57 PM, Michael Trimarchi
mich...@panicking.kicks-ass.org wrote:
Use an hub with external power and connect the hub to the OTG and the device
to the HUB.
Is it the same?
Uhm... what do you think how I attached a hard disk and a network
device to the Beagle's USB OTG
13 matches
Mail list logo
