From: Eero Nurkkala ext-eero.nurkk...@nokia.com
This patchset fixes a few minor issues:
- Keep McBSP fclk active when McBSP is active
- Enable/disable clocks at the proper location
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to
From: Eero Nurkkala ext-eero.nurkk...@nokia.com
McBSP fclk must be maintained for the duration of
audio playback or recording. Otherwise the fclk
may get autogated when the PER96M clk is no longer
required by other modules. This results in audio
playback being hang. Fix this phenomenom by
From: Eero Nurkkala ext-eero.nurkk...@nokia.com
McBSP clocks are being double enabled in the event the
McBSP is already active. Also, they are unnecessarily
disabled when there's no active McBSP in use. Fix this
phenomenom by enabling and disabling the clocks at a
proper location.
Signed-off-by:
ext Premi, Sanjeev pr...@ti.com writes:
While working with cpuidle, I have come across these problems.
I am also working on the solutions, but would be good to hear
more thoughts.
1) The flag 'enable_dyn_sleep' is honoured only in omap3_idle_bm_check()
but in the C1 state,
ext Sanjeev Premi pr...@ti.com writes:
When 'enable_off_mode' is 0, and (mpu_state PWRDM_POWER_RET)
the local variables mpu_state and core_state are modified; but
the usage count for the original state selected by the governor
are updated.
This patch updates the 'last_state' in the cpuidle
-Original Message-
From: Högander Jouni [mailto:jouni.hogan...@nokia.com]
Sent: Monday, March 09, 2009 3:38 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv2] PM : cpuidle - Update statistics for
correct state
ext Sanjeev Premi pr...@ti.com writes:
ext Premi, Sanjeev pr...@ti.com writes:
-Original Message-
From: Högander Jouni [mailto:jouni.hogan...@nokia.com]
Sent: Monday, March 09, 2009 3:38 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv2] PM : cpuidle - Update statistics for
correct state
-Original Message-
From: Högander Jouni [mailto:jouni.hogan...@nokia.com]
Sent: Monday, March 09, 2009 4:07 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv2] PM : cpuidle - Update statistics for
correct state
ext Premi, Sanjeev pr...@ti.com writes:
On Fri, 2009-03-06 at 14:48 -0800, David Brownell wrote:
On Friday 06 March 2009, Mark Brown wrote:
Would it make sense to make this platform data so that if a given board
requires running the chip like this it can be enabled for those boards
but it's not something people might turn on
On Sun, 2009-03-08 at 22:49 +0100, Pierre Ossman wrote:
On Sun, 8 Mar 2009 12:34:25 -0800
David Brownell davi...@pacbell.net wrote:
On Sunday 08 March 2009, Pierre Ossman wrote:
Looks good. Now what should I do with it? Merge it in the next window
good enough?
Well, after testing
This patch adds a new command line option i2c_bus=bus_id,clkrate into
I2C bus registration helper. Purpose of the option is to override the
default board specific bus speed which is supplied by the
omap_register_i2c_bus.
The default bus speed is typically set to speed of slowest I2C chip on the
Hi
Tony, I added kernel-parameters.txt change to the patches 2 and 3. Otherwise
set is the same than currently in linux-omap. Set is generated on top of
mainline version 2.6.29-rc7. Earlier discussion was
http://marc.info/?l=linux-omapm=123635604511892w=2
--
Jarkko
--
To unsubscribe from this
This patch extends command line option i2c_bus=bus_id,clkrate so that
it allow to register additional I2C busses that are not registered with
omap_register_i2c_bus from board initialization code.
Purpose of this is to register additional board busses which are routed
to external connectors only
Signed-off-by: Jarkko Nikula jarkko.nik...@nokia.com
---
arch/arm/plat-omap/i2c.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/arch/arm/plat-omap/i2c.c b/arch/arm/plat-omap/i2c.c
index 467531e..3e95954 100644
--- a/arch/arm/plat-omap/i2c.c
+++
Hi,
I want to test my regulator driver by writing a small kernel module.
But I am a little confused as what should be passed as the first
argument of regulator_get(). How would the kernel module know about
the device pointer that needs to be passed to the _get function?
Thanks,
Anuj Aggarwal
--
On Mon, Mar 09, 2009 at 08:32:55PM +0530, Anuj Aggarwal wrote:
I want to test my regulator driver by writing a small kernel module.
But I am a little confused as what should be passed as the first
argument of regulator_get(). How would the kernel module know about
the device pointer that
What GIT server is the canonical server for the DSS2 branch of the OMAP
kernel? And are there any plans to bring those changes into the main
OMAP kernel?
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo
* Jarkko Nikula jarkko.nik...@nokia.com [090309 06:46]:
Hi
Tony, I added kernel-parameters.txt change to the patches 2 and 3. Otherwise
set is the same than currently in linux-omap. Set is generated on top of
mainline version 2.6.29-rc7. Earlier discussion was
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: 375061a4c5eddf64de40ef2d5dc775b2f586cc12
PatchWorks
http://patchwork.kernel.org/patch/10435/
Git
* Juha Yrjola juha.yrj...@solidboot.com [090308 10:20]:
The reboot mode can be communicated to a bootloader (or the
kernel itself) with a scratchpad register. This functionality
is especially useful, if userspace is allowed to change
the reboot mode.
Signed-off-by: Juha Yrjola
Hi Felipe,
Sorry for the delay replying this...
Find my responses below.
-Original Message-
From: Felipe Balbi [mailto:felipe.ba...@nokia.com]
Sent: Wednesday, March 04, 2009 5:31 AM
To: Aguirre Rodriguez, Sergio Alberto
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org;
This patch has been applied to the linux-omap
by youw fwiendly patch wobot.
Commit: ccd1de46c33fddc044d957a723379acf6d66ebc0
PatchWorks
http://patchwork.kernel.org/patch/10565/
Git
Premi, Sanjeev pr...@ti.com writes:
-Original Message-
From: Högander Jouni [mailto:jouni.hogan...@nokia.com]
Sent: Monday, March 09, 2009 4:07 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv2] PM : cpuidle - Update statistics for
correct state
Juha Yrjola juha.yrj...@solidboot.com writes:
Kevin Hilman wrote:
Maybe just a brief description of this scratchpad location is reserved.
Is there a boot ROM doc that could be referenced?
I don't know how public the boot ROM behaviour is. On my OMAP34xx TRM,
the relevant info is in Chapter
Kevin Hilman wrote:
Maybe just a brief description of this scratchpad location is reserved.
Is there a boot ROM doc that could be referenced?
I don't know how public the boot ROM behaviour is. On my OMAP34xx TRM,
the relevant info is in Chapter 26.4.4.4, Software Booting Configuration.
Tero Kristo tero.kri...@nokia.com writes:
These two patches add fixes to GPIO off-mode handling. First patch is more
important as it fixes a HW bug, second one just optimizes off-mode code
a bit by removing a couple of unnecessary registers from the context save.
Thanks, pushing both patches
Gupta, Ramesh grgu...@ti.com writes:
From a0b8d146249e05465ff30cfd72592418c7a5da8d Mon Sep 17 00:00:00 2001
From: Ramesh Gupta G grgu...@ti.com
Date: Thu, 12 Feb 2009 03:03:18 +0530
Subject: [PATCH 3/3] Boosting OPP1 voltage level
some issues are observed like DSP sending SYS_ERROR
MMU
The GPIO IRQ enable/disable path attempts to also enable IRQ wake
support for the parent GPIO bank IRQ as well. However, since there is
no 'set_wake' hook for the bank IRQs, these calls will always fail.
Also, since the enable will fail on the suspend path, the disable on
the resume path will
Hi Alexey,
-Original Message-
From: Alexey Klimov [mailto:klimov.li...@gmail.com]
snip
--- /dev/null
+++ b/drivers/media/video/ov3640.c
@@ -0,0 +1,2202 @@
+/*
+ * drivers/media/video/ov3640.c
+ *
+ * ov3640 sensor driver
+ *
+ *
+ * Copyright (C) 2008 Texas
-Original Message-
From: Trent Piepho [mailto:xy...@speakeasy.org]
Sent: Wednesday, March 04, 2009 7:42 PM
To: Aguirre Rodriguez, Sergio Alberto
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org; Sakari Ailus;
Tuukka.O Toivonen; Hiroshi DOYU; DongSoo(Nathaniel) Kim;
The reboot mode can be communicated to a bootloader (or the
kernel itself) with a scratchpad register. This functionality
is especially useful, if userspace is allowed to change
the reboot mode.
Signed-off-by: Juha Yrjola juha.yrj...@solidboot.com
---
arch/arm/mach-omap2/prcm.c | 13
Hi,
-Original Message-
From: Alexey Klimov [mailto:klimov.li...@gmail.com]
Sent: Saturday, March 07, 2009 9:42 AM
To: DongSoo(Nathaniel) Kim
Cc: Curran, Dominic; Aguirre Rodriguez, Sergio Alberto; linux-
me...@vger.kernel.org; linux-omap@vger.kernel.org; Sakari Ailus; Tuukka.O
-Original Message-
From: Aguirre Rodriguez, Sergio Alberto
Sent: Monday, March 09, 2009 10:58 PM
To: Alexey Klimov
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org; Sakari Ailus;
Tuukka.O Toivonen; Hiroshi DOYU; DongSoo(Nathaniel) Kim; MiaoStanley;
Nagalla, Hari;
Juha Yrjola juha.yrj...@solidboot.com writes:
The reboot mode can be communicated to a bootloader (or the
kernel itself) with a scratchpad register. This functionality
is especially useful, if userspace is allowed to change
the reboot mode.
Signed-off-by: Juha Yrjola
The GPIO IRQ enable/disable path attempts to also enable IRQ wake
support for the parent GPIO bank IRQ as well. However, since there is
no 'set_wake' hook for the bank IRQs, these calls will always fail.
Also, since the enable will fail on the suspend path, the disable on
the resume path will
* z...@lurian.net z...@lurian.net [090308 11:12]:
On Wed, Mar 04, 2009 at 10:05:32AM -0800, Tony Lindgren wrote:
* z...@lurian.net z...@lurian.net [090127 16:25]:
On Mon, Jan 26, 2009 at 08:48:38AM -0800, Tony Lindgren wrote:
Hi,
* Zebediah C. McClure z...@lurian.net [090124
On Sunday 08 March 2009, Mark Brown wrote:
On Sun, Mar 08, 2009 at 12:54:35PM -0800, David Brownell wrote:
but the bootloader turned the regulator on, then drivers
can't disable the regulator (on penalty of a stackdump!)
unless they issue a spurious/pointless/undesirable enable()
On Fri, Mar 06, 2009 at 03:34:54PM +0200, Ari Kauppi wrote:
I have observed some Spurious IRQ's for I2C1 when all kernel hacking options
(and thus LOCKDEP) are disabled.
Applying Richard Woodruff's 'I2C bug fixes for L-O and L-Z' seems to help
but IRQF_DISABLED is needed for proper
-Original Message-
From: Högander Jouni [mailto:jouni.hogan...@nokia.com]
Sent: Monday, March 09, 2009 3:36 PM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: Problems in cpuidle
ext Premi, Sanjeev pr...@ti.com writes:
While working with cpuidle, I have come
Hi Kevin,
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Tuesday, March 10, 2009 12:41 AM
To: Gupta, Ramesh
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 3/3] Boosting OPP1 voltage level
Gupta, Ramesh grgu...@ti.com writes:
From
40 matches
Mail list logo
