1. 30 9月, 2012 1 次提交
    • R
      ARM: add v7 multi-platform defconfig · 1ec9c26a
      Rob Herring 提交于
      Add a v7 defconfig enabling highbank, socfpga, mvebu, and vexpress
      platforms and their drivers. Most other options are left to the default.
      
      The existing individual platform defconfigs are kept for now as they are
      a bit different. In some cases, the choices look pretty arbitrary and
      just copied from other defconfigs.
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      Cc: Jason Cooper <jason@lakedaemon.net>
      Cc: Andrew Lunn <andrew@lunn.ch>
      Cc: Gregory Clement <gregory.clement@free-electrons.com>
      Cc: Dinh Nguyen <dinguyen@altera.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      1ec9c26a
  2. 29 9月, 2012 1 次提交
  3. 20 9月, 2012 1 次提交
  4. 17 9月, 2012 1 次提交
  5. 13 9月, 2012 1 次提交
  6. 12 9月, 2012 2 次提交
    • K
      ARM: shmobile: kzm9g: use gpio-keys instead of gpio-keys-polled · ee6691d7
      Kuninori Morimoto 提交于
      6e20a0a4
      (gpio: pcf857x: enable gpio_to_irq() support) supports
      gpio_to_irq() on pcf857x driver.
      Now, we can use gpio-keys driver instead of gpio-keys-polled.
      Signed-off-by: NKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
      Signed-off-by: NSimon Horman <horms@verge.net.au>
      Acked-by: NPaul Mundt <lethal@linux-sh.org>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      ee6691d7
    • S
      ARM: tegra: defconfig updates · 9df25ccc
      Stephen Warren 提交于
      Removed:
      
      * MACH_HARMONY
      * MACH_PAZ00
      * MACH_TRIMSLICE
      
        These used to enable board support for individual boards. Now that we
        only support device tree, these options have been removed.
      
      Added:
      
      * TEGRA_PCI
      
        This used to be selected by the board options above. Select this
        explicitly now that the board options have been removed.
      
      * TEGRA_DEBUG_UART_AUTO_ODMDATA
      
        This makes the kernel automatically pick a UART for earlyprintk. It's
        likely to be a useful option for everyone.
      
      * PWM
      * PWM_TEGRA
      
        Enable the new PWM subsystem, and the Tegra driver within it.
      
      * GPIO_PCA953X
      * GPIO_PCA953X_IRQ
      * MFD_MAX8907
      * REGULATOR_MAX8907
      * RTC_DRV_MAX8907
      * RTC_DRV_TPS65910
      
        Various drivers required for the Whistler board.
      
      * RTC_INTF_SYSFS
      * RTC_INTF_PROC
      * RTC_INTF_DEV
      
        Some RTC options that Kconfig help implies should typically be
        enabled.
      
      * Wifi chip (rt3070)
      * Bluetooth (btusb)
      * Camera (uvcvideo)
      * 3G modem (acm and wdm)
      * rfkill
      * GPIO LEDs
      * NVEC
      
        Various devices and features found on PAZ00 boards.
      
        Some of these are enabled as modules because they are not needed for
        boot and will not be used on other boards. Wifi also needs to be
        module because of the firmware loader.
      
        The update also enabled support for the rfkill switch, the Wifi LED and
        the nvec power and led driver which got lost in the past.
      
      * DEVTMPFS, TMPFS_POSIX_ACL
      
        These are mandatory on modern linux distros.
      Signed-off-by: NJoseph Lo <josephl@nvidia.com>
      Signed-off-by: NMarc Dietrich <marvin24@gmx.de>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      9df25ccc
  7. 11 9月, 2012 4 次提交
  8. 06 9月, 2012 3 次提交
  9. 04 9月, 2012 3 次提交
  10. 03 9月, 2012 1 次提交
  11. 28 8月, 2012 2 次提交
  12. 26 8月, 2012 1 次提交
  13. 24 8月, 2012 1 次提交
  14. 23 8月, 2012 1 次提交
    • A
      ARM: ux500: don't select LEDS_GPIO for snowball · db43b184
      Arnd Bergmann 提交于
      Using 'select' in Kconfig is hard, a platform cannot just
      enable a driver without also making sure that its subsystem
      is there. Also, there is no actual code dependency between
      the platform and the gpio leds driver.
      
      Without this patch, building without LEDS_CLASS esults in:
      
      drivers/built-in.o: In function `create_gpio_led.part.2':
      governor_userspace.c:(.devinit.text+0x5a58): undefined reference to `led_classdev_register'
      drivers/built-in.o: In function `gpio_led_remove':
      governor_userspace.c:(.devexit.text+0x6b8): undefined reference to `led_classdev_unregister'
      
      This reverts 8733f53c "ARM: ux500: Kconfig: Compile in leds-gpio
      support for Snowball" that introduced the regression and did not
      provide a helpful explanation.
      
      In order to leave the GPIO LED code still present in normal
      builds, this also enables the symbol in u8500_defconfig, in addition
      to the other LED drivers that are already selected there.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Lee Jones <lee.jones@linaro.org>
      db43b184
  15. 17 8月, 2012 1 次提交
    • S
      ARM: mxs: remove board files · ab9aad57
      Shawn Guo 提交于
      Since DT kernel provides the equivalent support with those board
      files, we can remove them now.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      Cc: Lothar Waßmann <LW@KARO-electronics.de>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Lauri Hintsala <lauri.hintsala@bluegiga.com>
      ab9aad57
  16. 16 8月, 2012 1 次提交
  17. 11 8月, 2012 1 次提交
  18. 10 8月, 2012 4 次提交
  19. 09 8月, 2012 1 次提交
    • A
      ARM: imx: gpmi-nand depends on mxs-dma · a3349377
      Arnd Bergmann 提交于
      It is not currently possible to build the gpmi-nand driver without
      also building the mxs-dma driver. Clarify this Kconfig and enable
      both in the defconfig file so we can build it again with both enabled.
      
      drivers/built-in.o: In function `gpmi_dma_filter':
      clk-fixed-factor.c:(.text+0xafc18): undefined reference to `mxs_dma_is_apbh'
      make[1]: *** [vmlinux] Error 1
      make: *** [sub-make] Error 2
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NDirk Behme <dirk.behme@de.bosch.com>
      Cc: Shawn Guo <shawn.guo@linaro.org>
      Cc: Sascha Hauer <kernel@pengutronix.de>
      a3349377
  20. 07 8月, 2012 1 次提交
  21. 06 8月, 2012 1 次提交
  22. 04 8月, 2012 1 次提交
    • M
      ARM: mxs: Remove MMAP_MIN_ADDR setting from mxs_defconfig · 3bed491c
      Marek Vasut 提交于
      The CONFIG_DEFAULT_MMAP_MIN_ADDR was set to 65536 in mxs_defconfig,
      this caused severe breakage of userland applications since the upper
      limit for ARM is 32768. By default CONFIG_DEFAULT_MMAP_MIN_ADDR is
      set to 4096 and can also be changed via /proc/sys/vm/mmap_min_addr
      if needed.
      
      Quoting Russell King [1]:
      
      "4096 is also fine for ARM too. There's not much point in having
      defconfigs change it - that would just be pure noise in the config
      files."
      
      the CONFIG_DEFAULT_MMAP_MIN_ADDR can be removed from the defconfig
      altogether.
      
      This problem was introduced by commit cde7c41f (ARM: configs: add
      defconfig for mach-mxs).
      
      [1] http://marc.info/?l=linux-arm-kernel&m=134401593807820&w=2Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: stable@vger.kernel.org
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Wolfgang Denk <wd@denx.de>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      3bed491c
  23. 31 7月, 2012 1 次提交
    • J
      ARM: 7481/1: OMAP2+: omap2plus_defconfig: enable OMAP DMA engine · 89269ef1
      Javier Martinez Canillas 提交于
      commit 13f30fc893e4610f67dd7a8b0b67aec02eac1775
      Author: Russell King <rmk+kernel@arm.linux.org.uk>
      Date:   Sat Apr 21 22:41:10 2012 +0100
      
          mmc: omap: remove private DMA API implementation
      
      removed the private DMA API implementation from the OMAP mmc host to exclusively use the DMA engine API.
      
      Unfortunately OMAP MMC and High Speed MMC host drivers don't support poll mode and only works with DMA.
      
      Since omap2plus_defconfig doesn't enable this feature by default, the
      following error is happens on an IGEPv2 Rev.C (and probably on most OMAP boards with MMC support):
      
      [    2.199981] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine channel 48
      [    2.215087] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62
      Signed-off-by: NJavier Martinez Canillas <javier@dowhile0.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      89269ef1
  24. 25 7月, 2012 1 次提交
  25. 22 7月, 2012 1 次提交
    • O
      ARM: exynos_defconfig: enable more platforms in defconfig · 8c0383b8
      Olof Johansson 提交于
      This enables the new EXYNOS5 platforms in the defconfig, and enables DT
      support on EXYNOS4.
      
      Other options enabled: USB host, EXT3/4, regulators and tps65090,
      networking and a few of the common usb ethernet adapters as well as the
      smsc911x controller used on some boards.
      
      I enabled EFI_PARTITION, since it's used on some filesystem images I'm
      using. I didn't see a need to keep Solaris and BSD partition format
      still enabled.
      
      Finally, framebuffer console, logo and fonts were enabled.
      
      Note that enabling some of these options introduces build coverage
      previously missing, thus introducing a few build errors and warnings
      for which fixes have been sent out already.
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      [kgene.kim@samsung.com: restored exynos4_defconfig from original]
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      8c0383b8
  26. 19 7月, 2012 1 次提交
  27. 12 7月, 2012 1 次提交
  28. 11 7月, 2012 1 次提交