An error occurred fetching the project authors.
  1. 17 Apr, 2013 1 commit
  2. 26 Mar, 2013 1 commit
  3. 31 Jan, 2013 1 commit
  4. 10 Jan, 2013 1 commit
    • Will Deacon's avatar
      ARM: virt: hide CONFIG_ARM_VIRT_EXT from user · 651134b0
      Will Deacon authored
      ARM_VIRT_EXT is a property of CPU_V7, but does not adversely affect
      other CPUs that can be built into the same kernel image (i.e. ARMv6+).
      
      This patch defaults ARM_VIRT_EXT to y if CPU_V7, allowing hypervisors
      such as KVM to make better use of the option and being able to rely
      on hyp-mode boot support.
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      651134b0
  5. 21 Nov, 2012 1 commit
  6. 13 Oct, 2012 1 commit
    • Russell King's avatar
      ARM: config: sort select statements alphanumerically · b1b3f49c
      Russell King authored
      As suggested by Andrew Morton:
      
        This is a pet peeve of mine.  Any time there's a long list of items
        (header file inclusions, kconfig entries, array initalisers, etc) and
        someone wants to add a new item, they *always* go and stick it at the
        end of the list.
      
        Guys, don't do this.  Either put the new item into a randomly-chosen
        position or, probably better, alphanumerically sort the list.
      
      lets sort all our select statements alphanumerically.  This commit was
      created by the following perl:
      
      while (<>) {
      	while (/\\\s*$/) {
      		$_ .= <>;
      	}
      	undef %selects if /^\s*config\s+/;
      	if (/^\s+select\s+(\w+).*/) {
      		if (defined($selects{$1})) {
      			if ($selects{$1} eq $_) {
      				print STDERR "Warning: removing duplicated $1 entry\n";
      			} else {
      				print STDERR "Error: $1 differently selected\n".
      					"\tOld: $selects{$1}\n".
      					"\tNew: $_\n";
      				exit 1;
      			}
      		}
      		$selects{$1} = $_;
      		next;
      	}
      	if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
      			  /^endif/ or /^endchoice/)) {
      		foreach $k (sort (keys %selects)) {
      			print "$selects{$k}";
      		}
      		undef %selects;
      	}
      	print;
      }
      if (%selects) {
      	foreach $k (sort (keys %selects)) {
      		print "$selects{$k}";
      	}
      }
      
      It found two duplicates:
      
      Warning: removing duplicated S5P_SETUP_MIPIPHY entry
      Warning: removing duplicated HARDIRQS_SW_RESEND entry
      
      and they are identical duplicates, hence the shrinkage in the diffstat
      of two lines.
      
      We have four testers reporting success of this change (Tony, Stephen,
      Linus and Sekhar.)
      Acked-by: default avatarJason Cooper <jason@lakedaemon.net>
      Acked-by: default avatarTony Lindgren <tony@atomide.com>
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Acked-by: default avatarSekhar Nori <nsekhar@ti.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      b1b3f49c
  7. 19 Sep, 2012 1 commit
  8. 05 May, 2012 1 commit
  9. 13 Apr, 2012 1 commit
  10. 15 Feb, 2012 1 commit
  11. 23 Jan, 2012 1 commit
    • Will Deacon's avatar
      ARM: 7291/1: cache: assume 64-byte L1 cachelines for ARMv7 CPUs · a092f2b1
      Will Deacon authored
      To ensure correct alignment of cacheline-aligned data, the maximum
      cacheline size needs to be known at compile time.
      
      Since Cortex-A8 and Cortex-A15 have 64-byte cachelines (and it is likely
      that there will be future ARMv7 implementations with the same line size)
      then it makes sense to assume that CPU_V7 implies a 64-byte L1 cacheline
      size. For CPUs with smaller caches, this will result in some harmless
      padding but will help with single zImage work and avoid hitting subtle
      bugs with misaligned data structures.
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      a092f2b1
  12. 19 Dec, 2011 1 commit
  13. 08 Dec, 2011 1 commit
  14. 31 Oct, 2011 3 commits
  15. 08 Jul, 2011 1 commit
  16. 07 Jul, 2011 1 commit
    • Anton Vorontsov's avatar
      ARM: cns3xxx: Add support for L2 Cache Controller · 93e85d8e
      Anton Vorontsov authored
      CNS3xxx SOCs have L310-compatible cache controller, so let's use it.
      
      With this patch benchmarking with 'gzip' shows that performance is
      doubled, and I'm still able to boot full-fledged userland over NFS
      (using PCIe NIC), so the support should be pretty robust.
      
      p.s. While CNS3xxx reports that it has PL310, it still needs to wait
      on cache line operations, so we should not select 'CACHE_PL310',
      which is a micro-optimization that removes these waits for v7 CPUs.
      Someday we'd better rename CACHE_PL310 Kconfig option into
      NO_CACHE_WAIT or something less ambiguous.
      Signed-off-by: default avatarAnton Vorontsov <avorontsov@mvista.com>
      93e85d8e
  17. 20 Jun, 2011 1 commit
    • John Linn's avatar
      ARM: Xilinx: Adding Xilinx board support · b85a3ef4
      John Linn authored
      The 1st board support is minimal to get a system up and running
      on the Xilinx platform.
      
      This platform reuses the clock implementation from plat-versatile, and
      it depends entirely on CONFIG_OF support.  There is only one board
      support file which obtains all device information from a device tree
      dtb file which is passed to the kernel at boot time.
      Signed-off-by: default avatarJohn Linn <john.linn@xilinx.com>
      b85a3ef4
  18. 07 Mar, 2011 1 commit
  19. 23 Feb, 2011 1 commit
  20. 22 Feb, 2011 1 commit
  21. 10 Feb, 2011 1 commit
  22. 09 Feb, 2011 1 commit
    • Russell King's avatar
      ARM: Avoid building unsafe kernels on OMAP2 and MX3 · 15490ef8
      Russell King authored
      OMAP2 (armv6) and MX3 turn off support for the V6K instructions, which
      when they include support for SMP kernels means that the resulting
      kernel is unsafe on SMP and can result in corrupted filesystems as we
      end up using unsafe bitops.
      
      Re-enable the use of V6K instructions on such kernels, and let such
      kernels running on V6 CPUs eat undefined instruction faults which will
      be much safer than filesystem corruption.  Next merge window we can fix
      this properly (as it requires a much bigger set of changes.)
      Acked-by: default avatarTony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      15490ef8
  23. 02 Feb, 2011 6 commits
  24. 07 Jan, 2011 1 commit
  25. 18 Dec, 2010 2 commits
  26. 18 Nov, 2010 1 commit
    • Magnus Damm's avatar
      ARM: mach-shmobile: Initial AG5 and AG5EVM support · 6d9598e2
      Magnus Damm authored
      This patch adds initial support for Renesas SH-Mobile AG5.
      
      At this point the AG5 CPU support is limited to the ARM
      core, SCIF serial and a CMT timer together with L2 cache
      and the GIC. The AG5EVM board also supports Ethernet.
      
      Future patches will add support for GPIO, INTCS, CPGA
      and platform data / driver updates for devices such as
      IIC, LCDC, FSI, KEYSC, CEU and SDHI among others.
      
      The code in entry-macro.S will be cleaned up when the
      ARM IRQ demux code improvements have been merged.
      
      Depends on the AG5EVM mach-type recently registered but
      not yet present in arch/arm/tools/mach-types.
      
      As the AG5EVM board comes with 512MiB memory it is
      recommended to turn on HIGHMEM.
      
      Many thanks to Yoshii-san for initial bring up.
      Signed-off-by: default avatarMagnus Damm <damm@opensource.se>
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
      6d9598e2
  27. 04 Nov, 2010 2 commits
    • Leif Lindholm's avatar
      ARM: 6396/1: Add SWP/SWPB emulation for ARMv7 processors · 64d2dc38
      Leif Lindholm authored
      The SWP instruction was deprecated in the ARMv6 architecture,
      superseded by the LDREX/STREX family of instructions for
      load-linked/store-conditional operations. The ARMv7 multiprocessing
      extensions mandate that SWP/SWPB instructions are treated as undefined
      from reset, with the ability to enable them through the System Control
      Register SW bit.
      
      This patch adds the alternative solution to emulate the SWP and SWPB
      instructions using LDREX/STREX sequences, and log statistics to
      /proc/cpu/swp_emulation. To correctly deal with copy-on-write, it also
      modifies cpu_v7_set_pte_ext to change the mappings to priviliged RO when
      user RO.
      Signed-off-by: default avatarLeif Lindholm <leif.lindholm@arm.com>
      Acked-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      Acked-by: default avatarKirill A. Shutemov <kirill@shutemov.name>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      64d2dc38
    • Catalin Marinas's avatar
      ARM: 6384/1: Remove the domain switching on ARMv6k/v7 CPUs · 247055aa
      Catalin Marinas authored
      This patch removes the domain switching functionality via the set_fs and
      __switch_to functions on cores that have a TLS register.
      
      Currently, the ioremap and vmalloc areas share the same level 1 page
      tables and therefore have the same domain (DOMAIN_KERNEL). When the
      kernel domain is modified from Client to Manager (via the __set_fs or in
      the __switch_to function), the XN (eXecute Never) bit is overridden and
      newer CPUs can speculatively prefetch the ioremap'ed memory.
      
      Linux performs the kernel domain switching to allow user-specific
      functions (copy_to/from_user, get/put_user etc.) to access kernel
      memory. In order for these functions to work with the kernel domain set
      to Client, the patch modifies the LDRT/STRT and related instructions to
      the LDR/STR ones.
      
      The user pages access rights are also modified for kernel read-only
      access rather than read/write so that the copy-on-write mechanism still
      works. CPU_USE_DOMAINS gets disabled only if the hardware has a TLS register
      (CPU_32v6K is defined) since writing the TLS value to the high vectors page
      isn't possible.
      
      The user addresses passed to the kernel are checked by the access_ok()
      function so that they do not point to the kernel space.
      Tested-by: default avatarAnton Vorontsov <cbouatmailru@gmail.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarCatalin Marinas <catalin.marinas@arm.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      247055aa
  28. 26 Oct, 2010 1 commit
  29. 02 Sep, 2010 1 commit
  30. 05 Aug, 2010 2 commits