1. 26 4月, 2014 6 次提交
    • S
      ARM: dts: AM3517: Disable absent IPs inherited from OMAP3 · 4c051603
      Suman Anna 提交于
      AM3517 inherits OMAP3 dts file, but does not have all the IPs
      that are present on OMAP3. This patch disables the following
      absent IPs for AM3517: Mailbox, IVA, MMU_ISP, MPU_IVA SmartReflex.
      
      A label had to be added for IVA node in omap3.dtsi to be able to
      get a reference to the node for disabling.
      
      Otherwise we get the following warnings during booting:
      platform iva.2: Cannot lookup hwmod 'iva'
      platform 48094000.mailbox: Cannot lookup hwmod 'mailbox'
      platform 480bd400.mmu: Cannot lookup hwmod 'mmu_isp'
      platform 480c9000.smartreflex: Cannot lookup hwmod 'smartreflex_mpu_iva'
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      [tony@atomide.com: updated description for the warnings]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      4c051603
    • S
      ARM: dts: OMAP2: Fix interrupts for OMAP2420 mailbox · 4fe5bd5d
      Suman Anna 提交于
      The mailbox module is capable of generating two interrupts
      to MPU in OMAP2420, compared to one in OMAP2430. The second
      interrupt is to handle interrupts from the additional IVA
      processor present only on OMAP2420.
      
      Move the current common mailbox DT node into the SoC
      specific files to allow the above differentiation. Also,
      added back the interrupt-names on OMAP2420, that were
      previously defined in hwmod data.
      
      This fixes regression caused by the recent dropping of
      hwmod data in favor for defining it in the .dts files.
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      [tony@atomide.com: updated description]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      4fe5bd5d
    • S
      ARM: dts: OMAP5: Add mailbox dt node to fix boot warning · 84d89c31
      Suman Anna 提交于
      Add the mailbox device DT node for OMAP5 SoC. The OMAP5 mailbox
      IP is identical to that used in OMAP4.
      
      The OMAP5 hwmod data no longer publishes the module address space,
      so this patch fixes the WARN_ON backtrace associated with the
      following trace during the kernel boot:
      "omap_hwmod: mailbox: doesn't have mpu register target base".
      
      Otherwise we get a warning like this:
      
      WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2538 _init+0x1c0/0x3dc()
      omap_hwmod: mailbox: doesn't have mpu register target base
      Modules linked in:
      CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.15.0-rc2-00001-gb5e85a0 #45
      [<c0015724>] (unwind_backtrace) from [<c00120f4>] (show_stack+0x10/0x14)
      [<c00120f4>] (show_stack) from [<c05a1ccc>] (dump_stack+0x78/0x94)
      [<c05a1ccc>] (dump_stack) from [<c0042a74>] (warn_slowpath_common+0x6c/0x8c)
      [<c0042a74>] (warn_slowpath_common) from [<c0042b28>] (warn_slowpath_fmt+0x30/0x40)
      [<c0042b28>] (warn_slowpath_fmt) from [<c0803b40>] (_init+0x1c0/0x3dc)
      [<c0803b40>] (_init) from [<c0029c8c>] (omap_hwmod_for_each+0x34/0x5c)
      [<c0029c8c>] (omap_hwmod_for_each) from [<c08042b0>] (__omap_hwmod_setup_all+0x24/0x40)
      [<c08042b0>] (__omap_hwmod_setup_all) from [<c00088b8>] (do_one_initcall+0x34/0x160)
      [<c00088b8>] (do_one_initcall) from [<c07f7bf4>] (kernel_init_freeable+0xfc/0x1c8)
      [<c07f7bf4>] (kernel_init_freeable) from [<c059c4f4>] (kernel_init+0x8/0xe4)
      [<c059c4f4>] (kernel_init) from [<c000eaa8>] (ret_from_fork+0x14/0x2c)
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      [tony@atomide.com: updated description to for the warning]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      84d89c31
    • J
      ARM: OMAP5: Switch to THUMB mode if needed on secondary CPU · da0159fd
      Joel Fernandes 提交于
      On my DRA7 system, when the kernel is built in Thumb-2 mode, the secondary CPU
      (Cortex A15) fails to come up causing SMP boot on second CPU to timeout. This
      seems to be because the CPU is in ARM mode once the ROM hands over control to
      the kernel.  Switch to Thumb-2 mode if required once the kernel is control of
      secondary CPU. On OMAP4 on the other hand, it appears to be in Thumb-2 mode on
      entry so this is not required and SMP boot works as is.
      
      Also corrected a spurious '+' and updated copyright information.
      
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Nishanth Menon <nm@ti.com>
      Tested-by: NNishanth Menon <nm@ti.com>
      Acked-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: NJoel Fernandes <joelf@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      da0159fd
    • D
      ARM: dts: am437x-gp-evm: Do not reset gpio5 · 1ff3859e
      Dave Gerlach 提交于
      Do not reset GPIO5 at boot-up because GPIO5_7 is used
      on AM437x GP-EVM to control VTT regulators on DDR3.
      Without this some GP-EVM boards will fail to boot because
      of DDR3 corruption.
      Reported-by: NNishanth Menon <nm@ti.com>
      Tested-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NDave Gerlach <d-gerlach@ti.com>
      Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      1ff3859e
    • J
      ARM: dts: omap3-igep0020: use SMSC9221 timings · ef139e13
      Javier Martinez Canillas 提交于
      The IGEPv2 board has a SMSC LAN9221i ethernet chip and not a
      SMSC LAN911x connected to the GPMC. Each chip needs different
      timings in order to operate correctly so is wrong to include
      omap-gpmc-smsc911x.dtsi instead of omap-gpmc-smsc9221.dtsi.
      Signed-off-by: NJavier Martinez Canillas <javier.martinez@collabora.co.uk>
      [tony@atomide.com: this is needed to avoid potential memory corruption]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      ef139e13
  2. 25 4月, 2014 1 次提交
  3. 24 4月, 2014 11 次提交
  4. 22 4月, 2014 3 次提交
  5. 19 4月, 2014 16 次提交
  6. 18 4月, 2014 1 次提交
  7. 17 4月, 2014 2 次提交
    • M
      kprobes/x86: Fix page-fault handling logic · 6381c24c
      Masami Hiramatsu 提交于
      Current kprobes in-kernel page fault handler doesn't
      expect that its single-stepping can be interrupted by
      an NMI handler which may cause a page fault(e.g. perf
      with callback tracing).
      
      In that case, the page-fault handled by kprobes and it
      misunderstands the page-fault has been caused by the
      single-stepping code and tries to recover IP address
      to probed address.
      
      But the truth is the page-fault has been caused by the
      NMI handler, and do_page_fault failes to handle real
      page fault because the IP address is modified and
      causes Kernel BUGs like below.
      
       ----
       [ 2264.726905] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
       [ 2264.727190] IP: [<ffffffff813c46e0>] copy_user_generic_string+0x0/0x40
      
      To handle this correctly, I fixed the kprobes fault
      handler to ensure the faulted ip address is its own
      single-step buffer instead of checking current kprobe
      state.
      Signed-off-by: NMasami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
      Cc: Andi Kleen <andi@firstfloor.org>
      Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
      Cc: Sandeepa Prabhu <sandeepa.prabhu@linaro.org>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Cc: fche@redhat.com
      Cc: systemtap@sourceware.org
      Link: http://lkml.kernel.org/r/20140417081644.26341.52351.stgit@ltc230.yrl.intra.hitachi.co.jpSigned-off-by: NIngo Molnar <mingo@kernel.org>
      6381c24c
    • I
      x86/mce: Fix CMCI preemption bugs · ea431643
      Ingo Molnar 提交于
      The following commit:
      
        27f6c573 ("x86, CMCI: Add proper detection of end of CMCI storms")
      
      Added two preemption bugs:
      
       - machine_check_poll() does a get_cpu_var() without a matching
         put_cpu_var(), which causes preemption imbalance and crashes upon
         bootup.
      
       - it does percpu ops without disabling preemption. Preemption is not
         disabled due to the mistaken use of a raw spinlock.
      
      To fix these bugs fix the imbalance and change
      cmci_discover_lock to a regular spinlock.
      Reported-by: NOwen Kibel <qmewlo@gmail.com>
      Reported-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NIngo Molnar <mingo@kernel.org>
      Cc: Chen, Gong <gong.chen@linux.intel.com>
      Cc: Josh Boyer <jwboyer@fedoraproject.org>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Alexander Todorov <atodorov@redhat.com>
      Cc: Borislav Petkov <bp@alien8.de>
      Link: http://lkml.kernel.org/n/tip-jtjptvgigpfkpvtQxpEk1at2@git.kernel.orgSigned-off-by: NIngo Molnar <mingo@kernel.org>
      --
       arch/x86/kernel/cpu/mcheck/mce.c       |    4 +---
       arch/x86/kernel/cpu/mcheck/mce_intel.c |   18 +++++++++---------
       2 files changed, 10 insertions(+), 12 deletions(-)
      ea431643