Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Nov 20, 2012
  1. Merge branch 'omap-3.0p' into jb-dev-41

    authored
    Conflicts:
    	arch/arm/mach-omap2/board-44xx-tablet-panel.c
    	arch/arm/mach-omap2/emif.c
    	drivers/net/usb/asix.c
    	drivers/usb/otg/twl6030-usb.c
    	drivers/video/omap2/displays/Kconfig
    	drivers/video/omap2/displays/Makefile
    	drivers/video/omap2/dss/hdmi_panel.c
    	drivers/video/omap2/omaplfb/omaplfb_bv.c
    	include/linux/i2c/twl.h
  2. ARM: OMAP2+: clockdomain/hwmod: add workaround for EMU clockdomain id…

    Paul Walmsley authored committed
    …le problems
    
    The idle status of the IP blocks and clocks inside the EMU clockdomain
    isn't taken into account by the PRCM hardware when deciding whether
    the clockdomain is idle.  Add a workaround flag in the clockdomain
    code, CLKDM_MISSING_IDLE_REPORTING, to deal with this problem, and add
    the code necessary to support it.
    
    If CLKDM_MISSING_IDLE_REPORTING is set on a clockdomain, the
    clockdomain will be forced active whenever an IP block inside that
    clockdomain is in use, even if the clockdomain supports
    hardware-supervised idle.  When the kernel indicates that the last
    active IP block inside the clockdomain is no longer used, the
    clockdomain will be forced idle, or, if that mode is not supported in
    the hardware, it will be placed into hardware-supervised idle.
    
    This patch is an equal collaboration with Jon Hunter
    <jon-hunter@ti.com>.  Ming Lei <ming.lei@canonical.com>, Will Deacon
    <will.deacon@arm.com>, Madhav Vij <mvij@ti.com>, Kevin Hilman
    <khilman@ti.com>, Benoît Cousson <b-cousson@ti.com>, and Santosh
    Shilimkar <santosh.shilimkar@ti.com> all made essential contributions
    to the understanding of EMU clockdomain power management on OMAP.
    
    [steven@steven676.net: squash in cf956d9 ("ARM: OMAP3: fix workaround
    for EMU clockdomain")]
    
    Signed-off-by: Paul Walmsley <paul@pwsan.com>
    Cc: Jon Hunter <jon-hunter@ti.com>
    Cc: Ming Lei <ming.lei@canonical.com>
    Cc: Will Deacon <will.deacon@arm.com>
    Cc: Madhav Vij <mvij@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Benoît Cousson <b-cousson@ti.com>
    Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
    Tested-by: Jon Hunter <jon-hunter@ti.com>
    [steven@steven676.net: backport to p-android-omap3-3.0]
  3. update kernel defconfig:

    authored
    disable:
    CONFIG_PM_DEBUG
    
    enable:
    CONFIG_TWL6030_MADC
  4. Revert "Update lowmemorykiller to 3.4 version."

    authored
    This reverts commit d631698.
  5. Revert "Update android binder to 3.3 version."

    authored
    This reverts commit 9e9b2f2.
  6. ARM: OMAP2+: clockdomain/hwmod: add workaround for EMU clockdomain id…

    Paul Walmsley authored committed
    …le problems
    
    The idle status of the IP blocks and clocks inside the EMU clockdomain
    isn't taken into account by the PRCM hardware when deciding whether
    the clockdomain is idle.  Add a workaround flag in the clockdomain
    code, CLKDM_MISSING_IDLE_REPORTING, to deal with this problem, and add
    the code necessary to support it.
    
    If CLKDM_MISSING_IDLE_REPORTING is set on a clockdomain, the
    clockdomain will be forced active whenever an IP block inside that
    clockdomain is in use, even if the clockdomain supports
    hardware-supervised idle.  When the kernel indicates that the last
    active IP block inside the clockdomain is no longer used, the
    clockdomain will be forced idle, or, if that mode is not supported in
    the hardware, it will be placed into hardware-supervised idle.
    
    This patch is an equal collaboration with Jon Hunter
    <jon-hunter@ti.com>.  Ming Lei <ming.lei@canonical.com>, Will Deacon
    <will.deacon@arm.com>, Madhav Vij <mvij@ti.com>, Kevin Hilman
    <khilman@ti.com>, Benoît Cousson <b-cousson@ti.com>, and Santosh
    Shilimkar <santosh.shilimkar@ti.com> all made essential contributions
    to the understanding of EMU clockdomain power management on OMAP.
    
    [steven@steven676.net: squash in cf956d9 ("ARM: OMAP3: fix workaround
    for EMU clockdomain")]
    
    Signed-off-by: Paul Walmsley <paul@pwsan.com>
    Cc: Jon Hunter <jon-hunter@ti.com>
    Cc: Ming Lei <ming.lei@canonical.com>
    Cc: Will Deacon <will.deacon@arm.com>
    Cc: Madhav Vij <mvij@ti.com>
    Cc: Kevin Hilman <khilman@ti.com>
    Cc: Benoît Cousson <b-cousson@ti.com>
    Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
    Tested-by: Jon Hunter <jon-hunter@ti.com>
    [steven@steven676.net: backport to p-android-omap3-3.0]
  7. @intersectRaven

    Update lowmemorykiller to 3.4 version.

    intersectRaven authored committed
  8. @intersectRaven

    Update android binder to 3.3 version.

    intersectRaven authored committed
  9. @thalamus

    omap44xx: cpuidle: Update target residencies to saner values

    thalamus authored committed
    The current values are insane.
    
    There is no possible way power saving
    can be attained by heading into C4 for not much more than 1ms. The average
    values are in the 20ms range, so why do we need to even entertain entering
    at much lower values when we will use more power than we save in doing so.
    
    The actual recommended values are shown in 79e796f
    but for some obscure reason, in 16385c7 and
    22e2193 they were updated to match the exit_latency.
    
    This seems horribly wrong to me as there comes a point when the target residency is
    so low that you use more power actually entering the state than you gain from the
    insignificant amount of time you spend there.
    
    With the values in this commit, C4 state is used for >95% of the time when the screen
    is off, with C3 picking up the remainder.
    During audio playback, C4 is used ~50% of the time, C3 is used ~25% of the time and C2
    picks up whatever is left.
  10. @thalamus
  11. @thalamus
  12. update defconfig : fix lag on come devices

    authored
    disable :
    CONFIG_OMAP_SMARTREFLEX_CLASS1P5
    CONFIG_TWL6030_MADC
    
    enable:
    CONFIG_MMC_OMAP
    CONFIG_PM_DEBUG
    CONFIG_PM_ADVANCED_DEBUG
    CONFIG_PM_TEST_SUSPEND
    CONFIG_CAN_PM_TRACE
  13. update river_defconfig:

    authored
    enable:
    SND_OMAP_SOC_ABE_DL2
    OMAP4_DPLL_CASCADING
    TWL6030_MADC
    
    disable:
    REMOTEPROC_CORE_DUMP
    
    remove:
    SND_SOC_TWL6040
  14. add kernel defconfig

    authored
  15. update drivers/usb/ drivers

    authored
  16. update sound/soc/ :

    authored
    It's based on kindle fire 2 stock kernel sound driver.
    Merged all sound  patch from 3.0.8 to 3.0.31+ .
    Add speaker mute when plugin headset patch .
    
    It's use 44.1K rate default. So it need new audio HAL driver using 44.1K rate.
  17. update drivers/video/omap2/

    authored
  18. update arch/arm/boot/compressed/Makefile arch/arm/mm/Makefile securit…

    authored
    …y/smc/Makefile for gcc 4.6
  19. add kernel defconfig

    authored
  20. @grygoriyS

    OMAP4430/60: EMIF: errata: Prohibit usage of Power-Down mode

    grygoriyS authored Gerrit Code Review committed
    A ZQ calibration long command is issued every time on exit
    from active power-down and precharge power-down modes
    when EMIF is configured to use Power-down mode
    (EMIF_PWR_MGMT_CTRL.REG_LP_MODE=0x4).
    
    Due to very short periods of power-down cycles, ZQ calibration
    overhead creates bandwidth issues and increases overall system
    power consumption.
    
    As result, the guideline is to not allow Power-down mode and,
    therefore, to not have set the
    EMIF_PWR_MGMT_CTRL[10:8] REG_LP_MODE bit field to 0x4.
    
    TI Errata i743; IMPACTED: OMAP4430/60 all revisions
    
    Change-Id: Ib82f28e6e0c6c046ea277b90a78dc82c1ee82417
    Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
    Signed-off-by: Vitaly Chernooky <vitaly.chernooky@ti.com>
  21. @grygoriyS

    OMAP4430/60: EMIF: errata: Prohibit usage of Power-Down mode

    grygoriyS authored Gerrit Code Review committed
    A ZQ calibration long command is issued every time on exit
    from active power-down and precharge power-down modes
    when EMIF is configured to use Power-down mode
    (EMIF_PWR_MGMT_CTRL.REG_LP_MODE=0x4).
    
    Due to very short periods of power-down cycles, ZQ calibration
    overhead creates bandwidth issues and increases overall system
    power consumption.
    
    As result, the guideline is to not allow Power-down mode and,
    therefore, to not have set the
    EMIF_PWR_MGMT_CTRL[10:8] REG_LP_MODE bit field to 0x4.
    
    TI Errata i743; IMPACTED: OMAP4430/60 all revisions
    
    Change-Id: Ib82f28e6e0c6c046ea277b90a78dc82c1ee82417
    Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
    Signed-off-by: Vitaly Chernooky <vitaly.chernooky@ti.com>
Commits on Nov 19, 2012
  1. @daeskp

    Android alarm: IOCTL command encoding fix

    daeskp authored Andrii Beregovenko committed
    commit 6bd4a5d upstream.
    
    Fixed a bug. Data was being written to user space using an IOCTL
    command encoded with _IOC_WRITE access mode.
    
    Backported: 3.4 -> 3.0
    
    Change-Id: I228662c2da6ff3df087d2c97486f3ef1fd9a2280
    Signed-off-by: Dae S. Kim <dae@velatum.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Andrii Beregovenko <a.beregovenko@ti.com>
  2. @daeskp

    Android alarm: IOCTL command encoding fix

    daeskp authored Andrii Beregovenko committed
    commit 6bd4a5d upstream.
    
    Fixed a bug. Data was being written to user space using an IOCTL
    command encoded with _IOC_WRITE access mode.
    
    Backported: 3.4 -> 3.0
    
    Change-Id: I228662c2da6ff3df087d2c97486f3ef1fd9a2280
    Signed-off-by: Dae S. Kim <dae@velatum.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Andrii Beregovenko <a.beregovenko@ti.com>
Something went wrong with that request. Please try again.