Hi,
On Sun, Jul 24, 2011 at 11:52:37AM -0500, Nishanth Menon wrote:
SmartReflex should be disabled while entering low power mode due to
the following reasons:
a) SmartReflex values are not defined for retention voltage.
b) With SmartReflex enabled, if the CPU enters low power state, FSM
Hi,
On Sun, 2011-07-24 at 23:56 +0200, ext Sjur Brændeland wrote:
Hi Carlos,
Sorry for the long delay. My comments below:
No worries, I will probably be very slow when responding to you as
well for the next
couple of weeks...
+ * @flow: RX flow type (SYNCHRONIZED or PIPELINE)
+ *
On Thu, Jul 21, 2011 at 12:57:03PM +0300, Felipe Balbi wrote:
the problem seems to be worse then you thought:
$ git ls-files drivers/ | grep madc
drivers/hwmon/twl4030-madc-hwmon.c
drivers/mfd/twl4030-madc.c
This is normal for this sort of auxiliary ADC - they're *normally* used
for system
On Thu, Jul 21, 2011 at 8:56 PM, J, KEERTHY j-keer...@ti.com wrote:
On Thu, Jul 7, 2011 at 2:59 PM, Paul Walmsley p...@pwsan.com wrote:
Hi
On Tue, 5 Jul 2011, Vishwanath BS wrote:
From: Keerthy j-keer...@ti.com
Patch adds hwmod entry for 4460 thermal sensor module. Thermal sensor module
In the nand partition table specifying the offset addresses
directly instead of using the macro MTDPART_OFS_APPEND to gain
runtime efficiency while nand initialization.
MTDPART_OFS_APPEND has the value (-1) ,if assigned to offset,
a runtime calculation of actual offset happens each time nand is
On Mon, Jul 25, 2011 at 06:37:23PM +0530, Hrishikesh Bhandiwad wrote:
In the nand partition table specifying the offset addresses
directly instead of using the macro MTDPART_OFS_APPEND to gain
runtime efficiency while nand initialization.
MTDPART_OFS_APPEND has the value (-1) ,if assigned to
During normal system operation warning messages similar to this
are appearing quite often:
omap_device: omap4-keypad.-1: new worst case activate latency 0: 61035
This doesn't seem to be reporting a problem, nor is it very useful for
non-developers, so reduce it to debug level.
Cc: Steve Sakoman
Hi again,
On Mon, Jul 25, 2011 at 04:14:06PM +0300, Felipe Balbi wrote:
On Mon, Jul 25, 2011 at 06:37:23PM +0530, Hrishikesh Bhandiwad wrote:
In the nand partition table specifying the offset addresses
directly instead of using the macro MTDPART_OFS_APPEND to gain
runtime efficiency while
This patch adds the NAND support on OMAP3EVM board and also allocates
five partitions on NAND.
Referred to file: arch/arm/mach-omap2/board-omap3beagle.c
Signed-off-by: Vaibhav Hiremath hvaib...@ti.com
Signed-off-by: Sanjeev Premi pr...@ti.com
Signed-off-by: Hrishikesh Bhandiwad
On Sat, 2011-07-23 at 01:51 +0200, Balbi, Felipe wrote:
Hi,
On Tue, Jul 05, 2011 at 01:27:51PM +0300, Tero Kristo wrote:
This is no longer needed as it will be handled within serial driver itself.
Signed-off-by: Tero Kristo t-kri...@ti.com
isn't this introducing a regression ? Should
Hello,
Changes compared to previous set:
- moved OMAP3/OMAP4 specific code under prm.c files
- dropped most of the event definitions for now, and just left
wkup and io events in
- PRCM events are now defined as a common struct under prcm.c
- moved mux handling routines from omap_hwmod.c to
From: R, Govindraj govindraj.r...@ti.com
Add API to enable IO pad wakeup capability based on mux dynamic pad and
wake_up enable flag available from hwmod_mux initialization.
Use the wakeup_enable flag and enable wakeup capability
for the given pads. Wakeup capability will be enabled/disabled
From: R, Govindraj govindraj.r...@ti.com
Add API to determine IO-PAD wakeup event status for a given
hwmod dynamic_mux pad.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
---
arch/arm/mach-omap2/mux.c| 30 ++
arch/arm/mach-omap2/mux.h
OMAP mux now provides a service routine to parse pending wakeup events
and to call registered ISR whenever active wakeups are detected. This
routine is called directly from PRCM interrupt handler.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/mux.c | 27
This is no longer needed as it will be handled within serial driver itself.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm34xx.c | 19 ---
1 files changed, 0 insertions(+), 19 deletions(-)
diff --git a/arch/arm/mach-omap2/pm34xx.c
Just for PRCM chain handler testing purposes. This should be replaced with
a proper implementation.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/serial.c | 71 -
1 files changed, 69 insertions(+), 2 deletions(-)
diff --git
This patch is just a temporary hack to allow serial to work properly with
the PRCM chain handler. Should be replaced with a proper implementation.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/serial.c | 28 +---
drivers/tty/serial/omap-serial.c
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do this by introducing PRCM event
names, which are then matched to the particular PRCM interrupt bit
depending on the specific OMAP SoC
Prevents a hang when omap_device would want to print something for
serial console device while enabling / disabling its clocks.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/plat-omap/omap_device.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
These are no longer needed as omap_hwmod takes care of multiplexing of pads.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/serial.c | 25 +
1 files changed, 1 insertions(+), 24 deletions(-)
diff --git a/arch/arm/mach-omap2/serial.c
This prevents system hang while attempting to access suspended console. Should
most likely be fixed with proper console locking.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm34xx.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git
This is handled automatically by the PRCM chain interrupt mechanism now.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm34xx.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
index
On Mon, Jul 25, 2011 at 03:42, Felipe Balbi ba...@ti.com wrote:
Hi,
On Sun, Jul 24, 2011 at 11:52:37AM -0500, Nishanth Menon wrote:
SmartReflex should be disabled while entering low power mode due to
the following reasons:
a) SmartReflex values are not defined for retention voltage.
b) With
Hi,
On Mon, Jul 25, 2011 at 07:36:01PM +0300, Tero Kristo wrote:
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do this by introducing PRCM event
which drivers ? Are those somehow
Hi,
On Mon, Jul 25, 2011 at 11:59:10AM -0500, Menon, Nishanth wrote:
On Sun, Jul 24, 2011 at 11:52:37AM -0500, Nishanth Menon wrote:
SmartReflex should be disabled while entering low power mode due to
the following reasons:
a) SmartReflex values are not defined for retention voltage.
b)
On Mon, Jul 25, 2011 at 12:13, Felipe Balbi ba...@ti.com wrote:
[..]
while at that, SR's IRQ is never freed on exit path, could fix it while
you're already there ?
This is not really related to this patch is it? IMHO IRQ handling is
I didn't say to put it on the same patch ;-) I meant that
Hi,
On Mon, Jul 25, 2011 at 12:55:39PM -0500, Menon, Nishanth wrote:
On Mon, Jul 25, 2011 at 12:13, Felipe Balbi ba...@ti.com wrote:
[..]
while at that, SR's IRQ is never freed on exit path, could fix it while
you're already there ?
This is not really related to this patch is it? IMHO
Dear all,
Does anyone came across a v4l2 Linux Device Driver for an Image Sensor
that uses Parallel CMOS H/V and can only be control by UART interface
instead of the common I2C or SPI interface?
A similar sensor is the STMicroelectronics VL5510 Image Sensor
although it support all 3 types of
28 matches
Mail list logo
