1. 05 5月, 2015 1 次提交
    • S
      bus: omap_l3_noc: Fix master id address decoding for OMAP5 · e7309c26
      Suman Anna 提交于
      The L3 Error handling on OMAP5 for the most part is very similar
      to that of OMAP4, and had leveraged common data structures and
      register layout definitions so far. Upon closer inspection, there
      are a few minor differences causing an incorrect decoding and
      reporting of the master NIU upon an error:
      
        1. The L3_TARG_STDERRLOG_MSTADDR.STDERRLOG_MSTADDR occupies
           11 bits on OMAP5 as against 8 bits on OMAP4, with the master
           NIU connID encoded in the 6 MSBs of the STDERRLOG_MSTADDR
           field.
        2. The CLK3 FlagMux component has 1 input source on OMAP4 and 3
           input sources on OMAP5. The common DEBUGSS source is at a
           different input on each SoC.
      
      Fix the above issues by using a OMAP5-specific compatible property
      and using SoC-specific data where there are differences.
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Acked-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      e7309c26
  2. 01 4月, 2015 1 次提交
  3. 15 3月, 2015 1 次提交
    • M
      ARM: omap: convert wakeupgen to stacked domains · 7136d457
      Marc Zyngier 提交于
      OMAP4/5 has been (ab)using the gic_arch_extn to provide
      wakeup from suspend, and it makes a lot of sense to convert
      this code to use stacked domains instead.
      
      This patch does just this, updating the DT files to actually
      reflect what the HW provides.
      
      BIG FAT WARNING: because the DTs were so far lying by not
      exposing the WUGEN HW block, kernels with this patch applied
      won't have any suspend-resume facility when booted with old DTs,
      and old kernels with updated DTs won't even boot.
      
      On a platform with this patch applied, the system looks like
      this:
      
      root@bacon-fat:~# cat /proc/interrupts
                  CPU0       CPU1
       16:          0          0     WUGEN  37  gp_timer
       19:     233799     155916       GIC  27  arch_timer
       23:          0          0     WUGEN   9  l3-dbg-irq
       24:          1          0     WUGEN  10  l3-app-irq
       27:        282          0     WUGEN  13  omap-dma-engine
       44:          0          0  4ae10000.gpio  13  DMA
      294:          0          0     WUGEN  20  gpmc
      297:        506          0     WUGEN  56  48070000.i2c
      298:          0          0     WUGEN  57  48072000.i2c
      299:          0          0     WUGEN  61  48060000.i2c
      300:          0          0     WUGEN  62  4807a000.i2c
      301:          8          0     WUGEN  60  4807c000.i2c
      308:       2439          0     WUGEN  74  OMAP UART2
      312:        362          0     WUGEN  83  mmc2
      313:        502          0     WUGEN  86  mmc0
      314:         13          0     WUGEN  94  mmc1
      350:          0          0      PRCM  pinctrl, pinctrl
      406:   35155709          0       GIC 109  ehci_hcd:usb1
      407:          0          0     WUGEN   7  palmas
      409:          0          0     WUGEN 119  twl6040
      410:          0          0   twl6040   5  twl6040_irq_ready
      411:          0          0   twl6040   0  twl6040_irq_th
      IPI0:          0          1  CPU wakeup interrupts
      IPI1:          0          0  Timer broadcast interrupts
      IPI2:      95334     902334  Rescheduling interrupts
      IPI3:          0          0  Function call interrupts
      IPI4:        479        648  Single function call interrupts
      IPI5:          0          0  CPU stop interrupts
      IPI6:          0          0  IRQ work interrupts
      IPI7:          0          0  completion interrupts
      Err:          0
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      Link: https://lkml.kernel.org/r/1426088629-15377-8-git-send-email-marc.zyngier@arm.comSigned-off-by: NJason Cooper <jason@lakedaemon.net>
      7136d457
  4. 07 3月, 2015 1 次提交
    • T
      ARM: dts: OMAP5: fix polling intervals for thermal zones · 38f5c8ba
      Tero Kristo 提交于
      OMAP4 has a finer counter granularity, which allows for a delay of 1000ms
      in the thermal zone polling intervals. OMAP5 has a different counter
      mechanism, which allows at maximum a 500ms timer. Adjust the cpu thermal
      zone polling interval accordingly.
      
      Without this patch, the polling interval information is simply ignored,
      and the following thermal warnings are printed during boot (assuming
      thermal is enabled);
      
      [    1.545343] ti-soc-thermal 4a0021e0.bandgap: Delay 1000 ms is not supported
      [    1.552691] ti-soc-thermal 4a0021e0.bandgap: Delay 1000 ms is not supported
      [    1.560029] ti-soc-thermal 4a0021e0.bandgap: Delay 1000 ms is not supported
      Signed-off-by: NTero Kristo <t-kristo@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Acked-by: NEduardo Valentin <edubezval@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      38f5c8ba
  5. 25 2月, 2015 2 次提交
  6. 11 11月, 2014 1 次提交
  7. 19 9月, 2014 2 次提交
  8. 12 9月, 2014 1 次提交
    • S
      ARM: dts: OMAP2+: Add sub mailboxes device node information · d27704d1
      Suman Anna 提交于
      The sub-mailbox devices are added to the Mailbox DT nodes on
      OMAP2420, OMAP2430, OMAP3, AM33xx, AM43xx, OMAP4 and OMAP5
      family of SoCs. This data represents the same mailboxes that
      used to be represented in hwmod attribute data previously.
      The node name is chosen based on the .name field of
      omap_mbox_dev_info structure used in the hwmod data.
      
      Cc: "Benoît Cousson" <bcousson@baylibre.com>
      Cc: Rob Herring <robh+dt@kernel.org>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
      Cc: Kumar Gala <galak@codeaurora.org>
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      d27704d1
  9. 09 9月, 2014 4 次提交
    • N
      ARM: dts: OMAP5 / DRA7: switch over to interrupts-extended property for UART · e2265abe
      Nishanth Menon 提交于
      We've had deeper idle states working on omaps for few years now,
      but only in the legacy mode. When booted with device tree, the
      wake-up events did not have a chance to work until commit
      3e6cee17 ("pinctrl: single: Add support for wake-up interrupts")
      that recently got merged. In addition to that we also needed
      commit 79d97015 ("of/irq: create interrupts-extended property")
      that's now also merged.
      
      Note that there's no longer need to specify the wake-up bit in
      the pinctrl settings, the request_irq on the wake-up pin takes
      care of that.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      e2265abe
    • N
      ARM: dts: OMAP5: switch to compatible pinctrl · 924c31cc
      Nishanth Menon 提交于
      Now that ti,omap5-padconf is available, switch over to that compatible
      property. Retain pinctrl-single for legacy support.
      
      While at it, mark pinctrl as interrupt controller so that it can be
      used with interrupts-extended property for wakeup events.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      924c31cc
    • N
      ARM: dts: OMAP3+: Add PRM interrupt · 5081ce62
      Nishanth Menon 提交于
      Provide OMAP3, 4 and OMAP5 with interrupt number for PRM
      
      And for DRA7, provide crossbar number for prm interrupt.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      5081ce62
    • T
      ARM: dts: omap5.dtsi: add DSS RFBI node · 84ace674
      Tomi Valkeinen 提交于
      The RFBI node for OMAP DSS was left out when adding the rest of the DSS
      nodes, because it was not clear how to set up the clocks for the RFBI.
      
      However, it seems that if there is a HWMOD for a device, we also need a
      DT node for it. Otherwise, at boot, we get:
      
      WARNING: CPU: 0 PID: 1 at arch/arm/mach-omap2/omap_hwmod.c:2542 _init+0x464/0x4e0()
      omap_hwmod: dss_rfbi: doesn't have mpu register target base
      
      Now that v3.17-rc3 contains a fix 8fd46439 ("ARM: dts:
      omap54xx-clocks: Fix the l3 and l4 clock rates") for the L3 ICLK
      required by the RFBI, let's add the RFBI node to get rid of the
      warning.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      [tony@atomide.com: updated description per comments from Nishant]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      84ace674
  10. 15 7月, 2014 1 次提交
  11. 08 7月, 2014 1 次提交
  12. 16 6月, 2014 1 次提交
    • N
      ARM: dts: omap5: Update CPU OPP table as per final production Manual · 05e7d1a5
      Nishanth Menon 提交于
      As per the Final production Data Manual for OMAP5432,
      SWPS050F(APRIL 2014)
      
      There are only two OPPs - 1GHz and 1.5GHz. the older OPP_LOW has been
      completely descoped. The Nominal voltages are still correct though.
      However, expectation for final production configuration is operation
      with Adaptive Body Bias (ABB) and Adaptive Voltage Scaling Class 0
      operation.
      
      There are no IDcode or version change information encoded to
      programmatically detect this and software is supposed to NOT use
      OPP_LOW(500MHz) anymore for all devices (legacy and production
      samples).
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      05e7d1a5
  13. 03 6月, 2014 2 次提交
  14. 15 5月, 2014 2 次提交
  15. 07 5月, 2014 1 次提交
  16. 26 4月, 2014 1 次提交
    • 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
  17. 19 4月, 2014 3 次提交
  18. 14 3月, 2014 2 次提交
  19. 13 3月, 2014 1 次提交
  20. 06 3月, 2014 1 次提交
  21. 05 3月, 2014 2 次提交
  22. 03 3月, 2014 1 次提交
  23. 01 3月, 2014 3 次提交
  24. 18 1月, 2014 1 次提交
  25. 04 12月, 2013 2 次提交
    • E
      arm: dts: add cooling properties on omap5 cpu node · 2cd29f63
      Eduardo Valentin 提交于
      OMAP5 devices can reach high temperatures and thus
      needs to have cpufreq-cooling on systems running on it.
      
      This patch adds the required cooling device properties
      so that cpufreq-cpu0 driver loads the cooling device.
      
      Cc: "Benoît Cousson" <bcousson@baylibre.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Ian Campbell <ian.campbell@citrix.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: linux-omap@vger.kernel.org
      Cc: devicetree@vger.kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NEduardo Valentin <eduardo.valentin@ti.com>
      2cd29f63
    • E
      arm: dts: add omap5 thermal data · 1b761fc5
      Eduardo Valentin 提交于
      This patch changes the dtsi entry on omap5 to contain
      the thermal data. This data will enable the passive
      cooling with CPUfreq cooling device at 100C. The
      system will do a thermal shutdown at 125C whenever
      any of its sensors sees this level.
      
      Cc: "Benoît Cousson" <bcousson@baylibre.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Ian Campbell <ian.campbell@citrix.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: linux-omap@vger.kernel.org
      Cc: devicetree@vger.kernel.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NEduardo Valentin <eduardo.valentin@ti.com>
      1b761fc5
  26. 30 10月, 2013 1 次提交