On Fri, 2010-09-24 at 23:45 +0200, Loïc Minier wrote:
Fix missing cs arg to gpmc_prefetch_reset() when
CONFIG_MTD_NAND_OMAP_PREFETCH_DMA=y which caused a build failure since
948d38e799f0ab87cf8ed9113fcdaaee61acf321:
drivers/mtd/nand/omap2.c: In function 'omap_nand_dma_transfer':
TWL4030/TPS65950 is a multi-function device with integrated charger,
which allows charging from AC or USB. This driver enables the
charger and provides several monitoring functions.
Tested on OMAP3 Pandora board.
Signed-off-by: Grazvydas Ignotas nota...@gmail.com
---
This is v3 of BCI charger
This patch adds a definition of the OMAP1 camera interface platform device,
and a function that allows for providing a board specific platform data.
The device will be used with the upcoming OMAP1 SoC camera interface driver.
Created and tested against linux-2.6.36-rc5 on Amstrad Delta.
Hi Kevin,
I am interested in runtime pm implementation on OMAP3, and
want to test this function on omap3-based beagle board, but seems
no devices on omap3 Soc can support runtime pm(no __pm_runtime_*
message found from 'dmesg' and rpm debug option is surely enabled)
now after trying the two omap
Hi Thara,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Thara Gopinath
Sent: Saturday, September 25, 2010 6:21 PM
To: linux-omap@vger.kernel.org
Cc: khil...@deeprootsystems.com; p...@pwsan.com; b-cous...@ti.com;
Hi all,
Today's linux-next merge of the net tree got a conflict in
arch/arm/mach-omap2/board-zoom-peripherals.c between commit
6db649c505ddc6665176807c16745b9e01cf5031 (omap: mmc: extended to pass
host capabilities from board file) from the omap tree and commits
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in
arch/arm/mach-omap2/devices.c between commit
5d14f2792f9d63c5d25903bd048017c4b53c7d9a (omap: crypto: updates to
enable omap aes) from the omap tree and commit
b744c679f62b368cb94c21c1dcd4618e42d88d63 (crypto: updates to
On Mon, Sep 27, 2010 at 02:33:00PM +1000, Stephen Rothwell wrote:
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in
arch/arm/mach-omap2/devices.c between commit
5d14f2792f9d63c5d25903bd048017c4b53c7d9a (omap: crypto: updates to
enable omap aes) from the omap tree and
