1. 25 Sep, 2014 4 commits
  2. 13 Sep, 2014 2 commits
  3. 11 Sep, 2014 2 commits
  4. 10 Sep, 2014 1 commit
    • Roland Stigge's avatar
      ARM: LPC32xx: Fix reset function · 01100c02
      Roland Stigge authored
      In the recent change to the reset function API (commit
      7b6d864b
      
      ), the mode argument changed from a
      char to an enum. lpc23xx_restart() only handles REBOOT_SOFT and REBOOT_HARD,
      but the new kernel code emits REBOOT_COLD (0) on reboots now which leads to
      lpc32xx simply not rebooting (but halting).
      
      This patch fixes this by just resetting unconditionally as on other platforms
      (e.g. mach-bcm2835).
      
      Pulling lpc32xx_watchdog_reset() into lpc23xx_restart() since the while() in
      lpc23xx_restart() is part of the procedure anyway and lpc32xx_watchdog_reset()
      isn't used anywhere else anymore.
      Signed-off-by: default avatarRoland Stigge <stigge@antcom.de>
      01100c02
  5. 09 Sep, 2014 2 commits
  6. 08 Sep, 2014 7 commits
  7. 05 Sep, 2014 1 commit
  8. 04 Sep, 2014 1 commit
    • Xia Kaixu's avatar
      ARM: cns3xxx: fix allmodconfig panic in pci driver · 0a2e912d
      Xia Kaixu authored
      
      
      The kernel panic occurs when running an allmodconfig kernel on
      OMAP4460. The inicall "cns3xxx_pcie_init" does not check which
      hardware it's running on and just tries to access to its specific
      registers. Now call it from .init_late callback from the two
      machine descriptors.
      Signed-off-by: default avatarXia Kaixu <kaixu.xia@linaro.org>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Anton Vorontsov <anton@enomsg.org>
      Cc: Felix Fietkau <nbd@openwrt.org>
      Cc: Imre Kaloz <kaloz@openwrt.org>
      Cc: linaro-kernel@lists.linaro.org
      Cc: linux-arm-kernel@lists.infradead.org
      0a2e912d
  9. 03 Sep, 2014 2 commits
  10. 31 Aug, 2014 1 commit
  11. 29 Aug, 2014 1 commit
  12. 28 Aug, 2014 1 commit
    • Tony Lindgren's avatar
      mfd: twl4030-power: Fix PM idle pin configuration to not conflict with regulators · daebabd5
      Tony Lindgren authored
      Commit 43fef47f (mfd: twl4030-power: Add a configuration to turn
      off oscillator during off-idle) added support for configuring the PMIC
      to cut off resources during deeper idle states to save power.
      
      This however caused regression for n900 display power that needed the
      PMIC configuration to be disabled with commit d937678a (ARM: dts:
      Revert enabling of twl configuration for n900).
      
      Turns out the root cause of the problem is that we must use
      TWL4030_RESCONFIG_UNDEF instead of DEV_GRP_NULL to avoid disabling
      regulators that may have been enabled before the init function
      for twl4030-power.c runs. With TWL4030_RESCONFIG_UNDEF we let the
      regulator framework control the regulators like it should. Here we
      need to only configure the sys_clken and sys_off_mode triggers for
      the regulators that cannot be done by the regulator framework as
      it's not running at that point.
      
      This allows us to enable the PMIC configuration for n900.
      
      Fixes: 43fef47f
      
       (mfd: twl4030-power: Add a configuration to turn off oscillator during off-idle)
      
      Cc: stable@vger.kernel.org # v3.16
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      Tested-by: default avatarAaro Koskinen <aaro.koskinen@iki.fi>
      Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
      daebabd5
  13. 27 Aug, 2014 6 commits
  14. 26 Aug, 2014 4 commits
  15. 25 Aug, 2014 5 commits
    • Brian Norris's avatar
      ARM: brcmstb: revert SMP support · fc3e825f
      Brian Norris authored
      There were several issues (of varying degree of importance) pointed out
      with this code late in the review cycle, yet the code was still merged.
      Let's rip it out for now and look at resubmitting at a later time.
      
      This reverts most of commit 4fbe66d9
      
      .
      Signed-off-by: default avatarBrian Norris <computersforpeace@gmail.com>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      fc3e825f
    • Tony Lindgren's avatar
      ARM: OMAP2+: hwmod: Rearm wake-up interrupts for DT when MUSB is idled · cc824534
      Tony Lindgren authored
      
      
      Looks like MUSB cable removal can cause wake-up interrupts to
      stop working for device tree based booting at least for UART3
      even as nothing is dynamically remuxed. This can be fixed by
      calling reconfigure_io_chain() for device tree based booting
      in hwmod code. Note that we already do that for legacy booting
      if the legacy mux is configured.
      
      My guess is that this is related to UART3 and MUSB ULPI
      hsusb0_data0 and hsusb0_data1 support for Carkit mode that
      somehow affect the configured IO chain for UART3 and require
      rearming the wake-up interrupts.
      
      In general, for device tree based booting, pinctrl-single
      calls the rearm hook that in turn calls reconfigure_io_chain
      so calling reconfigure_io_chain should not be needed from the
      hwmod code for other events.
      
      So let's limit the hwmod rearming of iochain only to
      HWMOD_FORCE_MSTANDBY where MUSB is currently the only user
      of it. If we see other devices needing similar changes we can
      add more checks for it.
      
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: stable@vger.kernel.org # v3.16
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      cc824534
    • Tony Lindgren's avatar
      ARM: dts: Enable UART wake-up events for beagleboard · c15adae8
      Tony Lindgren authored
      
      
      For device tree based booting, we need to use wake-up
      interrupts like we already do for some omaps. This fixes
      a PM regression on beagleboard compared to legacy booting.
      Tested-by: default avatarTero Kristo <t-kristo@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      c15adae8
    • Mark Brown's avatar
      ARM: dts: Remove twl6030 clk32g "regulator" · 509a81fd
      Mark Brown authored
      
      
      The kernel has never supported clk32g as a regulator since it is a clock
      and not a regulator. Fortunately nothing actually references this node so
      we can just remove it.
      Signed-off-by: default avatarMark Brown <broonie@linaro.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      509a81fd
    • Markus Pargmann's avatar
      ARM: OMAP2+: omap_device: remove warning that clk alias already exists · 9a02ae4e
      Markus Pargmann authored
      
      
      When an alias for a clock already exists the warning is printed. For
      every module with a main_clk defined, a clk alias for fck is added.
      There are some components that have the same main_clk defined, so this
      is a really normal situation.
      
      For example the am33xx edma device has 4 components using the same main
      clock. So there are three warnings in the boot log for this already
      existing clock alias:
      	platform 49000000.edma: alias fck already exists
      	platform 49000000.edma: alias fck already exists
      	platform 49000000.edma: alias fck already exists
      
      As this is only interesting for developers, this patch changes the
      message to a debug message.
      Signed-off-by: default avatarMarkus Pargmann <mpa@pengutronix.de>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      9a02ae4e