1. 14 Jul, 2016 2 commits
  2. 11 Jul, 2016 2 commits
    • Thierry Reding's avatar
      arm64: Update default configuration · 10a7b37b
      Thierry Reding authored
      Enable a couple of drivers that are used on Jetson TX1:
      
        * GPIO_PCA953X, GPIO_PCA953X_IRQ: Two instances of this I2C GPIO
          expander are used on Jetson TX1 to expand the number of usable GPIOs
          on the I/O board. Enable the driver for this expander along with IRQ
          support.
      
        * MFD_MAX77620, REGULATOR_MAX77620, PINCTRL_MAX77620, GPIO_MAX77620,
          RTC_DRV_MAX77686: Enable support for the PMIC and various of its
          components found on the Jetson TX1 processor module (p2180).
      
        * RTC_DRV_TEGRA: This RTC is usually not hooked up to a battery on
          boards, but it can be useful as a wakeup source from suspend to RAM.
      
        * REGULATOR_PWM: The GPU is supplied by a regulator controlled via one
          of the Tegra's PWM channels.
      
        * DRM, DRM_NOUVEAU, DRM_TEGRA, DRM_PANEL_SIMPLE: Enable support for an
          optional DSI panel on Jetson TX1 as well as the GPU.
      
        * BACKLIGHT_GENERIC, BACKLIGHT_LP855X: The backlight on Jetson TX1, if
          shipped with a display module, is driver by an LP8557.
      
        * PHY_TEGRA_XUSB, USB_XHCI_TEGRA: Enable support for XUSB (USB 3.0) on
          Jetson TX1.
      
        * PWM, PWM_TEGRA: One of the PWM channels is used to control the
          voltage supplied to the GPU.
      
        * NFS_V4_1, NFS_V4_2: Support these newer versions of the NFS protocol
          to increase compatibility with distributions.
      
        * MFD_CROS_EC, MFD_CROS_EC_I2C and I2C_CROS_EC_TUNNEL: Used to enable
          the ChromeOS Embedded Controller and the I2C tunnel that allows the
          EC to function as an I2C bridge.
      
        * BATTERY_BQ27XXX: Support the battery charger and monitor found on
          the Google Pixel C.
      Signed-off-by: default avatarThierry Reding <treding@nvidia.com>
      10a7b37b
    • Krzysztof Kozlowski's avatar
      arm64: defconfig: Enable more IP blocks for Exynos7 and Exynos5433 · 426f754b
      Krzysztof Kozlowski authored
      Enable more drivers for IP blocks for existing Exynos7 and upcoming
      Exynos5433:
      1. SPI,
      2. Watchdog,
      3. USB: DWC3, Exynos EHCI and OHCI,
      4. Exynos ADC,
      5. Samsung PWM.
      
      These are already used by Exynos7 Espresso board or will be used by
      Exynos5433 based board.
      Signed-off-by: default avatarKrzysztof Kozlowski <krzk@kernel.org>
      Reviewed-by: default avatarAlim Akhtar <alim.akhtar@samsung.com>
      426f754b
  3. 07 Jul, 2016 4 commits
  4. 06 Jul, 2016 2 commits
  5. 05 Jul, 2016 3 commits
  6. 04 Jul, 2016 1 commit
  7. 25 Jun, 2016 3 commits
  8. 23 Jun, 2016 1 commit
  9. 21 Jun, 2016 1 commit
    • Sudeep Holla's avatar
      arm64: Kconfig: select PM{,_GENERIC_DOMAINS} for ARCH_VEXPRESS · 8da7cc08
      Sudeep Holla authored
      The Linux AMBA bus framework probes the peripheral IDs when adding the
      AMBA devices very early on the boot. Generally they are on APB bus and
      just require APB clocks to be on even when most of the core logic of the
      IP is powered down.
      
      However on Juno, the entire debugsys domain needs to be ON to access
      even the coresight components' CID/PID registers and hence broken by
      design. Accessing those while debugsys power domain is off will lead to
      the bridge stalling the transactions instead of returning the slave error.
      
      Further, the AMBA framework can't deal with !CONFIG_PM_GENERIC_DOMAINS
      case: it ignores the error and proceeds to access the device region.
      It was suggested to always enable CONFIG_PM{,_GENERIC_DOMAINS} in order
      to handle above explained scenario.
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Suggested-by: default avatarUlf Hansson <ulf.hansson@linaro.org>
      Signed-off-by: default avatarSudeep Holla <sudeep.holla@arm.com>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      8da7cc08
  10. 20 Jun, 2016 3 commits
  11. 16 Jun, 2016 1 commit
  12. 15 Jun, 2016 2 commits
  13. 14 Jun, 2016 2 commits
  14. 13 Jun, 2016 1 commit
  15. 06 Jun, 2016 2 commits
  16. 04 Jun, 2016 1 commit
  17. 03 Jun, 2016 1 commit
  18. 01 Jun, 2016 1 commit
  19. 31 May, 2016 1 commit
  20. 30 May, 2016 1 commit
  21. 29 May, 2016 3 commits
  22. 28 May, 2016 2 commits
    • Mikulas Patocka's avatar
      hpfs: implement the show_options method · 037369b8
      Mikulas Patocka authored
      The HPFS filesystem used generic_show_options to produce string that is
      displayed in /proc/mounts.  However, there is a problem that the options
      may disappear after remount.  If we mount the filesystem with option1
      and then remount it with option2, /proc/mounts should show both option1
      and option2, however it only shows option2 because the whole option
      string is replaced with replace_mount_options in hpfs_remount_fs.
      
      To fix this bug, implement the hpfs_show_options function that prints
      options that are currently selected.
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      037369b8
    • Mikulas Patocka's avatar
      affs: fix remount failure when there are no options changed · 01d6e087
      Mikulas Patocka authored
      Commit c8f33d0b ("affs: kstrdup() memory handling") checks if the
      kstrdup function returns NULL due to out-of-memory condition.
      
      However, if we are remounting a filesystem with no change to
      filesystem-specific options, the parameter data is NULL.  In this case,
      kstrdup returns NULL (because it was passed NULL parameter), although no
      out of memory condition exists.  The mount syscall then fails with
      ENOMEM.
      
      This patch fixes the bug.  We fail with ENOMEM only if data is non-NULL.
      
      The patch also changes the call to replace_mount_options - if we didn't
      pass any filesystem-specific options, we don't call
      replace_mount_options (thus we don't erase existing reported options).
      
      Fixes: c8f33d0b ("affs: kstrdup() memory handling")
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Cc: stable@vger.kernel.org	# v4.1+
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      01d6e087