Re: [PATCH v4 REPOST 18/20] gpio/omap: use pm-runtime framework

2011-07-28 Thread Todd Poynor
On Wed, Jul 27, 2011 at 05:14:58PM +0530, DebBarma, Tarun Kanti wrote: ... omap_gpio_mod_init calls mpuio_init calls platform_driver_register which can't be called in an IRQs off and spinlocked atomic context, ... I have isolated mpuio_init() from omap_gpio_mod_init(). mpuio_init() is now

[RFC/PATCH v3 00/13] PM QoS: add a per-device latency constraints class

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com This patch set is in an RFC state, for review and comments. High level implementation: 1. Add a new PM QoS class for device wake-up constraints (PM_QOS_DEV_LATENCY). . Define a pm_qos_constraints struct for the storage of the constraints list and associated

[PATCH 01/13] PM: QoS: rename pm_qos_params files to pm_qos

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com The PM QoS implementation files are better named kernel/pm_qos.c and include/linux/pm_qos.h. Signed-off-by: Jean Pihet j-pi...@ti.com --- arch/arm/mach-msm/clock.c |2 +- drivers/acpi/processor_idle.c |2 +- drivers/cpuidle/cpuidle.c

[PATCH 02/13] PM: add a per-device wake-up latency constraints plist

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Add the field latency_constraints in the struct dev_pm_info and the initialization of the plist in device_pm_init. This enables the implementation of per-device constraints in PM QoS. Signed-off-by: Jean Pihet j-pi...@ti.com --- drivers/base/power/main.c |1

[PATCH 03/13] PM: QoS: extend the in-kernel API with per-device latency constraints

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Extend the PM QoS kernel API: - add a new PM QoS class PM_QOS_DEV_LATENCY for device wake-up latency constraints - make the pm_qos_add_request API more generic by using a parameter of type struct pm_qos_parameters - minor clean-ups and rename of struct fields: .

[PATCH 04/13] PM: QoS: implement the per-device latency constraints

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Re-design the PM QoS implementation to support the per-device constraints: - Define a pm_qos_constraints struct for the storage of the constraints list and associated values (target_value, default_value, type ...). - Update the pm_qos_object struct with the

[PATCH 05/13] PM: QoS: support the dynamic insertion and removal of devices

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com The devices latency constraints class of PM QoS is storing the constraints list in the device dev_pm_info struct. This patch adds the init and de-init of the per-device constraints list in order to support the dynamic insertion and removal of the devices in the

[PATCH 06/13] OMAP PM: create a PM layer plugin for per-device constraints

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Created arch/arm/plat-omap/omap-pm-constraints.c file from arch/arm/plat-omap/omap-pm-noop.c and the associated Kconfig option OMAP_PM_CONSTRAINTS. Signed-off-by: Jean Pihet j-pi...@ti.com --- arch/arm/plat-omap/Kconfig |7 +

[PATCH 07/13] OMAP PM: early init of the pwrdms states

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com The powerdomains next states are initialized in pwrdms_setup as a late_initcall. Because the PM QoS devices constraint can be requested early in the boot sequence, the power domains next states can be overwritten by pwrdms_setup. This patch fixes it by

[PATCH 08/13] OMAP2+: powerdomain: control power domains next state

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com When a PM QoS device latency constraint is requested or removed the PM QoS layer notifies the underlying layer with the updated aggregated constraint value. The constraint is stored in the powerdomain constraints list and then applied to the corresponding power

[PATCH 09/13] OMAP3: powerdomain data: add wake-up latency figures

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Figures are added to the power domains structs. Note: the figures are preliminary figures. More accurate measurements are needed. Also the conditions of measurements shall be investigated and described. Tested on OMAP3 Beagleboard in RET/OFF using wake-up latency

[PATCH 10/13] OMAP4: powerdomain data: add wake-up latency figures

