On Fri, Apr 15, 2011 at 9:06 PM, Russell King - ARM Linux
wrote:
> This is work in progress.
>
> We have two SoCs using SRAM, both with their own allocation systems,
> and both with their own ways of copying functions into the SRAM.
>
> Let's unify this before we have additional SoCs re-implementi
On Sat, Apr 16, 2011 at 09:01:26PM +0800, Haojian Zhuang wrote:
> On Fri, Apr 15, 2011 at 9:06 PM, Russell King - ARM Linux
> wrote:
> > This is work in progress.
> >
> > We have two SoCs using SRAM, both with their own allocation systems,
> > and both with their own ways of copying functions into
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: devel-timer
Test Info:
* OMAP4430SDP: Functional tests
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.
Signed-off-by: Tarun Kanti DebBarma
Acked-by: Cousson, Benoit
---
arch/arm/mach-omap2/clock2420_data.c | 52 ++
OMAP4 has two groups of timers: version 1 timers are 1, 2, 10,
while the rest of the timers, 3-9, 11 are version 2 timers.
The version information is required by the driver so that they
could be handled correctly by it.
Signed-off-by: Tarun Kanti DebBarma
Acked-by: Cousson, Benoit
Cc: Cousson, B
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
Signed-off-by: Thara Gopinath
Acked-by: Cousson, Benoit
---
arch/arm/plat-omap/dmtimer.c | 159
From: Thara Gopinath
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
Signed-off-by: Tarun Kanti DebBarma
Acked-by: Cousson, Benoit
---
arch/arm/mach-omap1/Makefile
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.
In addition, capability attribute of each of the timers is added in
hwmod database.
Signed-off-by: Tar
Add pm_runtime feature to dmtimer whereby _get_sync() is called within
omap_dm_timer_enable(), _put_sync() is called in omap_dm_timer_disable().
Signed-off-by: Tarun Kanti DebBarma
[p-bas...@ti.com: added pm_runtime logic in probe()]
Signed-off-by: Partha Basak
Reviewed-by: Varadarajan, Charulat
Register timer devices by going through hwmod database using
hwmod API. The driver probes each of the registered devices.
Functionality which are already performed by hwmod framework
are removed from timer code. New set of timers present on
OMAP4 are now supported.
Signed-off-by: Tarun Kanti DebBa
In driver probe use sys_timer_reserved to identify which all timers
have already been used for clocksource and clockevent. Mark all those
timers as reserved so that no one else can use them.
Signed-off-by: Tarun Kanti DebBarma
---
arch/arm/plat-omap/dmtimer.c |8 +++-
1 files changed, 7
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
Rev
Since the spinlock is not used in any interrupt context we can
replace it with mutex instead.
Signed-off-by: Tarun Kanti DebBarma
---
arch/arm/plat-omap/dmtimer.c | 27 +++
1 files changed, 11 insertions(+), 16 deletions(-)
diff --git a/arch/arm/plat-omap/dmtimer.c b/a
Make plat-omap/dmtimer.c a normal driver. It is moved to drivers/misc
as timer-omap.c and the corresponding header file has been moved to
include/linux as timer-omap.h. Files which included plat/dmtimer.h
are changed to include linux/timer-omap.h now.
Signed-off-by: Tarun Kanti DebBarma
---
arch
On Mon, 2011-04-11 at 18:41 +0530, Avinash.H.M. wrote:
> > > > + oh->_sysc_cache = v;
> > > > + omap_hwmod_write(v, oh, oh->class->sysc->sysc_offs);
> > >
> > > Direct SYSCONFIG access isn't right here. This should go through
> > > omap_hwmod.
> > >
> > > What is probably needed is exposi
There are several OMAP boards that use SMSC911x Ethernet controller. Convert
them all to use gpmc-smsc911x for device registration.
Mike Rapoport (2):
OMAP: gpmc-smsc911x: always set irq flags to IORESOURCE_IRQ_LOWLEVEL
OMAP: convert boards that use SMSC911x to use gpmc-smsc911x
arch/arm/ma
SMSC911x devices attached to OMAP GPMC always use low level irqs.
Setting the appropriate flag in the irq resourse strucure allows using
.flags field in the omap_smsc911x_platform_data for driver specific
flags
Signed-off-by: Mike Rapoport
---
arch/arm/mach-omap2/board-omap3logic.c |1 -
arc
Signed-off-by: Mike Rapoport
---
arch/arm/mach-omap2/board-cm-t35.c | 84 +++--
arch/arm/mach-omap2/board-igep0020.c| 53 ++---
arch/arm/mach-omap2/board-ldp.c | 65 ++--
arch/arm/mach-omap2/board-omap3evm.c| 71 +++-
On 4/16/2011 9:21 PM, Tarun Kanti DebBarma wrote:
In driver probe use sys_timer_reserved to identify which all timers
have already been used for clocksource and clockevent. Mark all those
timers as reserved so that no one else can use them.
Signed-off-by: Tarun Kanti DebBarma
---
arch/arm/plat
19 matches
Mail list logo
