On Thu, Jul 28, 2011 at 9:45 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Jul 19, 2011 at 10:11:58PM -0700, Vikram Pandita wrote:
>> From: Anand Gadiyar
>>
>> This patch enables the DMA mode1 RX support.
>> This feature is enabled based on the short_not_ok flag passed from
>> gadget drivers.
>>
>> T
Hi,
On Tue, Jul 19, 2011 at 10:11:58PM -0700, Vikram Pandita wrote:
> From: Anand Gadiyar
>
> 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
> 40% fo
On Thu, Jul 28, 2011 at 05:32:14PM -0400, Cliff Brake wrote:
> On Thu, Jul 28, 2011 at 5:12 PM, Haslam, Axel 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 have that c
On Thu, 28 Jul 2011 16:18:51 +0200
Arno Steffen 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 Utriainen, PhD
Senior Software Engi
On Thu, Jul 28, 2011 at 11:34 AM, Cousson, Benoit wrote:
> Hi Grant,
>
> On 7/14/2011 1:20 AM, Grant Likely wrote:
>>
>> On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah
>> wrote:
>>>
>>> The i2c-omap driver is converted for supporting both
>>> dt and non dt builds and driver is modified to
On Thu, Jul 28, 2011 at 5:12 PM, Haslam, Axel 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
> Date: Thu Jun 2 16:35:44 2011 -0500
> MUSB: Dont save contex
On Thu, Jul 28, 2011 at 5:05 PM, Cliff Brake 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
CONFIG_USB_MUSB_OTG=y
CON
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 non-linefetch
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 Likely [110716 22:08]:
The way I see it, you've got two options:
1) modify the of_platform_bus_create() to call some
Hi Grant,
On 7/14/2011 1:20 AM, Grant Likely wrote:
On Thu, Jul 14, 2011 at 7:06 AM, G, Manjunath Kondaiah 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 the static regist
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
align
On 7/7/2011 2:10 PM, Tony Lindgren wrote:
* Martin Fouts [110707 10:20]:
Do we really need to do that patching right now to add base 4460
support?
It should be done sometime, but I see no need for it to be right
now.
If we're just doing a bunch of renames all over the place to add
support f
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 cal
2011/7/28 Sricharan R :
>>-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 :
>>> 2011/7/28 Sricharan R :
If
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 Weiyi
>-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
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
>
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
rootfst
On Thu, Jul 28, 2011 at 07:57, Cousson, Benoit 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 @@
>> #includ
Remove duplicated #include('s) in
arch/arm/mach-omap2/omap_hwmod_44xx_data.c
Signed-off-by: Huang Weiyi
---
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
b/arch/arm/mach-omap2/omap
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 start_k
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
On Thu, Jul 28, 2011 at 10:30:07AM +0200, jean.pi...@newoldbits.com wrote:
> From: Jean Pihet
>
> 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_con
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
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
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 =
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
Cc: Kevi
Beagleboard rev-c4 has a speed sorted OMAP3530 chip which can run at 720MHz.
Signed-off-by: Tero Kristo
---
arch/arm/mach-omap2/board-omap3beagle.c | 32 +++
arch/arm/mach-omap2/opp3xxx_data.c |4 +++
2 files changed, 36 insertions(+), 0 deletions(-)
diff
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
---
arch/arm/mach-omap2/voltage.c | 68
Needed as some of the voltage layer functionality is accessed from the
SMPS regulator driver.
Signed-off-by: Tero Kristo
---
arch/arm/plat-omap/include/plat/voltage.h | 20
1 files changed, 20 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/plat-omap/include/pla
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
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);
> + }
>
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
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 p
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.
Regards
Hi,
On Fri, Jul 22, 2011 at 10:57 AM, Felipe Balbi 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().
>>
>> Sign
Hi,
On Fri, Jul 22, 2011 at 10:57 AM, Felipe Balbi 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().
>>
>> Sign
From: Jean Pihet
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,
via the devices
From: Jean Pihet
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 no-op. A new PM Q
From: Jean Pihet
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 using wake-up
From: Vishwanath BS
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
The INACTIVE state is added as unsupported.
Tested on OMAP4 Pandaboard in RET/OFF using wake-up latency constraints on
MPU, CORE
From: Jean Pihet
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 constraints
on
From: Jean Pihet
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 domain.
The power
From: Jean Pihet
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 initializing the power dom
From: Jean Pihet
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
---
arch/arm/plat-omap/Kconfig |7 +
arch/arm/plat-omap/Makefile |1
From: Jean Pihet
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 system.
Signed-o
From: Jean Pihet
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 information related
From: Jean Pihet
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:
. rename pm_qos_c
From: Jean Pihet
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
---
drivers/base/power/main.c |1 +
include/linux/pm.h
From: Jean Pihet
The PM QoS implementation files are better named
kernel/pm_qos.c and include/linux/pm_qos.h.
Signed-off-by: Jean Pihet
---
arch/arm/mach-msm/clock.c |2 +-
drivers/acpi/processor_idle.c |2 +-
drivers/cpuidle/cpuidle.c |2 +-
driv
From: Jean Pihet
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 values (target_value
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 n
52 matches
Mail list logo