1. 21 Sep, 2012 1 commit
    • Olof Johansson's avatar
      Merge tag 'rpi-for-3.7' of... · 3aec092e
      Olof Johansson authored
      Merge tag 'rpi-for-3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-rpi into next/soc
      
      ARM: add basic BCM2835 SoC and Raspberry Pi board support
      
      The BCM2835 is an ARM SoC from Broadcom. This patch adds very basic
      support for this SoC; enough to boot the system into an initrd with
      UART console, interrupt controller, timers, and a stub clock driver.
      
      Also provided is a similarly basic device tree for the Raspberry Pi
      Model B board.
      
      This series was written by Simon Arlott, Chris Boot, and Dom Cobley
      downstream, with reference to a Broadcom tree, and modified for upstream
      and submitted by Stephen Warren.
      
      * tag 'rpi-for-3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-rpi:
        MAINTAINERS: add an entry for the BCM2835 ARM sub-architecture
        ARM: bcm2835: instantiate console UART
        ARM: bcm2835: add stub clock driver
        ARM: bcm2835: add system timer
        ARM: bcm2835: add interrupt controller driver
        ARM: add infra-structure for BCM2835 and Raspberry Pi
      3aec092e
  2. 20 Sep, 2012 7 commits
  3. 17 Sep, 2012 5 commits
  4. 13 Sep, 2012 24 commits
  5. 12 Sep, 2012 3 commits
    • Vaibhav Hiremath's avatar
      ARM: AM33XX: clock: Add dcan clock aliases for device-tree · 83c11542
      Vaibhav Hiremath authored
      Currently, the device names for the dcan module follows the
      format "dcan.X", where 'X' is the dcan instance number.
      On other side, driver may request for clock with/without con_id
      and dev_id, and it is expected that platform should respect this
      request and return the requested clock handle.
      
      Now, when using device tree, the format of the device name created
      by OF layer is different, "<reg-address>.<device-name>",
      assuming that the device-tree "reg" property is specified.
      This causes the look-up failure for clock node in dcan driver
      
      To fix this add new dcan clock alias for using device-tree.
      Signed-off-by: default avatarVaibhav Hiremath <hvaibhav@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Benoit Cousson <b-cousson@ti.com>
      Cc: Grant Likely <grant.likely@secretlab.ca>
      Cc: Rob Herring <robherring2@gmail.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      83c11542
    • Vaibhav Hiremath's avatar
      ARM: OMAP2+: dpll: Add missing soc_is_am33xx() check for common functions · 78da2640
      Vaibhav Hiremath authored
      Add missing soc_is_am33xx() check for DPLL common control & clock
      related functions, without this dpll programmability would be broken
      for am33xx family of devices.
      Signed-off-by: default avatarVaibhav Hiremath <hvaibhav@ti.com>
      Cc: Rajendra Nayak <rnayak@ti.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      78da2640
    • Kevin Hilman's avatar
      ARM: OMAP: omap_device: idle devices with no driver bound · 9634c8dd
      Kevin Hilman authored
      Under some circumstances, drivers may leave an omap_device enabled due
      to driver programming errors, or due to a failure in the drivers
      probe method.
      
      Using the recently added omap_device driver_status field, we can
      detect conditions where an omap_device is enabled but has no driver
      bound and then ensure that the device is properly idled until it can
      be probed again.
      
      The goal of this feature is not only to detect and warn on these error
      conditions, but also to ensure that devices are properly put in
      low-power states so they do not prevent SoC-wide low-power states.
      Reviewed-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarKevin Hilman <khilman@ti.com>
      9634c8dd