Skip to content
  1. Jun 21, 2016
  2. Apr 15, 2016
  3. Mar 13, 2016
  4. Mar 08, 2016
  5. Feb 10, 2016
  6. Feb 09, 2016
  7. Feb 01, 2016
  8. Dec 22, 2015
  9. Oct 31, 2015
    • Linus Walleij's avatar
      ARM64: juno: disable NOR flash node by default · 980bbff0
      Linus Walleij authored
      
      
      After discussing on the mailing list it turns out that
      accessing the flash memory from the kernel can disrupt CPU
      sleep states and CPU hotplugging, so let's disable this
      DT node by default. Setups that want to access the flash
      can modify this entry to enable the flash again.
      
      Quoting Sudeep Holla: "the firmware assumes the flash is
      always in read mode while Linux leaves NOR flash in
      "read id" mode after initialization."
      
      Reported-by: default avatarSudeep Holla <sudeep.holla@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Liviu Dudau <Liviu.Dudau@arm.com>
      Cc: Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Leif Lindholm <leif.lindholm@arm.com>
      Cc: Ryan Harkin <ryan.harkin@linaro.org>
      Fixes: 5078f77e "ARM64: juno: add NOR flash to device tree"
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      980bbff0
  10. Oct 26, 2015
  11. Oct 22, 2015
  12. Oct 15, 2015
    • Linus Walleij's avatar
      ARM64: juno: add NOR flash to device tree · 5078f77e
      Linus Walleij authored
      
      
      The Juno motherboard has a NOR flash on the motherboard, enable
      this to be accessed with the CFI flash driver. Results after
      enabling MTD, MTD_CFI, MTD_PHYSMAP, MTD_PHYSMAP_OF,
      MTD_CFI_INTELEXT:
      
      8000000.flash: Found 2 x16 devices at 0x0 in 32-bit bank.
      Manufacturer ID 0x000089 Chip ID 0x008919
      Intel/Sharp Extended Query Table at 0x010A
      Intel/Sharp Extended Query Table at 0x010A
      Intel/Sharp Extended Query Table at 0x010A
      Intel/Sharp Extended Query Table at 0x010A
      Intel/Sharp Extended Query Table at 0x010A
      Using buffer write method
      Using auto-unlock on power-up/resume
      cfi_cmdset_0001: Erase suspend on write enabled
      erase region 0: offset=0x0,size=0x40000,blocks=255
      erase region 1: offset=0x3fc0000,size=0x10000,blocks=4
      
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Acked-by: default avatarLiviu Dudau <Liviu.Dudau@arm.com>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      5078f77e
  13. Oct 14, 2015
    • Ian Campbell's avatar
      ARM64: dts: vexpress: Use a symlink to vexpress-v2m-rs1.dtsi from arch=arm · 8ee57b81
      Ian Campbell authored
      Commit 9ccd6080 "arm64: dts: add device tree for ARM SMM-A53x2 on
      LogicTile Express 20MG" added a new dts file to arch/arm64 which
      included "../../../../arm/boot/dts/vexpress-v2m-rs1.dtsi", i.e. a
      .dtsi supplied by arch/arm.
      
      Unfortunately this causes some issues for the split device tree
      repository[0], since things get moved around there. In that context
      the new .dts ends up at src/arm64/arm/vexpress-v2f-1xv7-ca53x2.dts
      while the include is at src/arm/vexpress-v2m-rs1.dtsi.
      
      The sharing of the .dtsi is legitimate since the baseboard is the same
      for various vexpress systems whatever processor they use.
      
      Previously I attempted to resolve this by creating a shared location
      for such things but we have been unable to come to a consensus on
      where that should be.
      
      Instead this patch simply replaces the use of ../../ in the dts
      /include/ with a symlink in arch/arm64/boot/dts/arm pointing to the
      file arch/arm/boot/dts.
      
      Since the split device tree repo will shortly be required to flatten
      symlinks for other reasons this will cause the dtsi file to appear in
      both src/arm and src/arm64 in the split repo, which is an improvement
      on not building for arm64 now.
      
      [0] https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-rebasing.git/
      
      
      
      Signed-off-by: default avatarIan Campbell <ian.campbell@citrix.com>
      Acked-by: default avatarMark Rutland <mark.rutland@arm.com>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Liviu Dudau <liviu.dudau@arm.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Catalin Marinas <catalin.marinas@arm.com>
      Cc: Will Deacon <will.deacon@arm.com>
      Cc: Kristina Martsenko <kristina.martsenko@arm.com>
      Cc: Kevin Hilman <khilman@linaro.org>
      Cc: Frank Rowand <frank.rowand@sonymobile.com>
      Cc: Olof Johansson <olof@lixom.net>
      Cc: devicetree@vger.kernel.org
      Cc: linux-kernel@vger.kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: arm@kernel.org
      Cc: linux-kbuild@vger.kernel.org
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      8ee57b81
  14. Oct 09, 2015
  15. Oct 07, 2015
  16. Aug 18, 2015
  17. Jul 08, 2015
  18. 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
  19. May 22, 2015
  20. May 12, 2015
    • 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
  21. 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
  22. Apr 03, 2015
  23. Mar 29, 2015
  24. Feb 25, 2015
    • Sudeep Holla's avatar
      arm64: Add L2 cache topology to ARM Ltd boards/models · 7934d69a
      Sudeep Holla authored
      
      
      Commit 5d425c18 ("arm64: kernel: add support for cpu cache
      information") adds cacheinfo support for ARM64. Since there's no
      architectural way of detecting the cpus that share particular cache,
      device tree can be used and the core cacheinfo already supports the
      same.
      
      This patch adds the L2 cache topology on Juno board, FVP/RTSM and
      foundation models.
      
      Signed-off-by: default avatarSudeep Holla <sudeep.holla@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Liviu Dudau <Liviu.Dudau@arm.com>
      Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      7934d69a
  25. Jan 23, 2015
  26. Nov 28, 2014
Loading