As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
Signed-off-by: Ajay Kumar Gupta ajay.gu...@ti.com
---
Patch created against recent Linus's tree.
Changes from v1:
On Mon, Oct 25, 2010 at 5:17 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
So that avoid nonkillable process.
Signed-off-by: Fernando Guzman Lugo x0095...@ti.com
---
.../staging/tidspbridge/include/dspbridge/sync.h | 13 +++--
1 files changed, 11 insertions(+), 2
On Wed, Nov 3, 2010 at 7:31 PM, Rene Sapiens rene.sapi...@ti.com wrote:
When calling the DSP's remote functions, the DSP returns error
codes different from the ones managed by the kernel, the
function's return value is shared with the MPU using a shared
structure. This patch overwrites those
On Fri, Nov 5, 2010 at 12:01 PM, Ionut Nicu ionut.n...@gmail.com wrote:
From: Felipe Contreras felipe.contre...@gmail.com
The current code was always returning a non-zero status value
to userspace applications when this ioctl was called.
The error code was ENODATA, which isn't actually an
On Fri, Nov 5, 2010 at 11:31 AM, Ionut Nicu ionut.n...@gmail.com wrote:
Changes since v1:
* Split the mgr_enum_node_info patch into two patches:
one that fixes the issue and one that reorganizes the
code.
Ionut Nicu (3):
staging: tidspbridge: fix mgr_enum_node_info
staging: tidspbridge:
Hi Ionut,
On Sun, Nov 21, 2010 at 4:46 AM, Ionut Nicu ionut.n...@gmail.com wrote:
This set of patches replaces some of the redundant components of
the tidspbridge driver, such as:
* wrapper functions for kmalloc/kfree
* custom bitmap implementation
* custom linked list implementation
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
Hello.
On 06-12-2010 11:13, Ajay Kumar Gupta wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
I'm not fond of the whole approach. I'm not sure why
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 convention for omap device naming is omap_XXX.
Rename the device name used in clock dev noded in order to stick
to this naming convention.
Signed-off-by: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
Cc: Rajendra Nayak rna...@ti.com
---
arch/arm/mach-omap1/clock_data.c
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.
Signed-off-by: Benoit Cousson b-cous...@ti.com
c: Paul Walmsley p...@pwsan.com
Cc: Kevin Hilman khil...@deeprootsystems.com
Cc: Rajendra Nayak rna...@ti.com
Cc: Ben
On Fri, Dec 03, 2010 at 07:08:53PM +0530, Gupta, Ajay Kumar wrote:
We already have generic APIs so I think we can pass function pointers to
musb driver via struct omap_musb_board_data,
struct omap_musb_board_data {
+ void(*phy_on) (void)
+ void(*phy_off) (void)
+ void
On Fri, Dec 03, 2010 at 07:08:53PM +0530, Gupta, Ajay Kumar wrote:
We already have generic APIs so I think we can pass function pointers
to
musb driver via struct omap_musb_board_data,
struct omap_musb_board_data {
+ void(*phy_on) (void)
+ void(*phy_off) (void)
+ void
On Mon, Dec 06, 2010 at 05:24:53PM +0530, Gupta, Ajay Kumar wrote:
On Fri, Dec 03, 2010 at 07:08:53PM +0530, Gupta, Ajay Kumar wrote:
We already have generic APIs so I think we can pass function pointers
to
musb driver via struct omap_musb_board_data,
struct omap_musb_board_data {
+ void
Hi,
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
I'm not fond of the whole approach. I'm not sure why accesses to the
control registers are such
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
(1) Add new fields and data structures to support dmtimer conversion
to platform driver.
(2) Constants to identify IP revision so that Highlander IP in OMAP 4
can be distinguished.
(3) field to identify OMAP4 abe timers.
(4) Interface function to support early boot.
Signed-off-by: Tarun Kanti
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: 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
Reviewed-by: Varadarajan, Charulatha ch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 624
1
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
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
Reviewed-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
Reviewed-by: Varadarajan, Charulatha ch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |
dmtimer adaptation to platform_driver.
This patch series is adaptation of dmtimer code to platform driver
using omap_device and omap_hwmod abstraction.
Tested on following platforms:
OMAP4430, OMAP3430, OMAP3630, OMAP2430
OMAP2420 -- Image with omap2plus_defconfig in too large to download on
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
Reviewed-by: Cousson,
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
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 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
Reviewed-by: Varadarajan, Charulatha ch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c |
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
Reviewed-by: Varadarajan, Charulatha ch...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c |
As previously requested.
The following is the behaviour of the latest mainline kernel on the LDP3430
platform.
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state can only be entered from
Kevin,
-Original Message-
From: linux-input-ow...@vger.kernel.org [mailto:linux-input-
ow...@vger.kernel.org] On Behalf Of Kevin Hilman
Sent: Thursday, September 30, 2010 7:21 PM
To: Arce, Abraham
Cc: linux-in...@vger.kernel.org; linux-omap@vger.kernel.org
Subject: Re: [PATCH v6
Patch fix following compilation warning:
arch/arm/mach-omap1/board-htcherald.c:442:
warning: large integer implicitly truncated to unsigned type
Hopefully this is just a typo.
Signed-off-by: Marek Belisko marek.beli...@open-nandra.com
---
arch/arm/mach-omap1/board-htcherald.c |2 +-
1 files
Fix following compilation warning:
arch/arm/mach-omap1/pm_bus.c: In function 'omap1_pm_runtime_resume':
arch/arm/mach-omap1/pm_bus.c:51: warning: unused variable 'ret'
Signed-off-by: Marek Belisko marek.beli...@open-nandra.com
---
arch/arm/mach-omap1/pm_bus.c |1 -
1 files changed, 0
Fix following compilation warning:
arch/arm/mach-omap1/mailbox.c: In function 'omap1_mbox_probe':
arch/arm/mach-omap1/mailbox.c:148: warning: unused variable 'i'
Signed-off-by: Marek Belisko marek.beli...@open-nandra.com
---
arch/arm/mach-omap1/mailbox.c |1 -
1 files changed, 0
Hi,
Where can I obtain the TI ITBOK (Is The Board OK) sources for TI
BeagleBoard? I have the sources for the OMAP35x EVM but it doesn't execute so
well, probably because it requires changes to work with BeagleBoard hardware.
So I was wondering if someone has already adapted ITBOK for
Ruseell,
On Thu, Dec 2, 2010 at 9:43 AM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Thu, Dec 2, 2010 at 9:20 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Thu, Dec 02, 2010 at 08:50:07AM -0600, Guzman Lugo, Fernando wrote:
On Thu, Dec 2, 2010 at 6:33 AM, Russell King
On Mon, Dec 06, 2010 at 09:16:23AM -0600, Kanigeri, Hari wrote:
Ruseell,
On Thu, Dec 2, 2010 at 9:43 AM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Thu, Dec 2, 2010 at 9:20 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Thu, Dec 02, 2010 at 08:50:07AM -0600,
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state can only be entered from initialized,
idle, or disabled state
On Tue, Dec 07, 2010 at 05:14:07AM +0530, Tarun Kanti DebBarma wrote:
dmtimer adaptation to platform_driver.
This patch series is adaptation of dmtimer code to platform driver
using omap_device and omap_hwmod abstraction.
Tested on following platforms:
OMAP4430, OMAP3430, OMAP3630,
Hi,
Sorry for the delay.
* Pedanekar, Hemant hema...@ti.com [101130 17:36]:
Tony Lindgren wrote on Tuesday, November 30, 2010 12:59 AM:
Thanks for clarifications. I have some concerns though:
1) I will eventually end up preceeding existing OMAP3 ckecks to have
cpu_is_34xx() fail. Fo
On Tue, Dec 07, 2010 at 05:14:09AM +0530, Tarun Kanti DebBarma wrote:
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
Reviewed-by: Varadarajan,
On Tue, Dec 07, 2010 at 05:14:13AM +0530, Tarun Kanti DebBarma wrote:
(1) Add new fields and data structures to support dmtimer conversion
to platform driver.
(2) Constants to identify IP revision so that Highlander IP in OMAP 4
s/OMAP 4/OMAP4
can be distinguished.
(3) field to identify
Hello.
Gupta, Ajay Kumar wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
I'm not fond of the whole approach. I'm not sure why accesses to the
On Mon, Dec 06, 2010 at 07:59:59AM -0800, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state
These patches enable the omap kernel to build and work in
Thumb-2 (CONFIG_THUMB2_KERNEL).
They may make useful reading for all low-level BSP maintainers,
since in general similar issues tend to crop up whenever migrating
code to support Thumb-2.
Tested on: omap3 (Beagle xM A2)
Not tested on any
almost all code for v7+ platforms) is deprecated/incorrect.
ENDPROC() tags the affected symbol as a function symbol, which will
ensure that link-time fixups don't accidentally switch to the
wrong instruction set.
omap_secondary_startup might still need to be changed to ARM,
depending on the
For the Thumb-2 case, the wfi mnemonic is used, since in this
case the tools will necessarily be new enough to support it.
Signed-off-by: Dave Martin dave.mar...@linaro.org
---
KernelVersion: 2.6.37-rc4
arch/arm/mach-omap2/include/mach/omap4-common.h |5 +
1 files changed, 5
sleep34xx.S, sram34xx.S:
* Added ENDPROC() directives for all exported function symbols.
Without these, exported function symbols are not correctly
identified as Thumb by the linker, causing incorrect linkage.
This is needed to avoid some calls to the functions ending up
with
On 5 December 2010 23:04, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Sun, Dec 05, 2010 at 10:18:27PM +, Catalin Marinas wrote:
On 5 December 2010 11:43, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
diff --git a/arch/arm/kernel/vmlinux.lds.S
* Sergei Shtylyov sshtyl...@mvista.com [101206 09:04]:
Hello.
Gupta, Ajay Kumar wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
I'm not fond
On Tue, Dec 07, 2010 at 05:14:14AM +0530, Tarun Kanti DebBarma wrote:
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
On Mon, 8 Nov 2010 13:08:44 +0200, Grazvydas Ignotas wrote:
On Sun, Nov 7, 2010 at 9:40 AM, [AvataR] public.ava...@x wrote:
Hi. After moving to upstream 2.6.3{5,6,7} kernels, i forced to use jffs2
instead of ubifs, because of lot CRC errors. If i use prefetch/dma, i
can attach to ubi,
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 09:12]:
On Mon, Dec 06, 2010 at 07:59:59AM -0800, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
On 6 December 2010 17:35, Dave Martin dave.mar...@linaro.org wrote:
* Explicitly build a few parts of sleep34xx.S as ARM.
* lock_scratchpad_sem is kept as ARM because of the need to
synchronise with hardware (?) using the SWP instruction.
* save_secure_ram_context and
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
NET: Registered protocol family 16
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2: enabled state can only be entered from
On Tue, Dec 07, 2010 at 05:14:15AM +0530, Tarun Kanti DebBarma wrote:
Add routines to converts dmtimers to platform devices. The device data
s/converts/convert
is obtained from hwmod database of respective platform and is registered
to device model after successful binding to driver. It also
On Mon, 6 Dec 2010, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
NET: Registered protocol family 16
[ cut here ]
WARNING: at arch/arm/mach-omap2/omap_hwmod.c:1185
_omap_hwmod_enable+0x34/0x114()
omap_hwmod: wd_timer2:
Hi,
On Mon, Dec 6, 2010 at 6:17 PM, Catalin Marinas catalin.mari...@arm.com wrote:
On 6 December 2010 17:35, Dave Martin dave.mar...@linaro.org wrote:
* Explicitly build a few parts of sleep34xx.S as ARM.
* lock_scratchpad_sem is kept as ARM because of the need to
synchronise
On Tue, Dec 07, 2010 at 05:14:16AM +0530, Tarun Kanti DebBarma wrote:
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
* Anand Gadiyar gadi...@ti.com [101130 13:56]:
On 12/1/2010 3:10 AM, Tony Lindgren wrote:
* Anand Gadiyar gadi...@ti.com [101129 09:16]:
- Add platform init code for EHCI on OMAP4
- Add pad configuration for PHY and TLL modes
Signed-off-by: Anand Gadiyar gadi...@ti.com
Looks OK to
Hi,
* Peter Barada pet...@logicpd.com [101122 22:09]:
Also, where in the kernel is the mux setup for the UARTs done? I'd
like to use UART2 and am not sure how to wire it into the
kernel(i.e. setup the mux for it as those pins are in mode 7) and
want to follow the same style as that for
* Laurent Pinchart laurent.pinch...@ideasonboard.com [101124 18:45]:
From: Tuukka Toivonen tuukka.o.toivo...@nokia.com
Add new/changed base address definitions and resources for
OMAP3630 ISP.
The OMAP3430 CSI2PHY block is same as the OMAP3630 CSIPHY2
block. But the later name is chosen as
* 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 ?
Yes indeed, why ? :-)
I guess things like that are difficult to spot
* Srikar ext-srikar.1.bhavanaray...@nokia.com [101125 07:40]:
To support tsc2005 driver on rx51,added tsc2005
intialization data ,functions to enable/disable
tsc2005 and loading driver on rx51.
#include linux/input/matrix_keypad.h
#include linux/spi/spi.h
#include linux/wl12xx.h
* Hemanth V heman...@ti.com [101129 02:48]:
From 8082870cc704d901d98cf0d6af90e45860927ceb Mon Sep 17 00:00:00 2001
From: Hemanth V heman...@ti.com
Date: Thu, 26 Aug 2010 17:49:12 +0530
Subject: [PATCH] Platform changes for CMA3000 Accelerometer driver
Update 4430 SDP board file with
* Felipe Balbi ba...@ti.com [101203 04:35]:
On Thu, Dec 02, 2010 at 02:27:36PM -0800, Tony Lindgren wrote:
Great, yeah I'll merge them into linux-omap master branch for testing
probably later on today.
Cool, I just made the updates Mike asked and it's now all good again
:-p
It will get
After Charu's GPIO hwmod patches, GPIO initialization on N800 emits
the following messages for all GPIO banks:
omap_hwmod: gpio1: cannot be enabled (3)
This is due to OMAP24XX_ST_GPIOS_SHIFT being defined as a bitmask.
Fix this and also fix two other macros that had the same problem.
Thanks to
From: Ravi Ramachandra r.ramachan...@ti.com
This patch implements a simple TILER Container Manager (TCM).
Signed-off-by: Ravi Ramachandra r.ramachan...@ti.com
Signed-off-by: Lajos Molnar mol...@ti.com
Signed-off-by: David Sin david...@ti.com
---
drivers/misc/tiler/tcm/Makefile|1 +
Tiling and Isometric Lightweight Engine for Rotation (TILER) driver
=
Dynamic Memory Manager (DMM) is a hardware block made by Texas Instruments.
Within the DMM exists at least one TILER hardware component. Its purpose is to
organize video/image memory in a 2-dimensional fashion to limit
From: Lajos Molnar mol...@ti.com
This patch contains the TILER interface file and the documentation.
Signed-off-by: Lajos Molnar mol...@ti.com
Signed-off-by: David Sin david...@ti.com
---
Documentation/arm/OMAP/TILER | 126 ++
include/linux/tiler.h| 173
From: Lajos Molnar mol...@ti.com
This patch contains the TILER driver and implementation of the TILER
block manipulation and mapping functions.
It also contains the makefile and config file for the TILER driver.
Signed-off-by: Lajos Molnar mol...@ti.com
Signed-off-by: David Sin david...@ti.com
Add DMM device support for OMAP utilizing the
OMAP HWMOD framework.
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
Signed-off-by: David Sin david...@ti.com
---
arch/arm/mach-omap2/Makefile |2 +
arch/arm/mach-omap2/dmm-omap44xx.c | 80
2 files
From: Lajos Molnar mol...@ti.com
This patch contains information on TILER geometry, as well as
tiler_view_t object manipulation functions.
It also contains an internal TILER header file to share geometric
information with other TILER files.
Signed-off-by: Lajos Molnar mol...@ti.com
From: Lajos Molnar mol...@ti.com
This patch defined the TILER Container Manager (TCM) interface and
provides utility methods for implementing a TCM.
Signed-off-by: Lajos Molnar mol...@ti.com
Signed-off-by: David Sin david...@ti.com
Signed-off-by: Ravi Ramachandra r.ramachan...@ti.com
---
From: Lajos Molnar mol...@ti.com
This patch links the TILER driver into the Linux kernel build
and config system.
Signed-off-by: Lajos Molnar mol...@ti.com
Signed-off-by: David Sin david...@ti.com
---
drivers/misc/Kconfig |1 +
drivers/misc/Makefile |1 +
2 files changed, 2
This patch adds support for DMM-PAT initialization and programming.
Signed-off-by: David Sin david...@ti.com
Signed-off-by: Lajos Molnar mol...@ti.com
---
arch/arm/mach-omap2/include/mach/dmm.h | 92
drivers/misc/tiler/dmm-main.c | 187
From: Lajos Molnar mol...@ti.com
This patch defines the TILER Memory Manager (TMM) interface and
provides implementation for a PAT-supporting TMM.
Signed-off-by: Lajos Molnar mol...@ti.com
Signed-off-by: David Sin david...@ti.com
---
drivers/misc/tiler/tmm-pat.c | 266
Hi Omar,
On Mon, 2010-12-06 at 02:59 -0600, Ramirez Luna, Omar wrote:
Hi Ionut,
On Sun, Nov 21, 2010 at 4:46 AM, Ionut Nicu ionut.n...@gmail.com wrote:
This set of patches replaces some of the redundant components of
the tidspbridge driver, such as:
* wrapper functions for
Hi,
* David Sin david...@ti.com [101206 14:09]:
From: Lajos Molnar mol...@ti.com
This patch contains the TILER driver and implementation of the TILER
block manipulation and mapping functions.
It also contains the makefile and config file for the TILER driver.
...
+config
* Chris Ball c...@laptop.org [101127 18:29]:
Hi,
On Sat, Nov 27, 2010 at 01:59:24AM +0200, Ohad Ben-Cohen wrote:
This patch complements ed919b0 mmc: sdio: fix runtime PM anomalies by
introducing MMC_CAP_POWER_OFF_CARD by declaring MMC_CAP_POWER_OFF_CARD
on the ZOOM's wl1271 mmc slot.
* Vasiliy Kulikov seg...@openwall.com [101126 08:56]:
clk_get() returns ERR_PTR() on error, not NULL.
Signed-off-by: Vasiliy Kulikov seg...@openwall.com
---
Cannot compile this driver, so it is not tested at all.
Thanks will merge this.
Tony
arch/arm/plat-omap/counter_32k.c |2 +-
Resolve the following section mismatch warnings in the OMAP core code
when building omap2plus_defconfig:
WARNING: vmlinux.o(.text+0x2617c): Section mismatch in reference from the
function zoom_twl_gpio_setup() to the (unknown reference) .init.data:(unknown)
WARNING: vmlinux.o(.text+0x26378):
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()
Signed-off-by: Paul Walmsley p...@pwsan.com
Cc: Samuel Ortiz sa...@linux.intel.com
Paul,
I did the similar patch several days ago.
https://patchwork.kernel.org/patch/367011/
On Tue, Dec 7, 2010 at 8:32 AM, Paul Walmsley p...@pwsan.com wrote:
Resolve the following section mismatch warnings in the OMAP core code
when building omap2plus_defconfig:
WARNING:
On Tue, 7 Dec 2010, Bryan Wu wrote:
Paul,
I did the similar patch several days ago.
https://patchwork.kernel.org/patch/367011/
Great, thanks Bryan, in that case yours should be used instead.
- Paul
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a
On Tue, 7 Dec 2010, Bryan Wu wrote:
On Tue, Dec 7, 2010 at 8:35 AM, Paul Walmsley p...@pwsan.com 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
From: Santosh Shilimkar santosh.shilim...@ti.com
Like OMAP3, OMAP4430 ES2 has additional bitfields in PWRSTST register
which help identify the previous power state entered by the
powerdomain. Add pwrdm_clear_all_prev_pwrst to the OMAP4 powerdomains
implementation to support this.
Signed-off-by:
From: Rajendra Nayak rna...@t.com
powerdomains.h header today has only static definitions. Adding any
function declarations into it and including it in multiple source file
is expected to cause issues. Hence move all the static definitions
from powerdomains.h file into powerdomains_data.c file.
Get rid of the open-coded scratchpad write in mach-omap2/prcm.c and
replace it with an actual API, omap3_ctrl_write_boot_mode(). While
there, get rid of the gratuitous omap_writel().
There's not much documentation available for what should wind up in
the scratchpad here, so more documentation
From: Rajendra Nayak rna...@ti.com
Put infrastructure in place, so arch specific func pointers
can be hooked up to the platform-independent part of the
framework.
This is in preparation of splitting the powerdomain framework into
platform-independent part (for all omaps) and platform-specific
Static data should be declared in .c files, not .h files. It should be
possible to #include .h files at any point without creating multiple
copies of the same data.
We converted the clock data to .c files some time ago. This patch does
the same for the powerdomain data.
Signed-off-by: Paul
From: Rajendra Nayak rna...@ti.com
Define the following architecture specific funtions for omap2/3/4
.pwrdm_set_next_pwrst
.pwrdm_read_next_pwrst
.pwrdm_read_pwrst
.pwrdm_read_prev_pwrst
Convert the platform-independent framework to call these functions.
Signed-off-by: Rajendra Nayak
From: Rajendra Nayak rna...@ti.com
Define the following architecture specific funtions for omap2/3/4
.pwrdm_set_logic_retst
.pwrdm_read_logic_pwrst
.pwrdm_read_prev_logic_pwrst
.pwrdm_read_logic_retst
Convert the platform-independent framework to call these functions.
Signed-off-by: Rajendra
For some reason, the PRCM context save/restore code also saves and
restores a single System Control Module register,
CONTROL_PADCONF_SYS_NIRQ. This is probably just an error -- the
register should be handled by SCM code -- so this patch moves it
there.
If this register really does need to be
This patch series, intended for 2.6.38:
- includes Rajendra's powerdomain changes to add OMAP4 support;
- allocates static powerdomain and clockdomain data in C files
rather than header files (long overdue);
- begins the process of cleaning up mach-omap2/prcm.c;
- splits the OMAP4 PRCM
The OMAP3 PRM module is in the WKUP powerdomain, which is always
powered when the chip is powered, so it shouldn't be necessary to save
and restore those PRM registers. Remove the PRM register save/restore
code, which should save several microseconds during off-mode
entry/exit, since PRM register
Static data should be declared in .c files, not .h files. It should be
possible to #include .h files at any point without creating multiple
copies of the same data.
We converted the clock data to .c files some time ago. This patch does
the same for the clockdomain data.
Signed-off-by: Paul
On Tue, Dec 7, 2010 at 8:35 AM, Paul Walmsley p...@pwsan.com 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()
On Tue, Dec 7, 2010 at 9:38 AM, Paul Walmsley p...@pwsan.com wrote:
On Tue, 7 Dec 2010, Bryan Wu wrote:
Paul,
I did the similar patch several days ago.
https://patchwork.kernel.org/patch/367011/
Great, thanks Bryan, in that case yours should be used instead.
Thanks, Paul. I guess you
Add myself and Benoît as co-maintainers of the OMAP hwmod core code.
(The OMAP hwmod code manages the integration of IP blocks on the OMAP SoC
family.)
Add Benoît as the maintainer of OMAP4-based SoC hwmod mode.
Signed-off-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Benoît Cousson
1 - 100 of 124 matches
Mail list logo