2011-07-28 Thread jean . pihet
From: Vishwanath BS vishwanath...@ti.com This patch adds wake up latency numbers for OMAP4. Note that these are preliminary numbers and need to be relooked. Signed-off-by: Vishwanath BS vishwanath...@ti.com The INACTIVE state is added as unsupported. Tested on OMAP4 Pandaboard in RET/OFF using

[PATCH 11/13] OMAP2+: omap_hwmod: manage the wake-up latency constraints

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Hwmod is queried from the OMAP_PM layer to manage the power domains wake-up latency constraints. Hwmod retrieves the correct power domain and if it exists it calls the corresponding power domain function. Tested on OMAP3 Beagleboard and OMAP4 Pandaboard in RET/OFF

[PATCH 12/13] OMAP: PM CONSTRAINTS: implement the devices wake-up latency constraints

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Implement the devices wake-up latency constraints using a PM QoS notification handler which applies the constraints to the underlying layer by calling the corresponding function at hwmod level. Note: the bus throughput function is implemented but currently is a

[PATCH 13/13] OMAP2+: cpuidle only influences the MPU state

2011-07-28 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com Since cpuidle is a CPU centric framework it decides the MPU next power state based on the MPU exit_latency and target_residency figures. The rest of the power domains get their next power state programmed from the PM_QOS_DEV_LATENCY class of the PM QoS framework,

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Jean Pihet
Hi, On Fri, Jul 22, 2011 at 10:57 AM, Felipe Balbi ba...@ti.com wrote: Hi, On Thu, Jul 21, 2011 at 04:52:13PM -0700, Kevin Hilman wrote: Board code should not touch omap_device internals.  To get the MPU/IVA devices, use existing APIs: omap2_get_mpu_device(), omap2_get_iva_device().

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Jean Pihet
Hi, On Fri, Jul 22, 2011 at 10:57 AM, Felipe Balbi ba...@ti.com wrote: Hi, On Thu, Jul 21, 2011 at 04:52:13PM -0700, Kevin Hilman wrote: Board code should not touch omap_device internals.  To get the MPU/IVA devices, use existing APIs: omap2_get_mpu_device(), omap2_get_iva_device().

Re: [PATCH v2 3/5] OMAP4: powerdomain data: Fix core mem states and missing cefuse flag

2011-07-28 Thread Cousson, Benoit
Hi Paul On 7/6/2011 7:59 AM, Paul Walmsley wrote: Hi I split the indentation changes into the following patch, queued for 3.1 at git://git.pwsan.com/linux-2.6 in the 'prcm_cleanup_a_3.1' branch. Thanks a lot for the re-organization of the series and for taking care of the upstream.

[RFC v2]: Issues implementing clock handling mechanism within UART driver

2011-07-28 Thread Govindraj.R
To handle uart clocks within uart driver we need the *semantics of clock enable API should not internally trigger any UART PORT operation* even before completing clock_enable. Ex: while configuring baud rate we may use runtime api's to enable uart port. get_sync - printk - call console uart to

RE: [PATCH v4 REPOST 18/20] gpio/omap: use pm-runtime framework

