1. 26 6月, 2013 1 次提交
  2. 07 5月, 2013 1 次提交
  3. 20 3月, 2013 1 次提交
  4. 13 3月, 2013 1 次提交
  5. 04 2月, 2013 1 次提交
  6. 02 2月, 2013 1 次提交
  7. 24 1月, 2013 1 次提交
  8. 22 1月, 2013 2 次提交
  9. 07 12月, 2012 1 次提交
  10. 04 12月, 2012 1 次提交
  11. 20 11月, 2012 1 次提交
    • C
      Add support for generic BCM SoC chipsets · 8ac49e04
      Christian Daudt 提交于
      In order to start upstreaming Broadcom SoC support, create
      a starting hierarchy, arch and dts files.
      The first support SoC family that is planned is the
      BCM281XX (BCM11130/11140/11351/28145/28155) family of dual A9 mobile
      SoC cores.
      This code is just the skeleton code for get the machine upstreamed. It
      has been made MULTIPLATFORM compatible.
      Next steps
      ----------
      Upstream a basic set of drivers - sufficient for a console boot to
      ramdisk. These will includer timer, gpio, i2c drivers.
      After this basic set, we will proceed with a more comprehensive set
      of drivers for the 281XX SoC family.
      
      v2 patch mods
      --------
       - Remove l2x0_of_init call as there were problems with the code.
         A separate patch will be submitted with cache init code
       - Rename capri files and refs to bcm281xx-based names
       - Add bcm281xx binding doc
       - various misc cleanups
      
      v3 patch mods
      -------------
       - Remove extra #include lines
       - Remove remaining references to capri
       - dt uart chipset string added
       - cleaned up chip # references
      
      v4 patch mods
      -------------
       - swap order of compatible definitions for uart
       - fix typo
      
      v5 patch mods
      -------------
       - Rename bcm281xx to bcm11351 in dts+code,
         leaving references to bcm281xx only in help+comments.
      
      v6 patch mods
      -------------
       - fix typo in uart 'compatible' string
      Signed-off-by: NChristian Daudt <csd@broadcom.com>
      Reviewed-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      8ac49e04
  12. 17 11月, 2012 1 次提交
  13. 05 11月, 2012 1 次提交
    • L
      ARM: plat-nomadik: move MTU, kill plat-nomadik · 694e33a7
      Linus Walleij 提交于
      This moves the MTU timer driver from arch/arm/plat-nomadik
      to drivers/clocksource and moves the header file to the
      platform_data directory.
      
      As this moves the last file being compiled to an object out
      of arch/arm/plat-nomadik, we have to "turn off the light"
      and delete the plat-nomadik directory, because it is not
      allowed to have an empty Makefile in a plat-* directory.
      This is probably also a desired side effect of depopulating
      the arch/arm directory of drivers. Luckily we have just
      deleted all the <plat/*> include files prior to this so
      by moving the last one we may delete the directory.
      
      After this all the Ux500 and Nomadik device drivers live
      outside of the arch/arm hierarchy.
      
      Cc: Alessandro Rubini <rubini@unipv.it>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      694e33a7
  14. 29 10月, 2012 1 次提交
    • J
      zynq: remove use of CLKDEV_LOOKUP · f7977939
      Josh Cartwright 提交于
      The Zynq support in mainline does not (yet) make use of any of the
      generic clk or clk lookup functionality.  Remove what is upstream for
      now, until the out-of-tree implementation is in suitable form for
      merging.
      
      An important side effect of this patch is that it allows the building of
      a Zynq kernel without running into unresolved symbol problems:
      
         drivers/built-in.o: In function `amba_get_enable_pclk':
         clkdev.c:(.text+0x444): undefined reference to `clk_enable'
         drivers/built-in.o: In function `amba_remove':
         clkdev.c:(.text+0x488): undefined reference to `clk_disable'
         drivers/built-in.o: In function `amba_probe':
         clkdev.c:(.text+0x540): undefined reference to `clk_disable'
         drivers/built-in.o: In function `amba_device_add':
         clkdev.c:(.text+0x77c): undefined reference to `clk_disable'
         drivers/built-in.o: In function `enable_clock':
         clkdev.c:(.text+0x29738): undefined reference to `clk_enable'
         drivers/built-in.o: In function `disable_clock':
         clkdev.c:(.text+0x29778): undefined reference to `clk_disable'
         drivers/built-in.o: In function `__pm_clk_remove':
         clkdev.c:(.text+0x297f8): undefined reference to `clk_disable'
         drivers/built-in.o: In function `pm_clk_suspend':
         clkdev.c:(.text+0x29bc8): undefined reference to `clk_disable'
         drivers/built-in.o: In function `pm_clk_resume':
         clkdev.c:(.text+0x29c28): undefined reference to `clk_enable'
         make[2]: *** [vmlinux] Error 1
         make[1]: *** [sub-make] Error 2
         make: *** [all] Error 2
      
      In addition, eliminate Zynq's "use" of the versatile platform, as it is
      no longer needed.  As Nick Bowler points out:
      
         For the record, I think this was introduced by commit 56a34b03
         ("ARM: versatile: Make plat-versatile clock optional") which forgot to
         select PLAT_VERSATILE_CLOCK on Zynq.  This is not all that surprising,
         because the fact that Zynq "uses" PLAT_VERSATILE is secretly hidden in
         the Makefile.
      
         Nevertheless, the only feature from versatile that Zynq needed was the
         clock support, so this patch should *also* delete the secret use of
         plat-versatile by removing this line from arch/arm/Makefile:
      
            plat-$(CONFIG_ARCH_ZYNQ)      += versatile
      Signed-off-by: NJosh Cartwright <josh.cartwright@ni.com>
      Cc: John Linn <john.linn@xilinx.com>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Tested-by: NMichal Simek <michal.simek@xilinx.com>
      f7977939
  15. 15 10月, 2012 1 次提交
  16. 10 10月, 2012 1 次提交
    • A
      ARM: pass -marm to gcc by default for both C and assembler · 91802a8e
      Arnd Bergmann 提交于
      The Linaro cross toolchain and probably others nowadays default to
      building in THUMB2 mode. When building a kernel for a CPU that does
      not support THUMB2, the compiler complains about incorrect flags.
      We can work around this by setting -marm for all non-T2 builds.
      
      -marm was passed unconditionally for C files previously, but nothing was
      passed to the gcc frontend when processing .S files, resulting in a
      warning.  The assembler never defaults to ARM unless -Wa,-mthumb is
      supplied explicitly, so the files were still assembled correctly.
      
      This patch makes sure that -marm is passed for .S files too, and also
      avoids the redundant gcc -marm -mthumb in Thumb kernels.
      
      Without this patch, building assabet_defconfig results in:
      
      usr/initramfs_data.S:1:0: warning: target CPU does not support THUMB instructions [enabled by default]
      arch/arm/nwfpe/entry.S:1:0: warning: target CPU does not support THUMB instructions [enabled by default]
      firmware/cis/PCMLM28.cis.gen.S:1:0: warning: target CPU does not support THUMB instructions [enabled by default]
      (and many more)
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Acked-by: NNicolas Pitre <nico@linaro.org>
      Acked-by: NDave Martin <dave.martin@linaro.org>
      Cc: Russell King <rmk+kernel@arm.linux.org.uk>
      91802a8e
  17. 29 9月, 2012 1 次提交
  18. 20 9月, 2012 1 次提交
  19. 16 9月, 2012 1 次提交
  20. 14 9月, 2012 1 次提交
    • R
      ARM: initial multiplatform support · 387798b3
      Rob Herring 提交于
      This lets us build a multiplatform kernel for experimental purposes.
      However, it will not be useful for any real work, because it relies
      on a number of useful things to be disabled for now:
      
      * SMP support must be turned off because of conflicting symbols.
        Marc Zyngier has proposed a solution by adding a new SOC
        operations structure to hold indirect function pointers
        for these, but that work is currently stalled
      
      * We turn on SPARSE_IRQ unconditionally, which is not supported
        on most platforms. Each of them is currently in a different
        state, but most are being worked on.
      
      * A common clock framework is in place since v3.4 but not yet
        being used. Work on this is on its way.
      
      * DEBUG_LL for early debugging is currently disabled.
      
      * THUMB2_KERNEL does not work with allyesconfig because the
        kernel gets too big
      
      [Rob Herring]: Rebased to not be dependent on the mass mach header rename.
      As a result, omap2plus, imx, mxs and ux500 are not converted. Highbank,
      picoxcell, mvebu, and socfpga are converted.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Jason Cooper <jason@lakedaemon.net>
      Cc: Andrew Lunn <andrew@lunn.ch>
      Acked-by: NJamie Iles <jamie@jamieiles.com>
      Cc: Dinh Nguyen <dinguyen@altera.com>
      387798b3
  21. 08 9月, 2012 1 次提交
  22. 07 9月, 2012 1 次提交
  23. 26 8月, 2012 1 次提交
  24. 14 9月, 2012 1 次提交
  25. 19 7月, 2012 1 次提交
  26. 10 7月, 2012 1 次提交
  27. 04 6月, 2012 1 次提交
    • V
      ARM: 7420/1: Improve build environment isolation · bcccc50c
      Vincent Sanders 提交于
      Increasingly distributions are setting default build environments to
      have LDFLAGS with hardening options. There seems to be an assumption
      with those options that LDFLAGS are passed to the compiler frontend
      rather than used directly with ld (which the kernel build process
      assumes)
      
      To prevent build failures in such environments this patch changes the
      ARM architecture Makefile to override the LDFLAGS from the environment
      similar to the behaviour on other common architectures e.g. x86
      Signed-off-by: NVincent Sanders <vince@collabora.co.uk>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      bcccc50c
  28. 14 5月, 2012 1 次提交
  29. 13 5月, 2012 1 次提交
  30. 08 5月, 2012 1 次提交
  31. 05 5月, 2012 2 次提交
  32. 06 4月, 2012 1 次提交
    • R
      ARM: remove ixp23xx and ixp2000 platforms · c65f2abf
      Rob Herring 提交于
      ixp2xxx platforms have had no real changes since ~2006 and the maintainer
      has said on irc that they can be removed:
      
      13:05 < nico> do you still care about ixp2000?
      13:22 < lennert> not really, no
      13:58 < nico> do you think we could remove it from the kernel tree?
      14:01 < lennert> go for it, and remove ixp23xx too while you're at it
      
      Removing will help simplify ARM consolidation in general and PCI re-work
      specifically.
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      Cc: Randy Dunlap <rdunlap@xenotime.net>
      Acked-by: NLennert Buytenhek <buytenh@wantstofly.org>
      c65f2abf
  33. 24 3月, 2012 1 次提交
  34. 14 3月, 2012 1 次提交
  35. 06 3月, 2012 1 次提交
  36. 03 3月, 2012 3 次提交