1. 02 4月, 2011 1 次提交
  2. 29 3月, 2011 9 次提交
    • T
      arm: Fold irq_set_chip/irq_set_handler · f38c02f3
      Thomas Gleixner 提交于
      Use irq_set_chip_and_handler() instead. Converted with coccinelle.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      f38c02f3
    • T
      arm: Cleanup the irq namespace · 6845664a
      Thomas Gleixner 提交于
      Convert to the new function names. Automated with coccinelle.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      6845664a
    • T
      arm: Use generic show_interrupts() · 25a5662a
      Thomas Gleixner 提交于
      Use the generic version and just keep the arch specific output.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      25a5662a
    • T
      arm: Use irq flag setter function · 1b7a2d90
      Thomas Gleixner 提交于
      Use the proper accessor function instead of fiddling in the status
      bits directly.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Cc: linux-arm-kernel@lists.infradead.org
      1b7a2d90
    • T
      arm: bios32: Remove non exisiting machine code · 11f2cde1
      Thomas Gleixner 提交于
      The id removal left this machine check in which breaks the build on
      some platforms. Remove it.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      11f2cde1
    • S
      ARM: 6826/1: Merge v6 and v7 DEBUG_LL DCC support · dfad549d
      Stephen Boyd 提交于
      The inline assembly differences for v6 vs. v7 are purely
      optimizations. On a v7 processor, an mrc with the pc sets the
      condition codes to the 28-31 bits of the register being read. It
      just so happens that the TX/RX full bits the DCC support code is
      testing for are high enough in the register to be put into the
      condition codes. On a v6 processor, this "feature" isn't
      implemented and thus we have to do the usual read, mask, test
      operations to check for TX/RX full. Thus, we can drop the v7
      implementation and just use the v6 implementation for both.
      
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      dfad549d
    • M
      ARM: 6838/1: etm: fix section mismatch warning · 8e880699
      Ming Lei 提交于
      The patch fixes the warning below:
      
      WARNING: arch/arm/kernel/built-in.o(.data+0x27c): Section mismatch in reference from the variable etb_driver to the function .init.text:etb_probe()
      The variable etb_driver references
      the function __init etb_probe()
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      
      WARNING: arch/arm/kernel/built-in.o(.data+0x2cc): Section mismatch in reference from the variable etm_driver to the function .init.text:etm_probe()
      The variable etm_driver references
      the function __init etm_probe()
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      Signed-off-by: NMing Lei <tom.leiming@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      8e880699
    • C
      ARM: 6837/1: remove unused pci_fixup_prpmc1100 · 7f479c64
      Colin Cross 提交于
      The PrPMC1100 machine was removed in 2.6.11, but left a reference to machine_is_prpmc1100 in arch/arm/kernel/bios32.c.  6f82f4db removed the machine type, which causes a build failure:
      
      CC      arch/arm/kernel/bios32.o
      arch/arm/kernel/bios32.c: In function 'pci_fixup_prpmc1100':
      arch/arm/kernel/bios32.c:174: error: implicit declaration of function 'machine_is_prpmc1100'
      
      Remove the unused pci_fixup_prpcm1100.
      Signed-off-by: NColin Cross <ccross@android.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      7f479c64
    • V
      ARM: 6836/1: kprobes/fix emulation of LDR/STR instruction when Rn == PC · 0652f067
      Viktor Rosendahl 提交于
      The Rn value from the emulation is unconditionally written back;
      this is fine as long as Rn != PC because in that case, even if the
      instruction isn't a write back instruction, it will only result in the
      same value being written back.
      
      In case Rn == PC, then the emulated instruction doesn't have the
      actual PC value in Rn but an adjusted value; when this is written
      back, it will result in the PC being incorrectly updated.
      
      An altenative solution would be to check bits 24 and 22 to see whether
      the instruction actually is a write back instruction or not. I think
      it's enough to check whether Rn != PC,  because:
      - it's looks cheaper than the alternative
      - to my understaning it's not permitted to update the PC with a write
      back instruction, so we don't lose any ability to emulate legal
      instructions.
      - in case of writing back for non write back instructions where Rn != PC, it doesn't matter because the values are the same.
      
      Regarding the second point above, it would possibly be prudent to add
      some checking to prep_emulate_ldr_str(), so that instructions with
      both write back and Rn == PC would be rejected.
      Signed-off-by: NViktor Rosendahl <viktor.rosendahl@nokia.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      0652f067
  3. 26 3月, 2011 4 次提交
  4. 24 3月, 2011 1 次提交
    • O
      crash_dump: export is_kdump_kernel to modules, consolidate elfcorehdr_addr,... · 93a72052
      Olaf Hering 提交于
      crash_dump: export is_kdump_kernel to modules, consolidate elfcorehdr_addr, setup_elfcorehdr and saved_max_pfn
      
      The Xen PV drivers in a crashed HVM guest can not connect to the dom0
      backend drivers because both frontend and backend drivers are still in
      connected state.  To run the connection reset function only in case of a
      crashdump, the is_kdump_kernel() function needs to be available for the PV
      driver modules.
      
      Consolidate elfcorehdr_addr, setup_elfcorehdr and saved_max_pfn into
      kernel/crash_dump.c Also export elfcorehdr_addr to make is_kdump_kernel()
      usable for modules.
      
      Leave 'elfcorehdr' as early_param().  This changes powerpc from __setup()
      to early_param().  It adds an address range check from x86 also on ia64
      and powerpc.
      
      [akpm@linux-foundation.org: additional #includes]
      [akpm@linux-foundation.org: remove elfcorehdr_addr export]
      [akpm@linux-foundation.org: fix for Tejun's mm/nobootmem.c changes]
      Signed-off-by: NOlaf Hering <olaf@aepfle.de>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: "H. Peter Anvin" <hpa@zytor.com>
      Cc: Johannes Weiner <hannes@cmpxchg.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      93a72052
  5. 11 3月, 2011 1 次提交
  6. 10 3月, 2011 1 次提交
  7. 04 3月, 2011 1 次提交
  8. 26 2月, 2011 2 次提交
  9. 24 2月, 2011 10 次提交
  10. 23 2月, 2011 2 次提交
  11. 22 2月, 2011 5 次提交
  12. 19 2月, 2011 2 次提交
  13. 18 2月, 2011 1 次提交