1. 25 7月, 2015 1 次提交
  2. 04 6月, 2015 4 次提交
  3. 03 6月, 2015 1 次提交
  4. 02 6月, 2015 4 次提交
  5. 28 5月, 2015 1 次提交
    • T
      ARM: OMAP3: Fix booting with thumb2 kernel · d8a50941
      Tony Lindgren 提交于
      We get a NULL pointer dereference on omap3 for thumb2 compiled kernels:
      
      Internal error: Oops: 80000005 [#1] SMP THUMB2
      ...
      [<c046497b>] (_raw_spin_unlock_irqrestore) from [<c0024375>]
      (omap3_enter_idle_bm+0xc5/0x178)
      [<c0024375>] (omap3_enter_idle_bm) from [<c0374e63>]
      (cpuidle_enter_state+0x77/0x27c)
      [<c0374e63>] (cpuidle_enter_state) from [<c00627f1>]
      (cpu_startup_entry+0x155/0x23c)
      [<c00627f1>] (cpu_startup_entry) from [<c06b9a47>]
      (start_kernel+0x32f/0x338)
      [<c06b9a47>] (start_kernel) from [<8000807f>] (0x8000807f)
      
      The power management related assembly on omaps needs to interact with
      ARM mode bootrom code, so we need to keep most of the related assembly
      in ARM mode.
      
      Turns out this error is because of missing ENDPROC for assembly code
      as suggested by Stephen Boyd <sboyd@codeaurora.org>. Let's fix the
      problem by adding ENDPROC in two places to sleep34xx.S.
      
      Let's also remove the now duplicate custom code for mode switching.
      This has been unnecessary since commit 6ebbf2ce ("ARM: convert
      all "mov.* pc, reg" to "bx reg" for ARMv6+").
      
      And let's also remove the comments about local variables, they are
      now just confusing after the ENDPROC.
      
      The reason why ENDPROC makes a difference is it sets .type and then
      the compiler knows what to do with the thumb bit as explained at:
      
      https://wiki.ubuntu.com/ARM/Thumb2PortingHowtoReported-by: NKevin Hilman <khilman@kernel.org>
      Tested-by: NKevin Hilman <khilman@linaro.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      d8a50941
  6. 21 5月, 2015 5 次提交
  7. 14 5月, 2015 1 次提交
  8. 13 5月, 2015 1 次提交
  9. 12 5月, 2015 1 次提交
    • T
      ARM: OMAP2+: Remove bogus struct clk comparison for timer clock · b0897972
      Tony Lindgren 提交于
      With recent changes to use determine_rate, the comparison of two
      clocks won't work without clk_is_match that does __clk_get_hw
      on the clocks first.
      
      As we've been unconditionally already calling clk_set_parent
      already because of the bogus comparison, let's just remove the
      check as suggested by Stephen Boyd <sboyd@codeaurora.org>.
      
      Cc: Michael Turquette <mturquette@linaro.org>
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>
      Acked-by: NStephen Boyd <sboyd@codeaurora.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b0897972
  10. 09 5月, 2015 3 次提交
  11. 07 5月, 2015 1 次提交
    • T
      ARM: OMAP2+: Remove legacy booting support for Beagleboards · d203c574
      Tony Lindgren 提交于
      We've been moving all omap2+ based systems to boot in device tree only
      mode for a few years now. Only omap3 has legacy booting support
      remaining. Most omap3 boards already have related arch/arm/boot/*.dts*
      files for booting with device tree.
          
      This board has support for device tree based booting, and we've been
      printing warnings about the legacy booting being deprecated for a
      few merge cycles now. Let's attempt to remove the legacy booting
      for it.
      
      The reason for removing the legacy booting support now rather than
      later is we can simply revert this patch if necessary if we run
      into some unexpected issues that are not trivial to fix for the
      device tree based booting.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      d203c574
  12. 06 5月, 2015 2 次提交
  13. 05 5月, 2015 2 次提交
    • T
      ARM: OMAP2+: Remove legacy booting support for Overo · 71115b30
      Tony Lindgren 提交于
      We've been moving all omap2+ based systems to boot in device tree only
      mode for a few years now. Only omap3 has legacy booting support
      remaining. Most omap3 boards already have related arch/arm/boot/*.dts*
      files for booting with device tree.
      
      This board has support for device tree based booting, and we've been
      printing warnings about the legacy booting being deprecated for a
      few merge cycles now. Let's attempt to remove the legacy booting
      for it.
      
      The reason for removing the legacy booting support now rather than
      later is we can simply revert this patch if necessary if we run
      into some unexpected issues that are not trivial to fix for the
      device tree based booting.
      
      Cc: Florian Vaussard <florian.vaussard@epfl.ch>
      Acked-by: NAsh Charles <ashcharles@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      71115b30
    • T
      ARM: OMAP2+: Remove legacy booting support for cm-t35 · 11cd7b8c
      Tony Lindgren 提交于
      We've been moving all omap2+ based systems to boot in device tree only
      mode for a few years now. Only omap3 has legacy booting support
      remaining. Most omap3 boards already have related arch/arm/boot/*.dts*
      files for booting with device tree.
      
      This board has support for device tree based booting, and we've been
      printing warnings about the legacy booting being deprecated for a
      few merge cycles now. Let's attempt to remove the legacy booting
      for it.
      
      The reason for removing the legacy booting support now rather than
      later is we can simply revert this patch if necessary if we run
      into some unexpected issues that are not trivial to fix for the
      device tree based booting.
      
      Cc: Dmitry Lifshitz <lifshitz@compulab.co.il>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      11cd7b8c
  14. 04 5月, 2015 1 次提交
    • T
      ARM: OMAP2+: Fix omap off idle power consumption creeping up · 102bcb6e
      Tony Lindgren 提交于
      If we use a combination of VMODE and I2C4 for retention modes,
      eventually the off idle power consumption will creep up by about
      23mW, even during off mode with I2C4 always staying enabled.
      
      Turns out this is because of erratum i531 "Extra Power Consumed
      When Repeated Start Operation Mode Is Enabled on I2C Interface
      Dedicated for Smart Reflex (I2C4)" as pointed out by Nishanth
      Menon <nm@ti.com>.
      
      Let's fix the issue by adding i2c_cfg_clear_mask for the bits
      to clear when initializing the I2C4 adapter so we can clear
      SREN bit that drives the I2C4 lines low otherwise when there
      is no traffic.
      
      Fixes: 3b8c4ebb ("ARM: OMAP3: Fix idle mode signaling for
      Cc: stable@vger.kernel.org # v3.16+
      sys_clkreq and sys_off_mode")
      Cc: Kevin Hilman <khilman@kernel.org>
      Cc: Tero Kristo <t-kristo@ti.com>
      Reviewed-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      102bcb6e
  15. 02 5月, 2015 1 次提交
  16. 21 4月, 2015 1 次提交
  17. 03 4月, 2015 5 次提交
  18. 01 4月, 2015 5 次提交