Hi all,
Last week I posted some more omap io.h clean-up patches to the linux-omap
list [1], and started looking at what it would take to reclaim lost address
space on top of the io.h clean-up patches.
Looks like we should be able to reclaim about 454MB of the 640MB
of the lost IO address space
On Friday 26 June 2009 07:27:15 Dongsoo, Nathaniel Kim wrote:
Hello,
On Fri, Jun 26, 2009 at 7:43 AM, Gary Thomasg...@mlbassoc.com wrote:
Still trying to wrap my head around the OMAP/34xx camera support.
I need to use the TVP5150 sensor/controller, but the existing
driver uses
-Original Message-
From: Shilimkar, Santosh
Sent: Tuesday, May 12, 2009 6:11 PM
To: linux-omap@vger.kernel.org
Cc: Shilimkar, Santosh
Subject: [PATCH] [RFC] OMAP4: sDMA: Update the request lines
and new registers.
This patch updates the platform dma.h with new dma request lines
* Shilimkar, Santosh santosh.shilim...@ti.com [090626 09:39]:
-Original Message-
From: Shilimkar, Santosh
Sent: Tuesday, May 12, 2009 6:11 PM
To: linux-omap@vger.kernel.org
Cc: Shilimkar, Santosh
Subject: [PATCH] [RFC] OMAP4: sDMA: Update the request lines
and new
On Fri, 26 Jun 2009, Tony Lindgren wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [090626 09:39]:
-Original Message-
From: Shilimkar, Santosh
Sent: Tuesday, May 12, 2009 6:11 PM
To: linux-omap@vger.kernel.org
Cc: Shilimkar, Santosh
Subject: [PATCH] [RFC] OMAP4:
/*
*/
/* Hardware registers for LCD DMA */
--
Tony,
Can you also check this patch and
UART4 patch:
http://www.spinics.net/lists/linux-omap/msg14161.html
If you ack these
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony Lindgren
Sent: Friday, June 26, 2009 11:56 AM
To: linux-omap@vger.kernel.org
Cc: linux-arm-ker...@lists.arm.linux.org.uk
Subject: RFC: Reclaim address space on
On Fri, Jun 26, 2009 at 09:25:40AM +0300, Tony Lindgren wrote:
Hi all,
Last week I posted some more omap io.h clean-up patches to the linux-omap
list [1], and started looking at what it would take to reclaim lost address
space on top of the io.h clean-up patches.
Looks like we should be
Hi,
On Tue, 23 Jun 2009, Woodruff, Richard wrote:
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Tuesday, June 23, 2009 3:05 PM
Looks like the significant difference is the use of CLKCTRL = 0x2 (+
AUTOCOUNT). Maybe there is some SDRC bug related to CLKCTRL = 0x2 that
causes this
* Shilimkar, Santosh santosh.shilim...@ti.com [090626 10:45]:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony Lindgren
Sent: Friday, June 26, 2009 11:56 AM
To: linux-omap@vger.kernel.org
Cc:
* Ben Dooks ben-li...@fluff.org [090626 11:37]:
On Fri, Jun 26, 2009 at 09:25:40AM +0300, Tony Lindgren wrote:
Hi all,
Last week I posted some more omap io.h clean-up patches to the linux-omap
list [1], and started looking at what it would take to reclaim lost address
space on top of
* Tony Lindgren t...@atomide.com [090626 11:58]:
* Ben Dooks ben-li...@fluff.org [090626 11:37]:
On Fri, Jun 26, 2009 at 09:25:40AM +0300, Tony Lindgren wrote:
Hi all,
Last week I posted some more omap io.h clean-up patches to the linux-omap
list [1], and started looking at what it
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Branch in linux-omap: master
Initial commit ID (Likely to change): 5234fb35f6b3313805d5d1014456b50159935edc
PatchWorks
http://patchwork.kernel.org/patch/32467/
Git (Likely to change, and takes a while to get mirrored)
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Branch in linux-omap: master
Initial commit ID (Likely to change): 947478830b2046913ef6cbe64243a4c6530ff835
PatchWorks
http://patchwork.kernel.org/patch/32468/
Git (Likely to change, and takes a while to get mirrored)
Hello,
Kevin Hilman wrote:
From: Rajendra Nayak rna...@ti.com
Because of OMAP off-mode, powerdomain can go off when I2C is idle.
Save enough state, and do a re-init for each transfer.
Additional save/restore state added by Jagadeesh Bhaskar Pakaravoor
(SYSC_REG) and Aaro Koskinen (wakeup
ARM TCM (Tightly-Coupled Memory) support v1
For details about TCM and this specific interface for
Linux, see the patch, which includes a document in
Documentation/arm/tcm.txt
I expect a few iterations on this, so it's not like this
is a merge candidate. Wait for v5 or so...
However it works.
This adds the TCM interface to Linux, when active, it will
detect and report TCM memories and sizes early in boot if
present, introduce generic TCM memory handling, provide a
generic TCM memory pool and select TCM memory for the U300
platform.
I use arch/arm/include/asm/cputype.h that defines a
The clock stabilization delay post a M2 divider change is needed
even before a SDRC interface clock re-enable and not only before
jumping back to SDRAM.
Signed-off-by: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap2/sram34xx.S |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Hello,
I'm afraid this patch needs more work. The optimized restoration of
chconf can cause occasionally errors with off mode if multiple chip
selects are in use. In practice it is needed to restore all CHxCONF
registers, not just the one by a specific chip select.
ext Kevin Hilman wrote:
Add checks to prevent NULL pointer exception in case no
OTG transceiver has been selected. i.e. musb-xceiv == NULL
Signed-off-by: Roger Quadros ext-roger.quad...@nokia.com
---
drivers/usb/musb/musb_core.c |3 ++-
drivers/usb/musb/omap2430.c |7 +--
2 files changed, 7 insertions(+),
Added REGULATOR, MMC and updated default CMDLINE. Linux-omap
now boots on RX51.
Signed-off-by: Roger Quadros ext-roger.quad...@nokia.com
---
arch/arm/configs/rx51_defconfig | 294 +++
1 files changed, 172 insertions(+), 122 deletions(-)
diff --git
Aaro Koskinen aaro.koski...@nokia.com writes:
Kevin Hilman wrote:
From: Rajendra Nayak rna...@ti.com
Because of OMAP off-mode, powerdomain can go off when I2C is idle.
Save enough state, and do a re-init for each transfer.
Additional save/restore state added by Jagadeesh Bhaskar Pakaravoor
But in user space there is nothing changed having access to
device and control them.
As you know, subdev and int-device is all about how to bind
interface(or host?) and device and make them communicated each other.
But using subdev device driver with int-device supporting interface
(or
sawsd wang sawsdw...@gmail.com writes:
From c1aba8ba7af3ddd16346d95795bda71e65baa4d0 Mon Sep 17 00:00:00 2001
From: Chunqiu Wang cqw...@motorola.com
Date: Wed, 24 Jun 2009 06:48:52 +0800
Subject: [PATCH] Support OMAP3 VC adaptation with different Power IC
Current OMAP SmartReflex driver
Hi Paul,
On Tue, 23 Jun 2009, Woodruff, Richard wrote:
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Tuesday, June 23, 2009 3:05 PM
Looks like the significant difference is the use of CLKCTRL = 0x2 (+
AUTOCOUNT). Maybe there is some SDRC bug related to CLKCTRL = 0x2 that
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Tony Lindgren
Last week I posted some more omap io.h clean-up patches to
the linux-omap
list [1], and started looking at what it would take to
reclaim lost address
space on top of the
This patch series enables support for IVA2 and SECURE
WDTs, available on omap34xx.
The WDTs will be accessible (when present on device) through:
MPU:/dev/watchdog
SECURE: /dev/watchdog_secure
IVA2: /dev/watchdog_iva2
Tested on Zoom1 OMAP3 platform, compile-tested for OMAP2
Signed-off-by:
This patch adds support for IVA2 and SECURE WDTs in the omap_wdt
driver for omap34xx family. SECURE will be available as
/dev/watchdog_secure on HS/EMU devices and IVA2 will be available
as /dev/watchdog_iva2. MPU will still be available as /dev/watchdog
Tested on Zoom1 OMAP3 platform
Enabling registration of IVA and SECURE WDT devices. Making
ick and fck for IVA and SECURE WDTs accessible.
Tested on Zoom1 OMAP3 platform
Signed-off-by: Ulrik Bech Hald u...@ti.com
---
arch/arm/mach-omap1/clock.c |6 +-
arch/arm/mach-omap2/clock24xx.c |4 +-
Woodruff, Richard r-woodru...@ti.com writes:
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Tony Lindgren
Last week I posted some more omap io.h clean-up patches to
the linux-omap
list [1], and started looking at what it would take to
Ulrik Bech Hald u...@ti.com writes:
Enabling registration of IVA and SECURE WDT devices. Making
ick and fck for IVA and SECURE WDTs accessible.
Tested on Zoom1 OMAP3 platform
Signed-off-by: Ulrik Bech Hald u...@ti.com
Acked-by: Kevin Hilman khil...@deeprootsystems.com
---
Ulrik Bech Hald u...@ti.com writes:
This patch adds support for IVA2 and SECURE WDTs in the omap_wdt
driver for omap34xx family. SECURE will be available as
/dev/watchdog_secure on HS/EMU devices and IVA2 will be available
as /dev/watchdog_iva2. MPU will still be available as /dev/watchdog
Kevin Hilman khil...@deeprootsystems.com writes:
From: Chunqiu Wang cqw...@motorola.com
According to the GPIO 'Wakeup and Interrupt' section of the TRM[1],
wake-up requests can only be generated on edge transitions.
Also for OMAP3, only edge GPIOs may lose interrupts when PER enters
On Mon, 2009-06-22 at 18:44 -0500, Kevin Hilman wrote:
Jon Hunter jon-hun...@ti.com writes:
From: Jon Hunter jon-hun...@ti.com
There are two scenarios where a race condition could result in a hang in the
prcm_interrupt handler. These are:
IIRC, the RX51 tree has a workaround for some
34 matches
Mail list logo