This patch fixes these warnings when building kernel for OMAP3EVM
only.
CC arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.o
arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c:95: warning:
'dsp_24xx_wkdeps' defined but not used
arch/arm/mach-omap2/clockdomains2xxx_3xxx_data.c:119: warning:
On Thu, Feb 10, 2011 at 7:11 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Thu, Feb 10, 2011 at 06:29:41PM +, Dave Martin wrote:
On Thu, Feb 10, 2011 at 2:46 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Thu, Feb 10, 2011 at 02:13:13PM +, Dave Martin
On Thu, Feb 10, 2011 at 9:38 PM, Kevin Hilman khil...@ti.com wrote:
Santosh Shilimkar santosh.shilim...@ti.com writes:
[...]
The SD card gets suspended, but nothing else seems to happen, and I
can't resume the system.
Am I doing something wrong?
MMC suspend is broken. I use ramdisk-ext3
On Thu, Feb 10, 2011 at 10:17 PM, Kevin Hilman khil...@ti.com wrote:
Dave Martin dave.mar...@linaro.org writes:
* Use BSYM() to get the correct Thumb branch address
for adr Rd, label
* Fix an out-of-range ADR when building for ARM
* Correctly call es3_sdrc_fix as Thumb when copied to
On Fri, Feb 11, 2011 at 09:33:56AM +, Dave Martin wrote:
Agreed -- actually, I suspected we might need to support this. But I
don't think solving this problem (= keeping the fixup implementation
in memory and enhancing the module loader) solved the
Jean,
On Fri, Feb 11, 2011 at 12:53 AM, jean.pi...@newoldbits.com wrote:
From: Jean Pihet j-pi...@ti.com
Implement OMAP PM layer omap_pm_set_max_dev_wakeup_lat 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
Hi,
I'm trying to figure out why my display which have 18bpp doesn't show
properly colors.
As I can understand from DSS when I set 18bpp 24bpp is used just 2
data bit aren't connected
so everything should be fine. Anyway my tux looks little bit red ;).
Any ideas? I use old 2.6.29-rc3 kernel.
On Fri, 11 Feb 2011 12:15:18 +0530
Keerthy j-keer...@ti.com wrote:
From: Richard woodruff r-woodru...@ti.com
ProDB00017052 - ARDY interrupt reasserted after being cleared.
This errata caused intermittent i2c instabilty(1 error per 3 hours) on several
customer platforms. After applying the
On Fri, Feb 11, 2011 at 10:13 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Feb 11, 2011 at 09:33:56AM +, Dave Martin wrote:
Agreed -- actually, I suspected we might need to support this. But I
don't think solving this problem (= keeping the fixup implementation
in
dmtimer adaptation to platform_driver.
This patch series is adaptation of dmtimer code to platform driver
using omap_device and omap_hwmod abstraction.
Baseline:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git
Branch: master
Test Platforms:
OMAP1710
OMAP2420
OMAP2430
From: Thara Gopinath th...@ti.com
Add dmtimer data.
Signed-off-by: Thara Gopinath th...@ti.com
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Acked-by: Cousson, Benoit b-cous...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 634
From: Thara Gopinath th...@ti.com
Add dmtimer data.
Signed-off-by: Thara Gopinath th...@ti.com
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Acked-by: Cousson, Benoit b-cous...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 633
1 files changed,
switch-over to platform device driver through following changes:
(a) call to dmtimer initialization routine from timer-gp.c is
removed (b) initiate dmtimer early initialization from omap2_init_common_hw
in io.c (c) modify plat-omap/dmtimer routines to use new register map and
platform data.
From: Thara Gopinath th...@ti.com
Add device name to OMAP2 dmtimer fclk nodes so that the fclk nodes can be
retrieved by doing a clk_get with the corresponding device pointers or
device names.
NOTE: gpt1_fck is modified in patch-10 when we switch to platform device
driver. This is to make sure
Add pm_runtime support to dmtimer. Since dmtimer is used during
early boot before pm_runtime is initialized completely there are
provisions to enable/disable clocks directly in the code during
early boot.
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
[p-bas...@ti.com: added pm_runtime
The low-level read and write access routines wait on
write-pending register in posted mode to make sure that
previous write is complete on respective registers.
This waiting is done in an infinite while loop. Now it
is being modified to use timeout instead.
Signed-off-by: Tarun Kanti DebBarma
Add routines to converts dmtimers to platform devices. The device data
is obtained from hwmod database of respective platform and is registered
to device model after successful binding to driver. It also provides
provision to access timers during early boot when pm_runtime framework
is not
From: Thara Gopinath th...@ti.com
Add dmtimer platform driver functions which include:
(1) platform driver initialization
(2) driver probe function
(3) driver remove function
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Signed-off-by: Thara Gopinath th...@ti.com
Acked-by: Cousson,
From: Cousson, Benoit b-cous...@ti.com
Add dmtimer data.
Signed-off-by: Cousson, Benoit b-cous...@ti.com
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 623
arch/arm/plat-omap/include/plat/dmtimer.h |2 +
From: Thara Gopinath th...@ti.com
Convert OMAP1 dmtimers into a platform devices and then registers with
device model framework so that it can be bound to corresponding driver.
Signed-off-by: Thara Gopinath th...@ti.com
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Acked-by: Cousson,
From: Thara Gopinath th...@ti.com
Add dmtimer data.
Signed-off-by: Thara Gopinath th...@ti.com
Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com
Acked-by: Cousson, Benoit b-cous...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 649
1 files changed,
On Thu, Feb 10, 2011 at 06:44:50PM +0530, Balaji T K wrote:
In OMAP4 Blaze and Panda, 32KHz clock to WLAN is supplied from Phoenix
TWL6030.
The 32KHz clock state (ON/OFF) is configured in CLK32KG_CFG_[GRP, TRANS,
STATE]
register. This follows the same register programming model as other
On Thu, Feb 10, 2011 at 06:45:26PM +0530, Balaji T K wrote:
In Blaze and Panda, 32KHz clock - CLK32KG to WLAN is supplied
from Phoenix TWL6030.
Add CLK32KG platform data to blaze and omap4panda board file.
Signed-off-by: Balaji T K balaj...@ti.com
Acked-by: Mark Brown
Hi,
On Thu, 2011-01-27 at 11:17 +, Sumit Semwal wrote:
From: Mayuresh Janorkar ma...@ti.com
Enable DSS2 and OMAPFB for OMAP4 in Kconfig
The indentation in this patch seems to be a bit inconsistent with the
current Kconfigs. For example, you use two tabs in the help lines, and
the current
On Wed, Feb 9, 2011 at 10:08 PM, Gadiyar, Anand gadi...@ti.com wrote:
On Wed, Feb 9, 2011 at 7:25 PM, Raghuveer Murthy
raghuveer.mur...@ti.com wrote:
Adding DVI support to OMAP4 PandaBoard.
PandaBoard uses TFP410 DVI Framer chip
http://focus.ti.com/lit/ds/symlink/tfp410.pdf
The TFP410 gets
Hi,
I can't really comment on the HWMOD parts, but beside the Kconfig
indentation comments this patch set looks good to me.
Tomi
On Thu, 2011-01-27 at 16:47 +0530, ext Sumit Semwal wrote:
This patch series enables support for OMAP4 DSS, and adds hwmod support
for dss, dispc, dsi1, dsi2,
Hi,
This patch set looks good, no comments from me. I'll take this to my
tree.
Tomi
On Mon, 2011-01-31 at 16:27 +, Sumit Semwal wrote:
Currently, clock database has dev, clock-name tuples for DSS2. Because of
this, the clock names are different across different OMAP platforms.
This
On Fri, Feb 11, 2011 at 12:07 AM, Kevin Hilman khil...@ti.com wrote:
Kevin Hilman khil...@ti.com writes:
Dave Martin dave.mar...@linaro.org writes:
* Use BSYM() to get the correct Thumb branch address
for adr Rd, label
* Fix an out-of-range ADR when building for ARM
* Correctly
Russell,
-Original Message-
From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
Sent: Friday, February 04, 2011 3:49 PM
To: Russell King - ARM Linux
Cc: linux-omap@vger.kernel.org; ccr...@android.com;
catalin.mari...@arm.com; linus.ml.wall...@gmail.com; linux-arm-
Hi,
I use this thread as I expect people following it, is exactly
the audience I am looking out for.
I am currently implementing a generic framework for CPU idle
state accounting.
X86 CPUs can do quite some magic behind the OS and might enter
deeper sleep states or might not enter them, even
(+ Kevin, Paul)
-Original Message-
From: Thomas Renninger [mailto:tr...@suse.de]
Sent: Friday, February 11, 2011 8:09 PM
To: Santosh Shilimkar
Cc: Tony Lindgren; linux-omap@vger.kernel.org; Jean Pihet-XID
Subject: Are there CPU sleep residency HW counters in OMAP? Was: Re:
[PATCH]
Remove the custom restore_control_register() and use the exported
set_cr() instead to set the system control register(SCTRL) value.
No functional change.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/pm34xx.c |7 +--
1
Add a description field to each idle C-state. This helps to give
better data with PowerTop and one don't have to refer to the code
to link what Cx means from system point of view while analysing
PowerTop data.
No functional change.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Cc:
Op 11 feb 2011, om 13:12 heeft Bryan Wu het volgende geschreven:
On Wed, Feb 9, 2011 at 10:08 PM, Gadiyar, Anand gadi...@ti.com wrote:
On Wed, Feb 9, 2011 at 7:25 PM, Raghuveer Murthy
raghuveer.mur...@ti.com wrote:
Adding DVI support to OMAP4 PandaBoard.
PandaBoard uses TFP410 DVI Framer
On Fri, Feb 11, 2011 at 10:52:17AM +, Dave Martin wrote:
On Fri, Feb 11, 2011 at 10:13 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Feb 11, 2011 at 09:33:56AM +, Dave Martin wrote:
Agreed -- actually, I suspected we might need to support this. But I
don't
The following patch series implements infrastructure to save/restore
CPU state on suspend/resume PM events, and updates SA11x0, PXA and
Samsung platforms to use this.
Only only ARM920, ARM926, SA11x0, XScale, XScale3, V6 and V7 CPUs are
supported.
I've build-tested this for Assabet, PXA, and
On Fri, Feb 11, 2011 at 4:05 PM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Feb 11, 2011 at 10:52:17AM +, Dave Martin wrote:
On Fri, Feb 11, 2011 at 10:13 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Fri, Feb 11, 2011 at 09:33:56AM +, Dave Martin
This allows the cache/processor/fault glue to be more easily used
from assembler code.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/include/asm/cacheflush.h | 133 +
arch/arm/include/asm/cpu-multi32.h | 69
arch/arm/include/asm/cpu-single.h |
This adds core support for saving and restoring CPU coprocessor
registers for suspend/resume support. This contains support for suspend
with ARM920, ARM926, SA11x0, PXA25x, PXA27x, PXA3xx, V6 and V7 CPUs.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/mach-pxa/include/mach/pm.h |5 +-
arch/arm/mach-pxa/palmz72.c |2 +-
arch/arm/mach-pxa/pm.c |5 -
arch/arm/mach-pxa/pxa25x.c |4 +-
arch/arm/mach-pxa/pxa27x.c |4 +-
Convert sa11x0 to use the generic CPU suspend/resume support, rather
than implementing its own version. Tested on Assabet.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/mach-sa1100/pm.c| 12 ++-
arch/arm/mach-sa1100/sleep.S | 72
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/mach-s3c64xx/sleep.S | 63 +-
arch/arm/mach-s5pv210/sleep.S | 104 +--
arch/arm/plat-s3c24xx/sleep.S | 57 +
Allow the generic sleep code to be used with SMP CPU idle by storing
N CPU stack pointers rather than just one.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/kernel/sleep.S | 26 +-
1 files changed, 25 insertions(+), 1 deletions(-)
diff --git
Hi Shweta,
Indeed the error checking is not good in this version.
I have inlined some comments.
On Fri, Feb 11, 2011 at 11:23 AM, Gulati, Shweta shweta.gul...@ti.com wrote:
Jean,
On Fri, Feb 11, 2011 at 12:53 AM, jean.pi...@newoldbits.com wrote:
From: Jean Pihet j-pi...@ti.com
Implement
On Fri, Feb 11, 2011 at 04:17:48PM +, Dave Martin wrote:
Yep -- I'm still applying my original patch to work around that, but
it sounds like I need to tidy that up. Can you elaborate on what you
meant by defining a KEEP_EXIT macro to handle this?
diff --git a/arch/arm/kernel/vmlinux.lds.S
Hi Hiroshi,
Hiroshi DOYU hiroshi.d...@nokia.com writes:
From: ext Tony Lindgren t...@atomide.com
Subject: Re: [PATCH v5 0/5] omap: mailbox: hwmod support
Date: Wed, 9 Feb 2011 10:32:19 -0800
* Omar Ramirez Luna omar.rami...@ti.com [110202 11:37]:
Mailbox hwmod support for OMAP 2,3,4.
Hi Sumit,
While I was trying to merge that patch for 2.6.39, I found some changes
that I didn't expected. I will take care of cleaning this patch, but I'd
to get the rational first.
All the other comments are purely cosmetic.
On 1/27/2011 12:17 PM, Semwal, Sumit wrote:
From: Benoit
On Fri, 11 Feb 2011 20:42:12 +0530
Santosh Shilimkar santosh.shilim...@ti.com wrote:
Add a description field to each idle C-state. This helps to give
better data with PowerTop and one don't have to refer to the code
to link what Cx means from system point of view while analysing
PowerTop
Missed adding linux omap
On Tuesday 08 February 2011 02:00 PM, Shubhrajyoti wrote:
Hello,
Any comments/suggestions.
Thanks,
On Monday 27 December 2010 11:21 AM, shubhrajy...@ti.com wrote:
From: Abraham Arcex0066...@ti.com
Enable Runtime PM functionality in OMAP4 driver based on the
This patch set adds support for TI816X processor series. This series includes
DM8168, C6A816x and AM389x devices.
The details can be found at following links:
http://focus.ti.com/general/docs/gencontent.tsp?contentId=77960
http://www.ti.com/ww/en/dsp/davinci-netra/index.shtml
This series is
This patch updates the common platform files with TI816X support.
The approach taken in this patch is to add TI816X as part of OMAP3 variant where
the cpu class is considered as OMAP34XX and the type is TI816X. This means, both
cpu_is_omap34xx() and cpu_is_ti816x() checks return success on
This patch updates the common machine specific source files with support for
TI816X.
Signed-off-by: Hemant Pedanekar hema...@ti.com
---
arch/arm/mach-omap2/clock3xxx_data.c |5 +++-
arch/arm/mach-omap2/common.c | 21 +++
arch/arm/mach-omap2/control.h
This patch adds minimal support and build configuration for TI816X EVM.
Signed-off-by: Hemant Pedanekar hema...@ti.com
---
arch/arm/mach-omap2/Kconfig |5 +++
arch/arm/mach-omap2/Makefile |1 +
arch/arm/mach-omap2/board-ti8168evm.c | 57
This patch adds support for low level debugging on TI816X boards. Currently the
support for UART3 console on TI816X EVM is added.
Signed-off-by: Hemant Pedanekar hema...@ti.com
---
arch/arm/mach-omap2/include/mach/debug-macro.S | 12
arch/arm/plat-omap/include/plat/serial.h
* Hemant Pedanekar hema...@ti.com [110211 09:32]:
This patch set adds support for TI816X processor series. This series includes
DM8168, C6A816x and AM389x devices.
Thanks for your patience with the changes, this looks good to me now.
Can you please post it one more time with linux-arm-kernel
The IRQ numbering for the IVA and DSP mailboxes was switched due
to the wrong ordering in the OMAP2 mbox list. Switch the ordering
so DSP is first and matches all the other SoCs.
Tested on OMAP2420/n810.
Signed-off-by: Kevin Hilman khil...@ti.com
---
arch/arm/mach-omap2/mailbox.c |2 +-
1
The pointer math in omap_mbox_get() is not quite right, and leads to
passing NULL to strcmp() when searching for an mbox that is not first
in the list.
Convert to using array indexing as is done in all the other functions
which walk the mbox list.
Tested on OMAP2420/n810, OMAP3630/zoom3,
On Monday, January 31, 2011, Rafael J. Wysocki wrote:
On Monday, January 31, 2011, Alan Stern wrote:
On Mon, 31 Jan 2011, Kevin Hilman wrote:
I understand how this works, but frankly I'm still a bit fuzzy on why.
I guess I'm still missing a good understanding of what interfering
On Fri, 11 Feb 2011, Rafael J. Wysocki wrote:
The reason why runtime suspend is not allowed during system power
transitions
if the following race:
- A device has been suspended via a system suspend callback.
- The runtime PM framework executes a (scheduled) suspend on that device,
Rafael J. Wysocki r...@sisk.pl writes:
On Monday, January 31, 2011, Rafael J. Wysocki wrote:
On Monday, January 31, 2011, Alan Stern wrote:
On Mon, 31 Jan 2011, Kevin Hilman wrote:
I understand how this works, but frankly I'm still a bit fuzzy on why.
I guess I'm still missing a
On Thu, 10 Feb 2011, Catalin Marinas wrote:
On Thu, 2011-02-10 at 13:04 +, Russell King - ARM Linux wrote:
On Wed, Feb 09, 2011 at 10:01:33AM +, Catalin Marinas wrote:
Could we make the domains usage a run-time feature based on the
architecture version? For ARMv7, we need to have
On Fri, Feb 11, 2011 at 03:45:51PM -0500, Nicolas Pitre wrote:
The patch below is making the code more straight forward regardless of
any swp emulation issues.
I don't know where you get that idea from. What it does is make a kernel
built with a standard set of options have differing
On Friday, February 11, 2011, Kevin Hilman wrote:
Rafael J. Wysocki r...@sisk.pl writes:
On Monday, January 31, 2011, Rafael J. Wysocki wrote:
On Monday, January 31, 2011, Alan Stern wrote:
On Mon, 31 Jan 2011, Kevin Hilman wrote:
I understand how this works, but frankly I'm
Omar Ramirez Luna omar.rami...@ti.com writes:
Mailbox hwmod support for OMAP 2,3,4.
This was tested on OMAP3 (3430, 3630), minor testing
was made on OMAP4.
No testing on OMAP2 since I don't have the hardware.
To help in testing, I wrote a simple mailbox loopback test module for
OMAP2/3/4
Hi Dave,
Dave Martin dave.mar...@linaro.org writes:
This set of patches, along with some other patches under
discussion on alkml, should enable omap3 and omap4 kernels to be
built with CONFIG_THUMB2_KERNEL.
OK, I tried some more testing with your 'dirty' branch merged with my PM
branch.
Rafael J. Wysocki r...@sisk.pl writes:
On Friday, February 11, 2011, Kevin Hilman wrote:
Rafael J. Wysocki r...@sisk.pl writes:
On Monday, January 31, 2011, Rafael J. Wysocki wrote:
On Monday, January 31, 2011, Alan Stern wrote:
On Mon, 31 Jan 2011, Kevin Hilman wrote:
I
Hi Anand,
Anand S Sawant saw...@ti.com writes:
omap_sr_probe() creates the smartreflex debug directory and its
underlying nvalue debug directory. These directories are removed in
omap_sr_remove().
Basic smartreflex functionality tested on OMAP3630 Zoom3 OMAP4430 SDP
Signed-off-by: Anand
On Saturday, February 12, 2011, Kevin Hilman wrote:
Rafael J. Wysocki r...@sisk.pl writes:
On Friday, February 11, 2011, Kevin Hilman wrote:
Rafael J. Wysocki r...@sisk.pl writes:
On Monday, January 31, 2011, Rafael J. Wysocki wrote:
On Monday, January 31, 2011, Alan Stern wrote:
Hi Manju,
G, Manjunath Kondaiah manj...@ti.com writes:
The omap1_defconfig build on pm branch throughs below build error:
CC drivers/i2c/busses/i2c-omap.o
drivers/i2c/busses/i2c-omap.c:1173: error: lvalue required as unary ''
operand
make[3]: *** [drivers/i2c/busses/i2c-omap.o]
On Fri, Feb 11, 2011 at 8:17 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
This adds core support for saving and restoring CPU coprocessor
registers for suspend/resume support. This contains support for suspend
with ARM920, ARM926, SA11x0, PXA25x, PXA27x, PXA3xx, V6 and V7 CPUs.
On Fri, Feb 11, 2011 at 8:17 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
This allows the cache/processor/fault glue to be more easily used
from assembler code.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/include/asm/cacheflush.h | 133
On Fri, Feb 11, 2011 at 8:19 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
Allow the generic sleep code to be used with SMP CPU idle by storing
N CPU stack pointers rather than just one.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
---
arch/arm/kernel/sleep.S | 26
-Original Message-
From: Jarkko Nikula [mailto:jhnik...@gmail.com]
Sent: Friday, February 11, 2011 10:37 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; linux-arm-
ker...@lists.infradead.org
Subject: Re: [PATCH] omap3: cpuidle: Add description field to each
73 matches
Mail list logo