2011-07-28 Thread DebBarma, Tarun Kanti
Todd, [...] omap_gpio_mod_init calls mpuio_init calls platform_driver_register which can't be called in an IRQs off and spinlocked atomic context, ... I have isolated mpuio_init() from omap_gpio_mod_init(). mpuio_init() is now called once in omap_gpio_probe(). Looking at

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Russell King - ARM Linux
On Thu, Jul 28, 2011 at 12:53:47AM -0500, Nishanth Menon wrote: +struct device *omap_hwmod_to_device(const char *oh_name) +{ + struct omap_hwmod *oh; + + if (!oh_name) { + WARN(1, %s: no hwmod name!\n, __func__); + return ERR_PTR(-EINVAL); + } + +

[PATCHv4 0/4] OMAP SMPS regulator driver

2011-07-28 Thread Tero Kristo
Hello, This version has following changes: - does not move voltage.h under plat-omap anymore, instead creates a stub voltage.h under plat-omap with minimal support required - platform device registration is now done from voltage.c, no need for board file changes anymore - Kconfig option does

[PATCHv4 1/4] omap: voltage: add a stub header file

2011-07-28 Thread Tero Kristo
Needed as some of the voltage layer functionality is accessed from the SMPS regulator driver. Signed-off-by: Tero Kristo t-kri...@ti.com --- arch/arm/plat-omap/include/plat/voltage.h | 20 1 files changed, 20 insertions(+), 0 deletions(-) create mode 100644

[PATCHv4 3/4] omap: smps: add smps regulator init to voltage.c

2011-07-28 Thread Tero Kristo
All voltagedomains that have support for vc and vp are now automatically registered with SMPS regulator driver. Voltage.c builds a platform device structure for this purpose during late init. Signed-off-by: Tero Kristo t-kri...@ti.com --- arch/arm/mach-omap2/voltage.c | 68

[PATCHv4 4/4] TEMP: OMAP3: beagle rev-c4: enable OPP6

2011-07-28 Thread Tero Kristo
Beagleboard rev-c4 has a speed sorted OMAP3530 chip which can run at 720MHz. Signed-off-by: Tero Kristo t-kri...@ti.com --- arch/arm/mach-omap2/board-omap3beagle.c | 32 +++ arch/arm/mach-omap2/opp3xxx_data.c |4 +++ 2 files changed, 36 insertions(+), 0

[PATCHv4 2/4] regulator: omap smps regulator driver

2011-07-28 Thread Tero Kristo
OMAP SMPS regulator driver provides access to OMAP voltage processor controlled regulators. These include VDD_MPU and VDD_CORE for OMAP3 and additionally VDD_IVA for OMAP4. SMPS regulators use the OMAP voltage layer for the actual voltage regulation operations. Signed-off-by: Tero Kristo

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Cousson, Benoit
Hi Nishanth, On 7/28/2011 7:53 AM, Menon, Nishanth wrote: On 11:57-20110722, Felipe Balbi wrote: [...] /* Custom OPP enabled for all xM versions */ if (cpu_is_omap3630()) { - struct omap_hwmod *mh = omap_hwmod_lookup(mpu); - struct omap_hwmod *dh =

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Felipe Balbi
Hi, On Thu, Jul 28, 2011 at 02:57:03PM +0200, Cousson, Benoit wrote: Hi Nishanth, On 7/28/2011 7:53 AM, Menon, Nishanth wrote: On 11:57-20110722, Felipe Balbi wrote: [...] /* Custom OPP enabled for all xM versions */ if (cpu_is_omap3630()) { - struct omap_hwmod *mh =

[Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Arno Steffen
Maybe you are so kind to give me a hint: Try to migrate from Kernel 33 to 37. Currently I don't see any message after Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... From what I understand kernel starts with start_kernel()). What is best way to find out which

Re: [RFC/PATCH v3 00/13] PM QoS: add a per-device latency constraints class

2011-07-28 Thread mark gross
On Thu, Jul 28, 2011 at 10:30:07AM +0200, jean.pi...@newoldbits.com wrote: From: Jean Pihet j-pi...@ti.com This patch set is in an RFC state, for review and comments. High level implementation: 1. Add a new PM QoS class for device wake-up constraints (PM_QOS_DEV_LATENCY). . Define a

Re: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Felipe Balbi
On Thu, Jul 28, 2011 at 03:15:20PM +0200, Arno Steffen wrote: Maybe you are so kind to give me a hint: Try to migrate from Kernel 33 to 37. Currently I don't see any message after Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... From what I

Re: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Gary Thomas
On 2011-07-28 07:15, Arno Steffen wrote: Maybe you are so kind to give me a hint: Try to migrate from Kernel 33 to 37. Currently I don't see any message after Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... From what I understand kernel starts with

[PATCH] OMAP4: hwmod data: remove duplicated #include

2011-07-28 Thread Huang Weiyi
Remove duplicated #include('s) in arch/arm/mach-omap2/omap_hwmod_44xx_data.c Signed-off-by: Huang Weiyi weiyi.hu...@gmail.com --- arch/arm/mach-omap2/omap_hwmod_44xx_data.c |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c

Re: [RFC/PATCH 2/7] OMAP3: beagle: don't touch omap_device internals

2011-07-28 Thread Menon, Nishanth
On Thu, Jul 28, 2011 at 07:57, Cousson, Benoit b-cous...@ti.com wrote: [...] diff --git a/arch/arm/mach-omap2/omap_hwmod.c b/arch/arm/mach-omap2/omap_hwmod.c index 293fa6c..77d01a2 100644 --- a/arch/arm/mach-omap2/omap_hwmod.c +++ b/arch/arm/mach-omap2/omap_hwmod.c @@ -142,6 +142,7 @@  

Re: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Arno Steffen
That has been good points. I've tried both, but with no result so far. boot_nfs_nand=tftpboot 0x8000 uImage; set bootargs ${bootargs_fs1}; run addip; bootm 0x8000 ethaddr=00:11:22:33:44:55 bootcmd=run boot_nfs_nand bootargs=mem=128M console=ttyO2,115200 noinitrd root=/dev/mtdblock6

Re: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Felipe Balbi
Hi, (please don't top-post) On Thu, Jul 28, 2011 at 04:18:51PM +0200, Arno Steffen wrote: That has been good points. I've tried both, but with no result so far. boot_nfs_nand=tftpboot 0x8000 uImage; set bootargs ${bootargs_fs1}; run addip; bootm 0x8000 ethaddr=00:11:22:33:44:55

RE: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Sricharan R
-Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Arno Steffen Sent: Thursday, July 28, 2011 6:45 PM To: linux-omap@vger.kernel.org Subject: [Q] No message from Kernel (Howto start debug?) Maybe you are so kind to give me a

Re: [PATCH] OMAP4: hwmod data: remove duplicated #include

2011-07-28 Thread Cousson, Benoit
On 7/28/2011 3:35 PM, Huang Weiyi wrote: Remove duplicated #include('s) in arch/arm/mach-omap2/omap_hwmod_44xx_data.c Thanks Huang, good catch. The second one was added by the 6d3c55f commit. It might not go in the current merge window since Tony is in vacation. Signed-off-by: Huang

Re: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Arno Steffen
2011/7/28 Sricharan R r.sricha...@ti.com: -Original Message- From: Arno Steffen [mailto:arno.stef...@googlemail.com] Sent: Thursday, July 28, 2011 9:13 PM To: Sricharan R Subject: Re: [Q] No message from Kernel (Howto start debug?) 2011/7/28 Arno Steffen arno.stef...@googlemail.com:

Re: [PATCH v4 REPOST 18/20] gpio/omap: use pm-runtime framework

2011-07-28 Thread Todd Poynor
On Thu, Jul 28, 2011 at 03:05:29PM +0530, DebBarma, Tarun Kanti wrote: ... Looking at omap_gpio_mod_init() it seems like much of its processing could probably be done once at probe time (or at pm_runtime_get_sync time) as well, namely setting the IRQ enable masks. This must be called at

Re: [PATCH v2 00/18] OMAP4: PM data big spring cleanup and fixes

2011-07-28 Thread Cousson, Benoit
On 7/6/2011 9:19 AM, Paul Walmsley wrote: Hi, On Fri, 1 Jul 2011, Benoit Cousson wrote: Here are a bunch of cleanups on almost every PRCM related data files. Some of them are purely code moves, and will look like a lot of noise for nothing, but this is needed if we want to keep the files

Re: [PATCH 4/4] dt: i2c-omap: Convert i2c driver to use device tree

2011-07-28 Thread Cousson, Benoit
Hi Grant, On 7/14/2011 1:20 AM, Grant Likely wrote: On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiahmanj...@ti.com wrote: The i2c-omap driver is converted for supporting both dt and non dt builds and driver is modified to use dt data partially. [...] /* NOTE: driver uses

Re: [PATCH 3/4] dt: omap3: add generic board file for dt support

2011-07-28 Thread Cousson, Benoit
Hi Rajendra, On 7/21/2011 10:55 AM, Nayak, Rajendra wrote: On 7/20/2011 3:04 AM, Grant Likely wrote: On Mon, Jul 18, 2011 at 02:07:10AM -0700, Tony Lindgren wrote: * Grant Likelygrant.lik...@secretlab.ca [110716 22:08]: The way I see it, you've got two options: 1) modify the

musb crash on suspend

2011-07-28 Thread Cliff Brake
Hello, I'm running 2.6.39 on omap3530 with a number of patches and am seeing the below crash on suspend. Questions: 1) does anyone have musb suspending with 2.6.39? 2) are there any fixes or suggestions? Thanks, Cliff musb-hdrc musb-hdrc: suspend Unhandled fault: external abort on

Re: musb crash on suspend

2011-07-28 Thread Cliff Brake
On Thu, Jul 28, 2011 at 5:05 PM, Cliff Brake cliff.br...@gmail.com wrote: My kernel config is: CONFIG_USB_MUSB_HDRC=y # CONFIG_USB_MUSB_TUSB6010 is not set CONFIG_USB_MUSB_OMAP2PLUS=y # CONFIG_USB_MUSB_AM35X is not set # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_PERIPHERAL is not set

Re: musb crash on suspend

2011-07-28 Thread Cliff Brake
On Thu, Jul 28, 2011 at 5:12 PM, Haslam, Axel axelhas...@ti.com wrote: Cliff, Im not sure if you have are seeing the same issue, but maybe something like this may help: commit 39b7060345141b3ed2567fc6bc104ccab545fc0e Author: Axel Haslam axelhas...@ti.com Date:   Thu Jun 2 16:35:44 2011 -0500

Re: [PATCH 4/4] dt: i2c-omap: Convert i2c driver to use device tree

2011-07-28 Thread Grant Likely
On Thu, Jul 28, 2011 at 11:34 AM, Cousson, Benoit b-cous...@ti.com wrote: Hi Grant, On 7/14/2011 1:20 AM, Grant Likely wrote: On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiahmanj...@ti.com  wrote: The i2c-omap driver is converted for supporting both dt and non dt builds and driver

Re: [Q] No message from Kernel (Howto start debug?)

2011-07-28 Thread Tapani Utriainen
On Thu, 28 Jul 2011 16:18:51 +0200 Arno Steffen arno.stef...@googlemail.com wrote: That has been good points. I've tried both, but with no result so far. Try appending earlyprintk=${console} to your bootargs (where ${console} is your console string, e.g. ttyO0,115200n8 ) --- Tapani

Re: musb crash on suspend

2011-07-28 Thread Felipe Balbi
On Thu, Jul 28, 2011 at 05:32:14PM -0400, Cliff Brake wrote: On Thu, Jul 28, 2011 at 5:12 PM, Haslam, Axel axelhas...@ti.com wrote: Cliff, Im not sure if you have are seeing the same issue, but maybe something like this may help: commit 39b7060345141b3ed2567fc6bc104ccab545fc0e I don't

Re: [PATCH v4] usb: musb: Enable DMA mode1 RX for USB-Mass-Storage

2011-07-28 Thread Felipe Balbi
Hi, On Tue, Jul 19, 2011 at 10:11:58PM -0700, Vikram Pandita wrote: From: Anand Gadiyar gadi...@ti.com This patch enables the DMA mode1 RX support. This feature is enabled based on the short_not_ok flag passed from gadget drivers. This will result in a thruput performance gain of around

Re: [PATCH v4] usb: musb: Enable DMA mode1 RX for USB-Mass-Storage

2011-07-28 Thread Pandita, Vikram
On Thu, Jul 28, 2011 at 9:45 PM, Felipe Balbi ba...@ti.com wrote: Hi, On Tue, Jul 19, 2011 at 10:11:58PM -0700, Vikram Pandita wrote: From: Anand Gadiyar gadi...@ti.com This patch enables the DMA mode1 RX support. This feature is enabled based on the short_not_ok flag passed from gadget