10 Jul, 2011
7 commits
-
The current code base is not linking with the OMAP_PM_NONE
option set.
Since the option OMAP_PM_NOOP provides a no-op/debug layer,
OMAP_PM_NONE can be removed.
OMAP_PM_NOOP is enabled by default by Kconfig.Signed-off-by: Jean Pihet
Signed-off-by: Paul Walmsley -
MPUSS was renamed MPU and L3_D2D D2D.
The rename will slightly change the order of the structure
and thus generate some structures moves.Add a comment and remove a comma.
Update Copyright for TI and Nokia and add back Paul
in the author list.Signed-off-by: Benoit Cousson
Cc: Paul Walmsley
Cc: Rajendra Nayak
Signed-off-by: Paul Walmsley -
Some maros were not well aligned. Re-align them.
Signed-off-by: Benoit Cousson
Cc: Paul Walmsley
Cc: Rajendra Nayak
Signed-off-by: Paul Walmsley -
The restore part of the CM is an alias of some regular registers
used only during the SAR restore to facilate the dma to write
a contiguous set of registers.
The registers should never be used by the SW, only the original
register have to be used.Remove them from cmX_44xx.h files to avoid anybody to use them by
mistake.Signed-off-by: Benoit Cousson
Cc: Paul Walmsley
Cc: Rajendra Nayak
Cc: Santosh Shilimkar
Signed-off-by: Paul Walmsley -
Indent flags to be aligned with other fields.
Signed-off-by: Benoit Cousson
Cc: Paul Walmsley
Cc: Rajendra Nayak
Cc: Santosh Shilimkar
[paul@pwsan.com: split this patch from an earlier patch by Benoît;
edited commit message]
Signed-off-by: Paul Walmsley -
The following commit introduced new macros to define an offset
per clock domain in an instance.commit e4156ee52fe617c2c2d80b5db993ff4bf07d7c3c
OMAP4: CM instances: add clockdomain register offsets
The PRM contains only two clock controls management entities:
EMU and WKUP.
Remove the other ones.Signed-off-by: Benoit Cousson
Cc: Paul Walmsley
Signed-off-by: Paul Walmsley -
A couple of macros were wrongly changed during the _MOD to _INST
rename done in the following commit:OMAP4: PRCM: rename _MOD macros to _INST
cdb54c4457d68994da7c2e16907adfbfc130060dFix them to their original name.
Some CM and PRM instances were not well aligned. Align them.
Remove one blank line in cm2_44xx.h to align the output with
the other (cm1_44xx.h, prm44xx.h) files.Update header copyright date.
Signed-off-by: Benoit Cousson
Cc: Paul Walmsley
Cc: Rajendra Nayak
Signed-off-by: Paul Walmsley
08 Jul, 2011
4 commits
-
…l/git/tmlind/linux-omap-2.6 into omap/cleanup
-
…io/linux-audio into cleanup-part-2
-
These McBSP port number enums are used only in two places in the McBSP code
so we may remove then and just use numeric values like rest of the code does.Signed-off-by: Jarkko Nikula
Signed-off-by: Tony Lindgren -
These variables got unused after ("omap: mcbsp: Drop in-driver transfer
support") but was noticed only afterwards.Signed-off-by: Jarkko Nikula
Signed-off-by: Tony Lindgren
04 Jul, 2011
4 commits
-
Some regulator config can be moved out from board files,
since they are close to identical.Signed-off-by: Peter Ujfalusi
Acked-by: Tony Lindgren -
Reduce the amount of duplicated code by moving the common
configuration for twl4030/5030/tpsxx to the twl-common file.
Use the omap3_pmic_get_config function from board files to
properly configure the PMIC with the common fields.Signed-off-by: Peter Ujfalusi
Acked-by: Tony Lindgren -
Reduce the amount of duplicated code by moving the common
configuration for TWL6030 (on OMAP4 platform) to the
twl-common file.
Use the omap4_pmic_get_config function from board files to
properly configure the PMIC with the common fields.Signed-off-by: Peter Ujfalusi
Acked-by: Tony Lindgren -
Introduce a new file, which will be used to configure
common pmic (TWL) devices, regulators, and TWL audio.Signed-off-by: Peter Ujfalusi
Acked-by: Tony Lindgren
30 Jun, 2011
1 commit
-
board-generic.c now contains a reference to omap3_timer, but depends
only on ARCH_OMAP2, not on ARCH_OMAP3, which controls that symbol.
omap2_timer seems to be more appropriate anyway, so use that instead.Signed-off-by: Arnd Bergmann
Acked-by: Tony Lindgren
29 Jun, 2011
6 commits
-
…khilman/linux-omap-pm into devel-cleanup
Conflicts:
arch/arm/mach-omap2/pm-debug.c
arch/arm/mach-omap2/pm.h -
We haven't seen either use for in-driver transfer API in McBSP driver
over the years so it looks they can be removed too.Signed-off-by: Jarkko Nikula
Signed-off-by: Tony Lindgren -
We haven't seen any use for the SPI API in McBSP driver over the years. More
over, Peter Ujfalusi noticed that SPI mode is not
even supported since OMAP2430 so it's very unlikely that we'll see any use
for it in the future either.Signed-off-by: Jarkko Nikula
Acked-by: Peter Ujfalusi
Signed-off-by: Tony Lindgren -
Fix compilation error introduced with 786b01a8c1db0c0decca55d660a2a3ebd7cfb26b
(cleanup regulator supply definitions in mach-omap2).Signed-off-by: Peter Ujfalusi
[tony@atomide.com: updated comments]
Signed-off-by: Tony Lindgren -
omap_nand_platform_data fields 'options', 'gpio_irq', 'nand_setup' and
'dma_channel' are never referenced by the NAND driver, yet various
board files are initializing those fields. This is both incorrect and
confusing, so remove them. This allows to get rid of a global
variable in gpmc-nand.c.This also corrects an issue where some boards are trying to pass NAND
16bit flag through .options, but the driver is using .devsize instead
and ignoring .options.Finally, .dev_ready is treated as a flag by the driver, so make it bool
instead of a function pointer.Signed-off-by: Grazvydas Ignotas
Signed-off-by: Tony Lindgren
28 Jun, 2011
6 commits
-
We can keep everything sys_timer and gptimer.c related code in
timer.c as the code will be very minimal.Later on we can also remove timer-mpu.c, as it can be called from
omap4_timer_init function.This allows us to get rid of confusing existing files. We currently
have timer-gp.c, timer-mpu.c, and patches have been posted to add
dmtimer.c. There's no need to have these multiple files, we can
put everything into timer.c.Signed-off-by: Tony Lindgren
-
This is no longer needed as we now just set the desired
.timer in MACHINE_START. We can now also remove timer-gp.h.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
Use dmtimer macros for clocksource. As with the clockevent,
this allows us to initialize the rest of dmtimer code later on.Note that eventually we will be initializing the timesource
from init_early so sched_clock will work properly for
CONFIG_PRINTK_TIME.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
There's no need to initialize the dmtimer framework early.
Just mark the clocksource and timesource as reserved, and
initialize dmtimer with an arch_initcall.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
Fix the section mismatch warning:
WARNING: vmlinux.o(.text+0x21118): Section mismatch
in reference from the function pm_dbg_init() to the
function .init.text:pwrdms_setup()
The function pm_dbg_init() references
the function __init pwrdms_setup().
This is often because pm_dbg_init lacks a __init
annotation or the annotation of pwrdms_setup is wrong.Signed-off-by: Sanjeev Premi
Signed-off-by: Kevin Hilman -
Remove OMAP3-specific register dumping feature from PM debug layer.
This is removed because:- it's ugly
- it's OMAP3-specific, and will obviously not scale to OMAP4+
- userspace /dev/mem-based tools (like omapconf) can do this much betterTested-by: Santosh Shilimkar
Acked-by: Santosh Shilimkar
Acked-by: Jean Pihet
Signed-off-by: Kevin Hilman
21 Jun, 2011
6 commits
-
Tested-by: Santosh Shilimkar
Acked-by: Santosh Shilimkar
Signed-off-by: Kevin Hilman -
Remove the OMAP-specific PM debug 'sleep_while_idle' feature which is
currently available as an OMAP-specific debugfs entry.This duplicates existing ARM-generic functionality available as a
boot-time option using the boot cmdline option 'hohlt'.If runtime configuration of this is needed, then adding a debugfs
entry for the ARM-generic hlt/nohlt interface should be added.Tested-by: Santosh Shilimkar
Acked-by: Santosh Shilimkar
Acked-by: Jean Pihet
Signed-off-by: Kevin Hilman -
Error label case seems to have a 2 tab indentation when just 1 is
necessary.Signed-off-by: Nishanth Menon
Signed-off-by: Kevin Hilman -
Since we already know the state of the autocomp enablement, we can
see if the requested state is different from the current state and
enable/disable SR only on the need basis.Signed-off-by: Nishanth Menon
Signed-off-by: Kevin Hilman -
We will enable and disable interrupt on a need basis in the class
driver. We need to keep the IRQ disabled by default else the
forceupdate or vcbypass events could trigger events that we don't
need/expect to handle.This is a preparation for SmartReflex AVS class drivers such as
class 2 and class 1.5 which would need to use interrupts. Existing
SmartReflex AVS class 3 driver does not require to use interrupts
and is not impacted by this change.Signed-off-by: Nishanth Menon
Signed-off-by: Kevin Hilman -
Interrupt notification mechanism of SmartReflex can be used by the
choice of implementation of the class driver. For example, Class 2 and
Class 1.5 of SmartReflex can both use the interrupt notification to
identify the transition of voltage or other events.Hence, the actual class does not matter for notifier. Let the class
driver's handling decide how it should be used. SmartReflex driver
should provide just the primitives.Signed-off-by: Nishanth Menon
Signed-off-by: Kevin Hilman
20 Jun, 2011
5 commits
-
This removes the support for setting the wake-up timer for debugging.
Later on we can reserve gptimer1 for PM code only and have similar
functionality.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
This patch makes timer-gp.c to use only a subset of dmtimer
functions without the need to initialize dmtimer code early.Also note that now with the inline functions, timer_set_next_event
becomes more efficient in the lines of assembly code.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
This will allow us to share the code between system timer and
dmtimer device driver code without having to initialize all the
dmtimers early. This change will also make the timer_set_next_event
more efficient as the inline functions will optimize the code
better for the timer reprogramming.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
These will be needed when dmtimer platform init code gets split
for omap1 and omap2+. These will also be needed for separate
sys_timer init and driver init for the rest of the hardware timers
in the following patches. No functional changes.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman -
This is needed for the following patches so we can initialize the
rest of the hardware timers later on.As with the init_irq calls, there's no need to do cpu_is_omap calls
during the timer init as we only care about the major omap generation.
This means that we can initialize the sys_timer with the .timer
entries alone.Note that for now we just set stubs for the various sys_timer entries
that will get populated in a later patch. The following patches will
also remove the omap_dm_timer_init calls and change the init for the
rest of the hardware timers to happen with an arch_initcall.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman
16 Jun, 2011
1 commit
-
This allows us to remove cpu_is_omap calls from init_irq functions.
There should not be any need for cpu_is_omap calls as at this point.
During the timer init we only care about SoC generation, and not about
subrevisions.The main reason for the patch is that we want to initialize only
minimal omap specific code from the init_early call.Signed-off-by: Tony Lindgren
Reviewed-by: Kevin Hilman