Skip to content
  1. May 22, 2017
  2. May 19, 2017
    • Olof Johansson's avatar
      devicetree: Move include prefixes from arch to separate directory · d5d332d3
      Olof Johansson authored
      We use a directory under arch/$ARCH/boot/dts as an include path
      that has links outside of the subtree to find dt-bindings from under
      include/dt-bindings. That's been working well, but new DT architectures
      haven't been adding them by default.
      
      Recently there's been a desire to share some of the DT material between
      arm and arm64, which originally caused developers to create symlinks or
      relative includes between the subtrees. This isn't ideal -- it breaks
      if the DT files aren't stored in the exact same hierarchy as the kernel
      tree, and generally it's just icky.
      
      As a somewhat cleaner solution we decided to add a $ARCH/ prefix link
      once, and allow DTS files to reference dtsi (and dts) files in other
      architectures that way.
      
      Original approach was to create these links under each architecture,
      but it lead to the problem of recursive symlinks.
      
      As a remedy, move the include link directories out of the architecture
      trees into a common location. At ...
      d5d332d3
  3. May 17, 2017
    • Ravikumar Kattekola's avatar
      ARM: dts: dra7: Reduce cpu thermal shutdown temperature · bca52388
      Ravikumar Kattekola authored
      
      
      On dra7, as per TRM, the HW shutdown (TSHUT) temperature is hardcoded
      to 123C and cannot be modified by SW. This means when the temperature
      reaches 123C HW asserts TSHUT output which signals a warm reset.
      This reset is held until the temperature goes below the TSHUT low (105C).
      
      While in SW, the thermal driver continuously monitors current temperature
      and takes decisions based on whether it reached an alert or a critical point.
      The intention of setting a SW critical point is to prevent force reset by HW
      and instead do an orderly_poweroff(). But if the SW critical temperature is
      greater than or equal to that of HW then it defeats the purpose. To address
      this and let SW take action before HW does keep the SW critical temperature
      less than HW TSHUT value.
      
      The value for SW critical temperature was chosen as 120C just to ensure
      we give SW sometime before HW catches up.
      
      Document reference
      SPRUI30C – DRA75x, DRA74x Technical Reference Manual - November 2016
      SPRUHZ6H - AM572x Technical Reference Manual - November 2016
      
      Tested on:
      DRA75x PG 2.0 Rev H EVM
      
      Signed-off-by: default avatarRavikumar Kattekola <rk@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      bca52388
  4. May 16, 2017
  5. May 15, 2017
    • Leonard Crestez's avatar
      ARM: dts: imx6sx-sdb: Remove OPP override · d8581c7c
      Leonard Crestez authored
      
      
      The board file for imx6sx-sdb overrides cpufreq operating points to use
      higher voltages. This is done because the board has a shared rail for
      VDD_ARM_IN and VDD_SOC_IN and when using LDO bypass the shared voltage
      needs to be a value suitable for both ARM and SOC.
      
      This only applies to LDO bypass mode, a feature not present in upstream.
      When LDOs are enabled the effect is to use higher voltages than necessary
      for no good reason.
      
      Setting these higher voltages can make some boards fail to boot with ugly
      semi-random crashes reminiscent of memory corruption. These failures only
      happen on board rev. C, rev. B is reported to still work.
      
      Signed-off-by: default avatarLeonard Crestez <leonard.crestez@nxp.com>
      Fixes: 54183bd7 ("ARM: imx6sx-sdb: add revb board and make it default")
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarShawn Guo <shawnguo@kernel.org>
      d8581c7c
    • Fabio Estevam's avatar
      ARM: dts: imx53-qsrb: Pulldown PMIC IRQ pin · 2fe4bff3
      Fabio Estevam authored
      
      
      Currently the following errors are seen:
      
      [   14.015056] mc13xxx 0-0008: Failed to read IRQ status: -6
      [   27.321093] mc13xxx 0-0008: Failed to read IRQ status: -6
      [   27.411681] mc13xxx 0-0008: Failed to read IRQ status: -6
      [   27.456281] mc13xxx 0-0008: Failed to read IRQ status: -6
      [   30.527106] mc13xxx 0-0008: Failed to read IRQ status: -6
      [   36.596900] mc13xxx 0-0008: Failed to read IRQ status: -6
      
      Also when reading the interrupts via 'cat /proc/interrupts' the
      PMIC GPIO interrupt counter does not stop increasing.
      
      The reason for the storm of interrupts is that the PUS field of
      register IOMUXC_SW_PAD_CTL_PAD_CSI0_DAT5 is currently configured as:
      10 : 100k pullup
      
      and the PMIC interrupt is being registered as IRQ_TYPE_LEVEL_HIGH type,
      which is the correct type as per the MC34708 datasheet.
      
      Use the default power on value for the IOMUX, which sets PUS field as:
      00: 360k pull down
      
      This prevents the spurious PMIC interrupts from happening.
      
      Commit e1ffceb0 ("ARM: imx53: qsrb: fix PMIC interrupt level")
      correctly described the irq type as IRQ_TYPE_LEVEL_HIGH, but
      missed to update the IOMUX of the PMIC GPIO as pull down.
      
      Fixes: e1ffceb0 ("ARM: imx53: qsrb: fix PMIC interrupt level")
      Signed-off-by: default avatarFabio Estevam <fabio.estevam@nxp.com>
      Signed-off-by: default avatarShawn Guo <shawnguo@kernel.org>
      2fe4bff3
  6. May 10, 2017
  7. Apr 21, 2017
  8. Apr 19, 2017
  9. Apr 14, 2017
  10. Apr 12, 2017
  11. Apr 11, 2017
  12. Apr 10, 2017