05 Jul, 2011

2 commits

  • Add twl4030_vibra platform data, and the needed regulators
    for twl6040 vibrator.

    Signed-off-by: Peter Ujfalusi
    Acked-by: Tony Lindgren

    Peter Ujfalusi
     
  • TWL6040 IC provides analog high-end audio codec functions for
    handset applications. It contains several audio analog inputs
    and outputs as well as vibrator support. It's connected to the
    host processor via PDM interface for audio data communication.
    The audio modules are controlled by internal registers that
    can be accessed by I2C and PDM interface.

    TWL6040 MFD will be registered as a child of TWL-CORE, and will
    have two children of its own: twl6040-codec and twl6040-vibra.

    This driver is based on TWL4030 and WM8350 MFD drivers.

    Signed-off-by: Misael Lopez Cruz
    Signed-off-by: Peter Ujfalusi
    Acked-by: Samuel Ortiz

    Misael Lopez Cruz
     

04 Jul, 2011

5 commits


29 Jun, 2011

6 commits


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

    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

    Tony Lindgren
     
  • 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

    Tony Lindgren
     
  • 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

    Tony Lindgren
     
  • 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

    Sanjeev Premi
     
  • 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 better

    Tested-by: Santosh Shilimkar
    Acked-by: Santosh Shilimkar
    Acked-by: Jean Pihet
    Signed-off-by: Kevin Hilman

    Kevin Hilman
     

21 Jun, 2011

6 commits

  • Tested-by: Santosh Shilimkar
    Acked-by: Santosh Shilimkar
    Signed-off-by: Kevin Hilman

    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

    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

    Nishanth Menon
     
  • 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

    Nishanth Menon
     
  • 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

    Nishanth Menon
     
  • 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

    Nishanth Menon
     

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

    Tony Lindgren
     
  • 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

    Tony Lindgren
     
  • 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

    Tony Lindgren
     
  • 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

    Tony Lindgren
     
  • 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

    Tony Lindgren
     

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

    Tony Lindgren
     

14 Jun, 2011

7 commits


13 Jun, 2011

2 commits