Skip to content
  1. Jul 07, 2015
  2. Jul 06, 2015
  3. Jul 01, 2015
  4. Jun 11, 2015
    • Linus Walleij's avatar
      ARM64: juno: add GPIO keys · 53bdd72c
      Linus Walleij authored
      
      
      The Juno board has two keys connected to a PL061 GPIO block,
      in accordance to DDI0524B "ARM Versatile Express Juno Development
      Platform" revision 1.0, table 2-4 "GPIO (0) and GPIO (1) used
      for additional user key entry". By trial-and-error I found that
      these are connected to the two keys named "power" and "home"
      on the motherboard.
      
      Register the GPIO block and these two keys in the device tree
      using the PL061 GPIO driver and the generic gpio keys.
      
      - Map POWER, HOME, VOL+ and VOL- to the obvious input events.
      - Map RLOCK to KEY_SCREENLOCK/KEY_COFFEE unless someone can
        explain better what this is for.
      - Map the NMI button to KEY_SYSREQ as this is used like so
        in the SYSREQ debugging hack.
      
      Acked-by: default avatarLiviu Dudau <Liviu.Dudau@arm.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarKevin Hilman <khilman@linaro.org>
      53bdd72c
  5. Jun 05, 2015
  6. Jun 01, 2015
  7. May 29, 2015
  8. May 22, 2015
  9. May 12, 2015
    • Mark Rutland's avatar
      arm64: dts: kill skeleton.dtsi · 3ebee5a2
      Mark Rutland authored
      
      
      While skeleton.dtsi was initially conceived as a simple way to bootstrap
      writing a dts, it has proven to be problematic:
      
      * The #address-cells and #size-cells values used in skeleton.dtsi may
        not match what a user wants (e.g. when they need to describe a range
        larger than 4GB).
      
      * For dts files where memory nodes have unit-addresses, it adds a
        redundant /memory node, for which the reg entry may not be
        appropriately sized (e.g. where #size-cells has been overridden).
      
      * For dts files which assume that a bootloader will fill in the memory
        node(s), no node is present in the dts (and hence there is no attached
        comment), making it hard to distinguish these cases from bad dts
        files, and masking any warnings dtc may produce w.r.t. missing nodes.
      
      * The default empty /chosen and /aliases are somewhat useless, and it
        would be preferable for dts to fill these in (e.g. for
        /aliases/serial0 and /chosen/stdout-path).
      
      This patch removes skeleton.dtsi from arm64. There are currently no
      users, so we can remove it before any appear.
      
      Signed-off-by: default avatarMark Rutland <mark.rutland@arm.com>
      Acked-by: default avatarRob Herring <rob.herring@arm.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Olof Johansson <olof@lixom.net>
      Cc: Will Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      3ebee5a2
    • Sudeep Holla's avatar
      ARM64: juno: add sp810 support and fix sp804 clock frequency · 3bb1555c
      Sudeep Holla authored
      
      
      The clock generator in IOFPGA generates the two source clocks: 32kHz and
      1MHz for the SP810 System Controller.
      
      The SP810 System Controller selects 32kHz or 1MHz as the sources for
      TIM_CLK[3:0], the SP804 timer clocks. The powerup default is 32kHz but
      the maximum of "refclk" and "timclk" is chosen by the SP810 driver.
      
      This patch adds support for SP810 system controller and also fixes the
      SP804 timer clock frequency.
      
      However the SP804 driver needs to be enabled on ARM64 to test this,
      which requires SP804 driver to be moved out of arch/arm.
      
      Fixes: 71f867ec ("arm64: Add Juno board device tree.")
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Olof Johansson <olof@lixom.net>
      Acked-by: default avatarLiviu Dudau <Liviu.Dudau@arm.com>
      Signed-off-by: default avatarSudeep Holla <sudeep.holla@arm.com>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      3bb1555c
  10. May 11, 2015
    • Linus Walleij's avatar
      arm64: juno: Add APB registers and LEDs using syscon · bfb47629
      Linus Walleij authored
      
      
      This defines the Juno "APB system registers" as a syscon device,
      and all the LEDs controlled by the APB system registers right
      below it using the syscon LEDs driver on top of syscon. Define
      LED0 for heartbeat, LED1 for MMC0 activity and the following
      four LEDs indicating CPU activity using the Linux-specific
      DT bindings for triggers.
      
      This is the pattern and same drivers as used on the legacy
      platform device trees for the ARM Integrators and the RealView
      PB1176.
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Robin Murphy <robin.murphy@arm.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Tested-by: default avatarLiviu Dudau <Liviu.Dudau@arm.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      bfb47629
  11. May 04, 2015
  12. Apr 27, 2015
  13. Apr 03, 2015
  14. Apr 02, 2015
  15. Mar 29, 2015
  16. Mar 27, 2015
  17. Mar 18, 2015
  18. Mar 11, 2015
  19. Mar 10, 2015
Loading