1. 26 Jun, 2015 1 commit
    • Joe Hershberger's avatar
      Move default y configs out of arch/board Kconfig · c9bb942e
      Joe Hershberger authored
      
      
      Some archs/boards specify their own default by pre-defining the config
      which causes the Kconfig system to mix up the order of the configs in
      the defconfigs... This will cause merge pain if allowed to proliferate.
      
      Remove the configs that behave this way from the archs.
      
      A few configs still remain, but that is because they only exist as
      defaults and do not have a proper Kconfig entry. Those appear to be:
      
      SPIFLASH
      DISPLAY_BOARDINFO
      Signed-off-by: default avatarJoe Hershberger <joe.hershberger@ni.com>
      [trini: rastaban, am43xx_evm_usbhost_boot, am43xx_evm_ethboot updates,
      drop DM_USB from MSI_Primo81 as USB_MUSB_SUNXI isn't converted yet to DM]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      c9bb942e
  2. 19 Jun, 2015 1 commit
    • Nishanth Menon's avatar
      ARM: DRA7: Change configuration to prevent DDR reset control from EMIF · 67055bee
      Nishanth Menon authored
      DRA7/AM57xx devices can be operated in many different configurations.
      When the SoC is supposed to support a configuration where low power mode
      state may involve the SoC completely powered off and DDR is in self
      refresh, SoC EMIF controller should not be the master of the reset
      signal and an external entity might be in control of things.
      
      The default configuration of Linux on TI evms involve not powering off
      the voltage rails (due to various reasons including reliability concerns)
      and must not allow DDR reset to be controlled by EMIF. On platforms
      where external entity might control the reset signal, this configuration
      will be a "dont care".
      
      Fixes: 536d8747
      
       ("ARM: DRA7: Update DDR IO registers")
      Tested-by: default avatarKeerthy <j-keerthy@ti.com>
      Acked-by: default avatarBrad Griffis <bgriffis@ti.com>
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      67055bee
  3. 17 Jun, 2015 1 commit
  4. 15 Jun, 2015 3 commits
  5. 12 Jun, 2015 9 commits
  6. 11 Jun, 2015 2 commits
  7. 10 Jun, 2015 1 commit
  8. 08 Jun, 2015 1 commit
  9. 04 Jun, 2015 1 commit
    • Hans de Goede's avatar
      sunxi: usb_phy: Swap check for disconnect threshold · 7afebb5b
      Hans de Goede authored
      
      
      Before this commit the code for determining the disconnect threshold was
      checking for sun4i or sun6i assuming that those where the exception and
      that newer SoCs use a disconnect threshold of 2 like sun7i does.
      
      But it turns out that newer SoCs actually use a disconnect threshold of 3
      and sun5i and sun7i are the exceptions, so check for those instead.
      
      Here are the settings from the various Allwinner SDK sources:
       sun4i-a10: USBC_Phy_Write(usbc_no, 0x2a, 3, 2);
       sun5i-a13: USBC_Phy_Write(usbc_no, 0x2a, 2, 2);
       sun6i-a31: USBC_Phy_Write(usbc_no, 0x2a, 3, 2);
       sun7i-a20: USBC_Phy_Write(usbc_no, 0x2a, 2, 2);
       sun8i-a23: USBC_Phy_Write(usbc_no, 0x2a, 3, 2);
       sun8i-h3:  USBC_Phy_Write(usbc_no, 0x2a, 3, 2);
       sun9i-a80: USBC_Phy_Write(usbc_no, 0x2a, 3, 2);
      
      Note this commit makes no functional changes for sun4i - sun7i, and
      changes the disconnect threshold for sun8i to match what Allwinner uses.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Acked-by: default avatarIan Campbell <ijc@hellion.org.uk>
      7afebb5b
  10. 01 Jun, 2015 1 commit
  11. 31 May, 2015 4 commits
  12. 29 May, 2015 8 commits
  13. 28 May, 2015 1 commit
  14. 26 May, 2015 1 commit
  15. 19 May, 2015 5 commits