Charles Manning wrote:
Luca, I have been having similar problems on a hacked Overo kernel.
I have no problems with 2.6.35.
I tried just commenting out the define and disabling PREFETCH and did not get
a good boot due to ubi not finding the volume info.
Are you loading up a UBI image
-Original Message-
From: Nishanth Menon [mailto:n...@ti.com]
Sent: Wednesday, December 08, 2010 10:05 PM
To: Gopinath, Thara
Cc: Kevin Hilman; linux-omap@vger.kernel.org; p...@pwsan.com; Cousson,
Benoit; Sripathy, Vishwanath; Sawant, Anand
Subject: Re: [PATCH v4 7/9] OMAP3: PM: Adding
Gopinath, Thara wrote, on 12/09/2010 03:43 AM:
-Original Message-
From: Nishanth Menon [mailto:n...@ti.com]
Sent: Wednesday, December 08, 2010 10:05 PM
To: Gopinath, Thara
Cc: Kevin Hilman; linux-omap@vger.kernel.org; p...@pwsan.com; Cousson,
Benoit; Sripathy, Vishwanath; Sawant,
Some configurations don't make sense with Thumb-2, or don't
currently work and are unlikely to be relevant.
The patches avoid Kconfig from allowing these problematic
combinations, for now.
Dave Martin (2):
ARM: Thumb-2: Make CONFIG_THUMB2_KERNEL depend on !CPU_V6
ARM: Make CONFIG_FPE_NWFPE
This makes sense, because Thumb-2 code can't execute on plain
ARMv6 processors.
This will avoid accidentally configuring a broken kernel where the
config otherwise would allow multiple architecture versions to
coexist in the same kernel.
Not adding !CPU_V5 etc., because the chance of anyone
Because the nwfpe support is unlikely to be used on new platforms
and requires CONFIG_OABI_COMPAT, which is not generally used with
ARMv7+, we shouldn't expect to build nwfpe support into a Thumb-2
kernel.
At present, nwfpe contains assembly code which isn't Thumb-2
compatible, and for now it
Hello.
On 08-12-2010 19:01, Hema HK wrote:
Registering the twl6030-usb transceiver device as a child to twl6030 core.
Removed the NOP transceiver init call from board file.
Populated twl4030_usb_data platform data structure with the function
pointers for OMAP4430 internal PHY operation to
Hi,
On Tuesday 07 December 2010 20:03:28 Mark Brown wrote:
On Tue, Dec 07, 2010 at 07:11:39PM +0100, Hans Verkuil wrote:
Ah, now I understand what you mean. Would 'activated' be better than
'active'?
Better, yes, though it still sounds a bit like something should be
actively (IYSWIM)
This patch extends the LED backlight tirgger driver with an option that allows
for inverting the trigger output polarity.
With the invertion option provided, I (ab)use the backlight trigger for
driving a LED that indicates LCD display blank condtition on my Amstrad Delta
videophone. Since the
-Original Message-
From: Menon, Nishanth
Sent: Thursday, December 09, 2010 4:54 PM
To: Gopinath, Thara
Cc: Kevin Hilman; linux-omap@vger.kernel.org; p...@pwsan.com; Cousson,
Benoit; Sripathy, Vishwanath; Sawant, Anand
Subject: Re: [PATCH v4 7/9] OMAP3: PM: Adding debug support to Voltage
On Tue, 07 Dec 2010 23:18:28 -0700
Paul Walmsley p...@pwsan.com wrote:
This series is available via git from git://git.pwsan.com/linux-2.6 in
the branch 'pwrdm_prcm_b_2.6.38'. It applies on top of the OMAP:
PRCM/powerdomain/clockdomain patches for 2.6.38, part one series,
sent earlier.
Hi All,
In order to enforce a little bit of consistency in the omap devices name,
the convention for omap devices name will be now omap_xxx. All the drivers
adapted to hwmod will be named like that during the on-going adaptations.
The I2C and UART drivers are already adapted to hwmod but with
The naming convention for omap_device is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Remove the hs prefix that is implicit for every OMAP uarts.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Acked-by: Govindraj Raja govindraj.r...@ti.com
Cc: Paul
The convention for omap device naming is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Change device name in clock nodes as well.
Signed-off-by: Benoit Cousson b-cous...@ti.com
c: Paul Walmsley p...@pwsan.com
Cc: Kevin Hilman
Hi Bryan,
On Wed, Dec 08, 2010 at 10:42:04AM +0800, Bryan Wu wrote:
Fix the following section mismatch warning when building omap2plus_defconfig:
WARNING: vmlinux.o(.data+0x47d7c): Section mismatch in reference from the
variable twl_driver to the function .init.text:twl_probe()
Patch
This patch adds OPP tables for OMAP4. New file has been added to keep
the OMAP4 opp tables and the registration of these tables with the
generic opp framework by OMAP SoC OPP interface.
Based on:
From: Kevin Hilman khil...@deeprootsystems.com
With new OPP layer, OPP users will access OPP API directly instead of
using OMAP PM layer, so remove all notions of OPPs from the OMAP PM
layer.
Acked-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Nishanth Menon n...@ti.com
Signed-off-by: Kevin
Hi,
This series introduces OPP data for OMAP3 and 4 with relevant cleanups
in OMAP's pm layer. Additional patches for cpufreq interface to OPP
library + enablement of SmartReflex, voltage layers depend on the
data made available here.
Major changes in V6:
Looping in L-a + added Paul's Ack in
Add OPP data for OMAP34xx and OMAP36xx and initialization functions
to populate OPP tables based on current SoC.
introduce an OMAP generic opp initialization routine which OMAP3
and OMAP4+ SoCs can use to register their OPP definitions.
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Vitaly Wool vitalyw...@gmail.com writes:
On Wed, Dec 8, 2010 at 11:40 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
@@ -120,8 +133,9 @@ static void omap2_enter_full_retention(void)
goto no_sleep;
/* Block console output in case it is on one of the OMAP UARTs */
These patches add initial support for Nokia RM-680 board.
Patches 1-7 are just preparation and make board-rx51-sdram.c reusable
by renaming it to sdram-nokia.c etc.
Patch 8 adds a new board and requires updated mach-types from
http://www.arm.linux.org.uk/developer/machines/download.php in order
Add a header file for Nokia SDRAM functions. Based on patches by Juha
Keski-Saari.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/board-rx51.c |2 +-
arch/arm/mach-omap2/sdram-nokia.c |1 +
arch/arm/mach-omap2/sdram-nokia.h | 12
3 files
Rename the file and functions so that it can be reused by future Nokia
boards. Based on patches by Juha Keski-Saari.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/Makefile |2 +-
arch/arm/mach-omap2/board-rx51.c |4 +-
Rename the current timings to indicate they're for 166 MHz. Based on
patches by Eduardo Valentin and Juha Keski-Saari.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
Cc: Eduardo Valentin eduardo.valen...@nokia.com
---
arch/arm/mach-omap2/sdram-nokia.c | 11 ++-
1 files changed, 6
Use an array to make it easier to add new values.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/sdram-nokia.c | 21 +++--
1 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-omap2/sdram-nokia.c
Actually check for errors: print an error log and return NULL.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/sdram-nokia.c |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/sdram-nokia.c
41.5 MHz SDRAM clock is not usable.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/sdram-nokia.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/sdram-nokia.c
b/arch/arm/mach-omap2/sdram-nokia.c
index 863586b..baf83ec
Introduce 97.6/195.2 MHz memory timing data. Based on patches by Eduardo
Valentin, Igor Dmitriev and Juha Keski-Saari.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
Cc: Eduardo Valentin eduardo.valen...@nokia.com
Cc: Igor Dmitriev ext-dmitriev.i...@nokia.com
---
Add minimal support for Nokia RM-680 board.
Tested with omap2plus_defconfig.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
arch/arm/mach-omap2/Kconfig |6 +
arch/arm/mach-omap2/Makefile |3 +
arch/arm/mach-omap2/board-rm680.c| 187
Aaro Koskinen had written, on 12/09/2010 10:39 AM, the following:
[...]
diff --git a/arch/arm/mach-omap2/sdram-nokia.h
b/arch/arm/mach-omap2/sdram-nokia.h
new file mode 100644
index 000..ee63da5
--- /dev/null
+++ b/arch/arm/mach-omap2/sdram-nokia.h
@@ -0,0 +1,12 @@
+/*
+ * SDRC register
Ben,
Benoit Cousson b-cous...@ti.com writes:
The convention for omap device naming is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Change device name in clock nodes as well.
Signed-off-by: Benoit Cousson b-cous...@ti.com
c: Paul Walmsley
Benoit Cousson b-cous...@ti.com writes:
Hi All,
In order to enforce a little bit of consistency in the omap devices name,
the convention for omap devices name will be now omap_xxx. All the drivers
adapted to hwmod will be named like that during the on-going adaptations.
The I2C and UART
From: Ming Lei tom.leim...@gmail.com
Obviously we should only initialize musb once.
Signed-off-by: Ming Lei tom.leim...@gmail.com
---
arch/arm/mach-omap2/board-omap4panda.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
Hi Aaro,
A couple of small comments below, otherwise looks nice to me.
Jamie
On Thu, Dec 09, 2010 at 06:39:24PM +0200, Aaro Koskinen wrote:
Add minimal support for Nokia RM-680 board.
Tested with omap2plus_defconfig.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
[...]
+#if
On Thu, 9 Dec 2010, Benoit Cousson wrote:
The convention for omap device naming is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Change device name in clock nodes as well.
Acked-by: Paul Walmsley p...@pwsan.com
- Paul
--
To unsubscribe from
Omar Ramirez Luna omar.rami...@ti.com writes:
Patch OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va[1],
introduces omap_device_get_rt_va which is meant to be called
by drivers to retrieve the _mpu_rt_va, however this function
receives a pointer to an omap_device; since there is no
Gopinath, Thara th...@ti.com writes:
[...]
So for this first version that we plan to push to kernel.org, I plan
to expose out these parameters to user space but not allow a write
access to them. The write access part can be added later whenever
required.
OK with me.
Kevin
--
To unsubscribe
tom.leim...@gmail.com had written, on 12/09/2010 11:02 AM, the following:
From: Ming Lei tom.leim...@gmail.com
Obviously we should only initialize musb once.
Signed-off-by: Ming Lei tom.leim...@gmail.com
---
arch/arm/mach-omap2/board-omap4panda.c |3 ---
1 files changed, 0 insertions(+),
Kevin Hilman had written, on 12/09/2010 11:19 AM, the following:
Gopinath, Thara th...@ti.com writes:
[...]
So for this first version that we plan to push to kernel.org, I plan
to expose out these parameters to user space but not allow a write
access to them. The write access part can be
On Thu, Dec 09, 2010 at 07:11:28PM +0200, Aaro Koskinen wrote:
Hi,
On Thu, 9 Dec 2010, Jamie Iles wrote:
+static void __init rm680_peripherals_init(void)
+{
+ platform_add_devices(rm680_peripherals_devices,
+ ARRAY_SIZE(rm680_peripherals_devices));
+
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to move the calls to disable_hlt at the very
Hello Jarkko
On Thu, 9 Dec 2010, Jarkko Nikula wrote:
On Tue, 07 Dec 2010 23:18:28 -0700
Paul Walmsley p...@pwsan.com wrote:
This series is available via git from git://git.pwsan.com/linux-2.6 in
the branch 'pwrdm_prcm_b_2.6.38'. It applies on top of the OMAP:
Kevin,
On Thu, Dec 9, 2010 at 12:01 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
Paul Walmsley p...@pwsan.com writes:
Hi,
On Tue, 7 Dec 2010, Chikkature Rajashekar, Madhusudhan wrote:
On Tue, Dec 7, 2010 at 1:51 PM, Adrian Hunter adrian.hun...@nokia.com
wrote:
It is at least because omap_pm_get_dev_context_loss_count() is not
implemented. Tero Kristo was looking
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to
Govindraj govindraj...@gmail.com writes:
On Fri, Dec 3, 2010 at 4:38 PM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Friday, December 03, 2010 3:53 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org;
Hi Kevin
On Thu, 9 Dec 2010, Kevin Hilman wrote:
Paul, do you want to submit a formal patch for this for 2.6.38? if not,
I can add a changelog and queue this with other PM core changes for 2.6.38.
we should probably come up with a patch for .38 that only increments this
when off-mode is
On Thu, 9 Dec 2010, Paul Walmsley wrote:
On Thu, 9 Dec 2010, Kevin Hilman wrote:
Paul, do you want to submit a formal patch for this for 2.6.38? if not,
I can add a changelog and queue this with other PM core changes for 2.6.38.
we should probably come up with a patch for .38 that only
On Thu, 9 Dec 2010, Dave Martin wrote:
Because the nwfpe support is unlikely to be used on new platforms
and requires CONFIG_OABI_COMPAT, which is not generally used with
ARMv7+, we shouldn't expect to build nwfpe support into a Thumb-2
kernel.
At present, nwfpe contains assembly code
On Thu, 9 Dec 2010, Dave Martin wrote:
This makes sense, because Thumb-2 code can't execute on plain
ARMv6 processors.
This will avoid accidentally configuring a broken kernel where the
config otherwise would allow multiple architecture versions to
coexist in the same kernel.
Not adding
On Thu, Dec 09, 2010 at 08:55:28AM -0800, Kevin Hilman wrote:
Ben,
The convention for omap device naming is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Renaming stuff like this is going to have an impact on the userspace
as anyone looking
Hi Charu,
Varadarajan, Charulatha ch...@ti.com writes:
Prepare for implementing GPIO as a platform driver.
Modifies omap_gpio_init() to make use of omap_gpio_chip_init()
and omap_gpio_mod_init(). omap_gpio_mod_init() does the module init
by clearing the status register and initializing the
As part of the GPIO conversion to platform_device/platform_driver,
commit 2fae7fbed072705d91e09ed393b2e580b2d895fc (OMAP: GPIO: prepare
for platform driver) removed hard-coded per-bank SYSCONFIG register
values in favor of using omap_hwmod to manage the SYSCONFIG register.
In the previous code,
Hello.
Kevin Hilman wrote:
The resource data is getting automatically populated from a set of data
generated from TI's hardware database for the OMAP platform,
While we could hack in some exceptions to that tool to generate resources
in a specific order, it seems less fragile to use the
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to move the calls to disable_hlt at the very
On Thu, Dec 9, 2010 at 7:00 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
jean.pi...@newoldbits.com writes:
From: Jean Pihet j-pi...@ti.com
Some bad interaction between the idle and the suspend paths has been
identified: the idle code is called during the suspend enter and exit
Ben Dooks ben-...@fluff.org writes:
On Thu, Dec 09, 2010 at 08:55:28AM -0800, Kevin Hilman wrote:
Ben,
The convention for omap device naming is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Renaming stuff like this is going to have an
On Thu, Dec 09, 2010 at 08:55:28AM -0800, Kevin Hilman wrote:
Ben,
Benoit Cousson b-cous...@ti.com writes:
The convention for omap device naming is omap_XXX.
Rename the device and driver name in order to stick
to this naming convention.
Change device name in clock nodes as well.
Hi Paul,
On Dec 9, 2010, at 12:36 AM, Paul Walmsley wrote:
On Wed, 8 Dec 2010, Elvis Dowson wrote:
What should I do to change the output frequency of mmc2_clk
signal to 48Mhz for the OMAP35xx processor?
Right now it is giving an output of 96MHz and the signal output looks
more
Salut Kevin,
On 12/9/2010 8:18 PM, Kevin Hilman wrote:
Hi Charu,
Varadarajan, Charulathach...@ti.com writes:
Prepare for implementing GPIO as a platform driver.
Modifies omap_gpio_init() to make use of omap_gpio_chip_init()
and omap_gpio_mod_init(). omap_gpio_mod_init() does the module
This series is a reduced set of the previous one, containing only two
patches that were changed based on Omar's review:
http://marc.info/?l=linux-omapm=129162731925095
Also rebased to the latest dspbridge branch from the
omapzoom.org git tree.
Ionut Nicu (2):
staging: tidspbridge: rmgr/node.c
Reorganized some code in rmgr/node.c to increase its
readability. Most of the changes reduce the code
indentation level and simplifiy the code. No functional
changes were done.
Signed-off-by: Ionut Nicu ionut.n...@mindbit.ro
---
drivers/staging/tidspbridge/rmgr/node.c | 607
Reorganized some code in the rmgr module to increase
its readability. No functional changes were done.
Signed-off-by: Ionut Nicu ionut.n...@mindbit.ro
---
drivers/staging/tidspbridge/rmgr/drv.c | 171 +---
drivers/staging/tidspbridge/rmgr/node.c | 81 +-
Hi Paul,
Here is a collections of fixes and clock nodes addition done on OMAP3
and OMAP4 clock data files.
I have included the one that Thara already submitted after fixing the
various comments done on the original version.
That revision include as well a new fix from Jon. Thanks to both fixes,
The gating of pad_clks and slimbus_ck is controlled by the PRCM, but
since the clock source is external, this is the SW responsability
to gate / un-gate it when the mcpdm or slimbus module need to be used.
There is no autogating possible with such external clock.
Add SW control to enable /
The smartreflex modules belong to an ALWON_FCLK clock domain that
does not have any SW control. The gating of that interface clock
is triggered by a transition of the WKUP clock domain to idle.
Attach both smartreflex instances on OMAP3 to the WKUP clock domain.
The missing clock domain field in
From: Jonathan Bergsagel jbergsa...@ti.com
Add register address, mask and link to the clksel structure that
were missing in the IVA DPLL mux clock node.
Signed-off-by: Jonathan Bergsagel jbergsa...@ti.com
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc:
From: Thara Gopinath th...@ti.com
This patch extends the OMAP4 clock data to include
various x2 clock nodes between DPLL and HS dividers as the
clock framework skips a x2 while calculating the dpll locked
frequency.
The clock database extensions are autogenerated using
the scripts maintained by
Add the header file with scrm registers absolute address, offset
and bitfields.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Cc: Paul Walmsley p...@pwsan.com
---
arch/arm/mach-omap2/scrm44xx.h | 176
1 files
From: Rajendra Nayak rna...@ti.com
Add support for auxiliary clocks nodes which are part of SCRM.
Signed-off-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
---
arch/arm/mach-omap2/clock44xx_data.c | 175
From: Jon Hunter jon-hun...@ti.com
The following OMAP4 clocks have the following fixed divisors that
determine the frequency at which these clocks operate. These
dividers are defined by the PRCM specification and without these
dividers the rates of the below clocks are calculated incorrectly.
From: Rajendra Nayak rna...@ti.com
The CORE and PER M3 post dividers are different from the rest of the
DPLL post dividers as in they go to SCRM, and are used
there to export clocks for instance used by external sensor.
There is no automatic HW dependency in PRCM to manage them. Hence these
two
On Wed, Dec 8, 2010 at 5:59 PM, Omar Ramirez Luna omar.rami...@ti.com wrote:
Patch OMAP: hwmod/device: add omap_{device, hwmod}_get_mpu_rt_va[1],
introduces omap_device_get_rt_va which is meant to be called
by drivers to retrieve the _mpu_rt_va, however this function
receives a pointer to an
Hi,
Kevin Hilman [khil...@deeprootsystems.com]:
Ben Dooks ben-...@fluff.org writes:
Renaming stuff like this is going to have an impact on the userspace
as anyone looking through /sys's driver heirarchy is going to miss the
old name...
It all depends if you really want to go ahead with
Cousson, Benoit b-cous...@ti.com writes:
Salut Kevin,
On 12/9/2010 8:18 PM, Kevin Hilman wrote:
Hi Charu,
Varadarajan, Charulathach...@ti.com writes:
Prepare for implementing GPIO as a platform driver.
Modifies omap_gpio_init() to make use of omap_gpio_chip_init()
and
On Thu, Dec 09, 2010 at 10:18:48PM +, aaro.koski...@nokia.com wrote:
Hi,
Kevin Hilman [khil...@deeprootsystems.com]:
Ben Dooks ben-...@fluff.org writes:
Renaming stuff like this is going to have an impact on the userspace
as anyone looking through /sys's driver heirarchy is going
Hi Omar,
On Thu, 2010-12-09 at 23:47 +0200, Ionut Nicu wrote:
Reorganized some code in rmgr/node.c to increase its
readability. Most of the changes reduce the code
indentation level and simplifiy the code. No functional
changes were done.
snip
/*
* Check stream mode. Default
On 12/9/2010 11:19 PM, Kevin Hilman wrote:
Cousson, Benoitb-cous...@ti.com writes:
Salut Kevin,
On 12/9/2010 8:18 PM, Kevin Hilman wrote:
Hi Charu,
Varadarajan, Charulathach...@ti.com writes:
Prepare for implementing GPIO as a platform driver.
Modifies omap_gpio_init() to make use of
Salut Paul,
On 12/8/2010 7:47 AM, Paul Walmsley wrote:
Salut Benoît,
On Tue, 7 Dec 2010, Cousson, Benoit wrote:
Salut Paul,
On 12/7/2010 2:25 AM, Paul Walmsley wrote:
Split the existing cm44xx.h file into cm1_44xx.h and cm2_44xx.h files
so they match their underlying OMAP hardware modules.
On Fri, Dec 10, 2010 at 12:22 AM, Ionut Nicu ionut.n...@mindbit.ro wrote:
I tried removing the first check and tested with the
userspace-dspbridge strmcopy application, but I noticed the DSP hangs if
I try to use it with anything else than the copy mode.
Are the other modes (rdma, zerocopy)
Hi Ionut,
On Thu, Dec 9, 2010 at 4:22 PM, Ionut Nicu ionut.n...@mindbit.ro wrote:
Hi Omar,
On Thu, 2010-12-09 at 23:47 +0200, Ionut Nicu wrote:
Reorganized some code in rmgr/node.c to increase its
readability. Most of the changes reduce the code
indentation level and simplifiy the code. No
In the omap_hwmod core, most of the SYSCONFIG register helper
functions do not directly write the register, but instead just modify
a value passed in.
This patch converts the _enable_wakeup() and _disable_wakeup() helper
functions to take a value argument and only modify it instead of
actually
Hi Charu,
I owe you an apology.
Kevin Hilman khil...@deeprootsystems.com writes:
[...]
I just noticed while testing on 36xx/Zoom3 that GPIO wakeups are no
longer working after this series.
The problem seems to be that for OMAP2+, this series removed manual
SYSCONFIG register setting in
Hi Paul,
Here is a small set of OMAP4 hwmod data updates.
Re-order properly the data that were a little bit shuffled during
the previous merge window.
Add the new reset flags introduced in 2.6.37 and that were not
used in the hwmod data. The OMAP2 and OMAP3 fixes should come soon.
Fix some
The original OMAP4 hwmod data files is fully generated from HW
database. But since the file is introduced incrementaly along
with driver that uses the data, it has to be splitted by the driver
owner and then re-merged by the maintainer.
Because of the similarity of the data, git is completely lost
The DMM is a piece of interconnect that need to be configured properly
for the tiler functionnality. It thus exposes some configuration registers
that were missing previously.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
---
Update the data for GPIO, UART, WD_TIMER and I2C in order to
support the new reset status flag introduce in the following
commit:
commit 2cb068149c365f1c2b10f2ece6786139527dcc16
OMAP: hwmod: Fix softreset status check for some new OMAP4 IPs
Without this flag properly set, the reset is done, but
Add IVA and DSP hwmods in order to allow the pm code to
initialize properly the processors devices during
omap2_init_processor_devices.
It will avoid the following warnings.
_init_omap_device: could not find omap_hwmod for iva
_init_omap_device: could not find omap_hwmod for dsp
Signed-off-by:
Fix opt clocks name in clock framework and hwmod.
Add the missing iclk in the ocp_if structure.
Add the HWMOD_CONTROL_OPT_CLKS_IN_RESET flag to ensure
the the GPIO optional clock is enable during reset.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Tested-by: Charulatha V ch...@ti.com
Cc: Paul
On Thu, Dec 09, 2010 at 10:18:48PM +, aaro.koski...@nokia.com wrote:
Hi,
Kevin Hilman [khil...@deeprootsystems.com]:
Ben Dooks ben-...@fluff.org writes:
Renaming stuff like this is going to have an impact on the userspace
as anyone looking through /sys's driver heirarchy is going
Paul Walmsley p...@pwsan.com writes:
Hi Kevin
On Thu, 9 Dec 2010, Kevin Hilman wrote:
Paul, do you want to submit a formal patch for this for 2.6.38? if not,
I can add a changelog and queue this with other PM core changes for 2.6.38.
we should probably come up with a patch for .38 that
* Kevin Hilman khil...@deeprootsystems.com [101209 11:33]:
As part of the GPIO conversion to platform_device/platform_driver,
commit 2fae7fbed072705d91e09ed393b2e580b2d895fc (OMAP: GPIO: prepare
for platform driver) removed hard-coded per-bank SYSCONFIG register
values in favor of using
Add new powerdomain API
int pwrdm_get_context_loss_count(struct powerdomain *pwrdm)
for checking how many times the powerdomain has lost context. The
loss count is the sum sum of the powerdomain off-mode counter, the
logic off counter and the per-bank memory off counter.
Cc: Paul Walmsley
Implement OMAP PM layer omap_pm_get_dev_context_loss_count() API by
creating similar APIs at the omap_device and omap_hwmod levels. The
omap_hwmod level call is the layer with access to the powerdomain
core, so it is the place where the powerdomain is queried to get the
context loss count.
NOTE:
Tony Lindgren t...@atomide.com writes:
* Kevin Hilman khil...@deeprootsystems.com [101209 11:33]:
As part of the GPIO conversion to platform_device/platform_driver,
commit 2fae7fbed072705d91e09ed393b2e580b2d895fc (OMAP: GPIO: prepare
for platform driver) removed hard-coded per-bank SYSCONFIG
* Kevin Hilman khil...@deeprootsystems.com [101207 17:06]:
Kernel was failing to boot on omap1611 based OSK boards due to
mis-configured SRAM size. Existing code was using a hard-coded value
for 250k, which was then rounded down by PAGE_SIZE. Increasing this to
256k allows kernel to boot on
Hi Benoit,
Benoit Cousson b-cous...@ti.com writes:
Hi Paul,
Here is a collections of fixes and clock nodes addition done on OMAP3
and OMAP4 clock data files.
I have included the one that Thara already submitted after fixing the
various comments done on the original version.
That
Benoit Cousson b-cous...@ti.com writes:
Hi Paul,
Here is a small set of OMAP4 hwmod data updates.
Re-order properly the data that were a little bit shuffled during
the previous merge window.
Add the new reset flags introduced in 2.6.37 and that were not
used in the hwmod data. The OMAP2
* Kevin Hilman khil...@deeprootsystems.com [101209 07:40]:
Vitaly Wool vitalyw...@gmail.com writes:
+static void omap2_pm_end(void)
+{
+ suspend_state = PM_SUSPEND_ON;
+ return;
+}
Redundant return.
but harmless
I'll queue this fix, will leave out the harmless
Hi Tony,
On Monday 06 December 2010 20:32:13 Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [101125 03:13]:
Hi,
On Thu, Nov 25, 2010 at 12:17:59PM +0100, Laurent Pinchart wrote:
pass platform_data as an argument to this call ? Then remove the static
inline and export this one ?
1 - 100 of 113 matches
Mail list logo
