1. 01 6月, 2015 2 次提交
  2. 30 5月, 2015 2 次提交
  3. 29 5月, 2015 3 次提交
  4. 28 5月, 2015 1 次提交
  5. 25 5月, 2015 1 次提交
    • A
      ARM: shmobile: only select sound drivers that build · 66f72f0c
      Arnd Bergmann 提交于
      A couple of codec drivers are selected by shmobile platform code,
      but depend on I2C, which results in a build error:
      
      sound/soc/codecs/ak4642.c:638:1: warning: data definition has no type or storage class
       module_i2c_driver(ak4642_i2c_driver);
       ^
      sound/soc/codecs/ak4642.c:638:1: error: type defaults to 'int' in declaration of 'module_i2c_driver' [-Werror=implicit-int]
      sound/soc/codecs/ak4642.c:638:1: warning: parameter names (without types) in function declaration
      sound/soc/codecs/ak4642.c:627:26: warning: 'ak4642_i2c_driver' defined but not used [-Wunused-variable]
      
      This ensures that we do not enable the respective drivers when I2C
      is disabled.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      66f72f0c
  6. 22 5月, 2015 6 次提交
    • S
      ARM: use ARM_SINGLE_ARMV7M for ARMv7-M platforms · 499f1640
      Stefan Agner 提交于
      Use the new config symbol ARM_SINGLE_ARMV7M which groups config
      symbols used by modern ARMv7-M platforms. This allows supporting
      multiple ARMv7-M platforms in one kernel image. However, a common
      kernel image requires the combined platforms to share the same
      main memory layout to be bootable.
      Signed-off-by: NStefan Agner <stefan@agner.ch>
      Acked-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Acked-by: NJoachim Eastwood <manabian@gmail.com>
      Acked-by: NMaxime Coquelin <maxime.coquelin@st.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      499f1640
    • A
      ARM: zx: fix building with CONFIG_THUMB2_KERNEL · 993198a6
      Arnd Bergmann 提交于
      The newly added zx platform causes a build error when
      CONFIG_THUMB2_KERNEL is enabled:
      
      arch/arm/mach-zx/headsmp.S:16: Error: invalid immediate for address calculation (value = 0x00000004)
      
      I'm assuming that the ROM code that is calling these entry
      points runs in ARM mode, so there would be another problem
      in the same file, and we can solve both problems at once
      by adding a '.arm' statement that will make zx_resume_jump
      and zx_secondary_startup both be built as ARM code.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NJun Nie <jun.nie@linaro.org>
      Tested-by: NJun Nie <jun.nie@linaro.org>
      993198a6
    • A
      Merge tag 'omap-for-v4.2/omap1-v2' of... · ac0b2092
      Arnd Bergmann 提交于
      Merge tag 'omap-for-v4.2/omap1-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into next/soc
      
      Merge fixed up omap1 sparse irq support for v4.2 from Tony Lindgren:
      
      Add support for CONFIG_SPARSE_IRQ for omap1. This takes us a bit closer
      to making omap1 support multiarch. After this series we still need to
      make omap1 use the common clock framework and fix up the drivers to not
      rely on includes from mach and plat directories.
      
      Note that this branch depends on a GPIO driver fix in v4.1-rc3
      d2d05c65 ("gpio: omap: Fix regression for MPUIO interrupts").
      
      * tag 'omap-for-v4.2/omap1-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        ARM: OMAP1: Fix section mismatch warnings for omap_cfg_reg
        ARM: OMAP1: Fix randconfig builds if ARCH_OMAP15XX not selected
        ARM: OMAP1: Change interrupt numbering for sparse IRQ
        ARM: omap1: Switch to use MULTI_IRQ
        ARM: OMAP1: Switch to use generic irqchip in preparation for sparse IRQ
        ARM: OMAP1: Move UART defines to prepare for sparse IRQ
      ac0b2092
    • A
      Merge tag 'arm-soc/for-4.2/soc-take2' of http://github.com/broadcom/stblinux into next/soc · a4526915
      Arnd Bergmann 提交于
      Merge mach-bcm changes from Florian Fainelli:
      
      This pull request contains the following changes:
      
      - Rafal adds an additional fault code to be ignored by the kernel on BCM5301X SoC
      
      - BCM63138 SMP support which:
      	* common code to control the PMB bus, to be shared with a reset
      	  controller driver in drivers/reset
      	* secondary CPU initialization sequence using PMB helpers
      	* small changes suggested by Russell King to allow platforms to disable VFP
      
      * tag 'arm-soc/for-4.2/soc-take2' of http://github.com/broadcom/stblinux:
        ARM: BCM63xx: Add SMP support for BCM63138
        ARM: vfp: Add vfp_disable for problematic platforms
        ARM: vfp: Add include guards
        ARM: BCM63xx: Add secondary CPU PMB initialization sequence
        ARM: BCM63xx: Add Broadcom BCM63xx PMB controller helpers
        ARM: BCM5301X: Ignore another (BCM4709 specific) fault code
      a4526915
    • T
      ARM: OMAP1: Fix section mismatch warnings for omap_cfg_reg · 7bf15c43
      Tony Lindgren 提交于
      This is cleary used after init time too for example for
      configuring UART wake-up events during runtime. This fixes
      section mismatch warnings for randconfig builds that happen
      because __init_or_module.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      7bf15c43
    • T
      ARM: OMAP1: Fix randconfig builds if ARCH_OMAP15XX not selected · e99b32e2
      Tony Lindgren 提交于
      With the omap1 SPARSE_IRQ changes mach/irqs.h is no longer
      automatically included. Turns out now we rely on ARCH_OMAP15XX
      including hardware.h from memory.h, so without ARCH_OMAP15XX
      we get build failures.
      
      As we have legacy drivers still relying on these indirect
      includes, let's not add more mach includes to the drivers.
      Those have to be removed anyways for multiplatform support.
      
      Let's fix up mach-omap1 to include soc.h where cpu_is_omap
      checks are done, and common.h for board-*.c files.
      
      But let's keep the indirect memory.h include for now to avoid
      unnecessary churn in the drivers.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      e99b32e2
  7. 21 5月, 2015 15 次提交
  8. 20 5月, 2015 4 次提交
  9. 19 5月, 2015 1 次提交
    • S
      irqchip: vf610-mscm: Support NVIC parent chip · b5cc5cbc
      Stefan Agner 提交于
      Support the NVIC interrupt controller as node parent of the MSCM
      interrupt router. On the dual-core variants of Vybird (VF6xx), the
      NVIC interrupt controller is used by the Cortex-M4. To support
      running Linux on this core too, MSCM needs NVIC parent support too.
      Signed-off-by: NStefan Agner <stefan@agner.ch>
      Cc: marc.zyngier@arm.com
      Cc: linux@arm.linux.org.uk
      Cc: u.kleine-koenig@pengutronix.de
      Cc: olof@lixom.net
      Cc: arnd@arndb.de
      Cc: daniel.lezcano@linaro.org
      Cc: mark.rutland@arm.com
      Cc: pawel.moll@arm.com
      Cc: robh+dt@kernel.org
      Cc: ijc+devicetree@hellion.org.uk
      Cc: galak@codeaurora.org
      Cc: mcoquelin.stm32@gmail.com
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: shawn.guo@linaro.org
      Cc: kernel@pengutronix.de
      Cc: jason@lakedaemon.net
      Link: http://lkml.kernel.org/r/1431769465-26867-6-git-send-email-stefan@agner.chSigned-off-by: NThomas Gleixner <tglx@linutronix.de>
      b5cc5cbc
  10. 18 5月, 2015 5 次提交