1. 29 Mar, 2011 1 commit
  2. 28 Mar, 2011 6 commits
    • Stephen Boyd's avatar
      ARM: 6826/1: Merge v6 and v7 DEBUG_LL DCC support · dfad549d
      Stephen Boyd authored
      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: default avatarStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      dfad549d
    • Ming Lei's avatar
      ARM: 6838/1: etm: fix section mismatch warning · 8e880699
      Ming Lei authored
      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: default avatarMing Lei <tom.leiming@gmail.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      8e880699
    • Colin Cross's avatar
      ARM: 6837/1: remove unused pci_fixup_prpmc1100 · 7f479c64
      Colin Cross authored
      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: default avatarColin Cross <ccross@android.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      7f479c64
    • Viktor Rosendahl's avatar
      ARM: 6836/1: kprobes/fix emulation of LDR/STR instruction when Rn == PC · 0652f067
      Viktor Rosendahl authored
      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: default avatarViktor Rosendahl <viktor.rosendahl@nokia.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      0652f067
    • Russell King's avatar
    • Russell King's avatar
  3. 27 Mar, 2011 1 commit
  4. 26 Mar, 2011 28 commits
  5. 25 Mar, 2011 4 commits