1. 20 2月, 2014 1 次提交
    • J
      kbuild: dtbs_install: new make target · f4d4ffc0
      Jason Cooper 提交于
      Unlike other build products in the Linux kernel, there is no 'make
      *install' mechanism to put devicetree blobs in a standard place.
      
      This commit adds a new 'dtbs_install' make target which copies all of
      the dtbs into the INSTALL_DTBS_PATH directory. INSTALL_DTBS_PATH can be
      set before calling make to change the default install directory. If not
      set then it defaults to:
      
      	$INSTALL_PATH/dtbs/$KERNELRELEASE.
      
      This is done to keep dtbs from different kernel versions separate until
      things have settled down.  Once the dtbs are stable, and not so strongly
      linked to the kernel version, the devicetree files will most likely move
      to their own repo.  Users will need to upgrade install scripts at that
      time.
      
      v7: (reworked by Grant Likely)
      - Moved rules from arch/arm/Makefile to arch/arm/boot/dts/Makefile so
        that each dtb install could have a separate target and be reported as
        part of the make output.
      - Fixed dependency problem to ensure $KERNELRELEASE is calculated before
        attempting to install
      - Removed option to call external script. Copying the files should be
        sufficient and a build system can post-process the install directory.
        Despite the fact an external script is used for installing the kernel,
        I don't think that is a pattern that should be encouraged. I would
        rather see buildroot type tools post process the install directory to
        rename or move dtb files after installing to a staging directory.
        - Plus it is easy to add a hook after the fact without blocking the
          rest of this feature.
      - Move the helper targets into scripts/Makefile.lib with the rest of the
        common dtb rules
      Signed-off-by: NJason Cooper <jason@lakedaemon.net>
      Signed-off-by: NGrant Likely <grant.likely@linaro.org>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Rob Herring <robh+dt@kernel.org>
      f4d4ffc0
  2. 29 1月, 2014 1 次提交
  3. 23 12月, 2013 1 次提交
  4. 21 12月, 2013 1 次提交
  5. 20 12月, 2013 1 次提交
    • K
      stackprotector: Unify the HAVE_CC_STACKPROTECTOR logic between architectures · 19952a92
      Kees Cook 提交于
      Instead of duplicating the CC_STACKPROTECTOR Kconfig and
      Makefile logic in each architecture, switch to using
      HAVE_CC_STACKPROTECTOR and keep everything in one place. This
      retains the x86-specific bug verification scripts.
      Signed-off-by: NKees Cook <keescook@chromium.org>
      Cc: Arjan van de Ven <arjan@linux.intel.com>
      Cc: Michal Marek <mmarek@suse.cz>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: James Hogan <james.hogan@imgtec.com>
      Cc: Stephen Rothwell <sfr@canb.auug.org.au>
      Cc: Shawn Guo <shawn.guo@linaro.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-mips@linux-mips.org
      Cc: linux-arch@vger.kernel.org
      Link: http://lkml.kernel.org/r/1387481759-14535-2-git-send-email-keescook@chromium.orgSigned-off-by: NIngo Molnar <mingo@kernel.org>
      19952a92
  6. 18 12月, 2013 1 次提交
  7. 17 12月, 2013 1 次提交
  8. 14 12月, 2013 1 次提交
  9. 13 12月, 2013 1 次提交
  10. 10 12月, 2013 1 次提交
  11. 20 10月, 2013 1 次提交
  12. 03 10月, 2013 1 次提交
    • R
      arm, kbuild: make "make install" not depend on vmlinux · 19514fc6
      Robert Richter 提交于
      Install targets (install, zinstall, uinstall) on arm have a dependency
      to vmlinux. This may cause parts of the kernel to be rebuilt during
      installation. We must avoid this since this may run as root. Install
      targets "ABSOLUTELY MUST NOT MODIFY THE SOURCE TREE." as Linus
      emphasized this in:
      
       http://lkml.org/lkml/2013/7/10/600
      
      So on arm and maybe other archs we need the same as for x86:
      
       1648e4f8 x86, kbuild: make "make install" not depend on vmlinux
      
      This patch fixes this for arm. Dependencies are removed and instead a
      check to install.sh is added for the files that are needed.
      
      This issue was uncovered by this build error where the -j option is
      used in conjunction with install targets:
      
       $ make <makeflags>
       $ make <makeflags> zinstall
       ...
         DEPMOD
       Usage: .../scripts/depmod.sh /sbin/depmod <kernelrelease>
      
      (INSTALL_MOD_PATH and INSTALL_PATH variables set, so no root perms
      required in this case.)
      
      The problem is that zinstall on arm due to its dependency to vmlinux
      does a prepare/prepare3 and finally does a forced rewrite of
      kernel.release even if it exists already.
      
      Rebuilding kernel.release removes it first and then recreates it. This
      might race with another parallel make job running depmod.
      
      So this patch should fix this one too.
      
      Also quoting $(KERNELRELEASE) arg for install.sh as this messes
      argument order in case it is empty (which is the case if the kernel
      was not built yet).
      Signed-off-by: NRobert Richter <robert.richter@linaro.org>
      Signed-off-by: NRobert Richter <rric@kernel.org>
      Acked-by: Michal Marek <mmarek@suse.cz>.
      Acked-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: N"Yann E. MORIN" <yann.morin.1998@free.fr>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      19514fc6
  13. 17 9月, 2013 1 次提交
    • L
      ARM: delete mach-shark · 136dfa5e
      Linus Walleij 提交于
      The Shark machine sub-architecture (also known as DNARD, the
      DIGITAL Network Appliance Reference Design) lacks a maintainer
      able to apply and test patches to modernize the architecture.
      
      It is suspected that the current kernel, while it compiles,
      does not even boot on this machine. The listed maintainer has
      expressed that he will not be able to spend any time on the
      maintenance for the coming year.
      
      So let's delete it from the kernel for now. It can always be
      resurrected with git revert if maintenance is resumed.
      
      As the VIA82c505 PCI adapter was only used by this
      architecture, that gets deleted too.
      
      Cc: arm@kernel.org
      Cc: Alexander Schulz <alex@shark-linux.de>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      136dfa5e
  14. 27 7月, 2013 1 次提交
  15. 23 7月, 2013 1 次提交
  16. 29 6月, 2013 2 次提交
  17. 26 6月, 2013 1 次提交
  18. 22 6月, 2013 1 次提交
  19. 21 6月, 2013 1 次提交
  20. 20 6月, 2013 1 次提交
  21. 19 6月, 2013 1 次提交
  22. 18 6月, 2013 1 次提交
    • S
      ARM: keystone: Add minimal TI Keystone platform support · 828989ad
      Santosh Shilimkar 提交于
      Texas Instruments Keystone family of multi-core devices are
      based on ARM Cortex A15. Patch adds basic definitions for a
      new Keystone sub-architecture in ARM.
      
      The TCI66xxK2H Communications Infrastructure Keystone SoCs
      are member of the C66x family based on TI's new KeyStone 2
      multi-core SoC Architecture designed specifically for high
      performance wireless and networking infrastructure applications.
      The SOCs contains many subsystems like Cortex A15 ARM CorePacs,
      C66XX DSP CorePacs, MSMC memory controller, Tera Net bus,
      IP Network, Navigator, Hyperlink, 1G/10G Ethernet, Radio layers
      and queue based communication systems.
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: arm@kernel.org
      Acked-by: NOlof Johansson <olof@lixom.net>
      Signed-off-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      828989ad
  23. 07 5月, 2013 1 次提交
  24. 18 4月, 2013 1 次提交
  25. 20 3月, 2013 1 次提交
  26. 13 3月, 2013 1 次提交
  27. 04 2月, 2013 1 次提交
  28. 02 2月, 2013 1 次提交
  29. 24 1月, 2013 1 次提交
  30. 22 1月, 2013 2 次提交
  31. 07 12月, 2012 1 次提交
  32. 04 12月, 2012 1 次提交
  33. 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
  34. 17 11月, 2012 1 次提交
  35. 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
  36. 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
  37. 15 10月, 2012 1 次提交
  38. 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