1. 07 Oct, 2021 2 commits
  2. 06 Oct, 2021 6 commits
  3. 05 Oct, 2021 14 commits
  4. 04 Oct, 2021 9 commits
  5. 30 Sep, 2021 1 commit
    • Tony Lindgren's avatar
      soc: ti: omap-prm: Fix external abort for am335x pruss · b2325370
      Tony Lindgren authored
      Starting with v5.15-rc1, we may now see some am335x beaglebone black
      device produce the following error on pruss probe:
      
      Unhandled fault: external abort on non-linefetch (0x1008) at 0xe0326000
      
      This has started with the enabling of pruss for am335x in the dts files.
      
      Turns out the is caused by the PRM reset handling not waiting for the
      reset bit to clear. To fix the issue, let's always wait for the reset
      bit to clear, even if there is a separate reset status register.
      
      We attempted to fix a similar issue for dra7 iva with a udelay() in
      commit effe89e4 ("soc: ti: omap-prm: Fix occasional abort on reset
      deassert for dra7 iva"). There is no longer a need for the udelay()
      for dra7 iva reset either with the check added for reset bit clearing.
      
      Cc: Drew Fustini <pdp7pdp7@gmail.com>
      Cc: Grygorii Strashko <grygorii.strashko@ti.com>
      Cc: "H. Nikolaus Schaller" <hns@goldelico.com>
      Cc: Robert Nelson <robertcnelson@gmail.com>
      Cc: Yongqin Liu <yongqin.liu@linaro.org>
      Fixes: effe89e4 ("soc: ti: omap-prm: Fix occasional abort on reset deassert for dra7 iva")
      Reported-by: default avatarMatti Vaittinen <mazziesaccount@gmail.com>
      Tested-by: default avatarMatti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      b2325370
  6. 26 Sep, 2021 1 commit
    • Rob Herring's avatar
      arm: dts: vexpress: Fix motherboard bus 'interrupt-map' · 319aeaf6
      Rob Herring authored
      Commit 078fb7aa ("arm: dts: vexpress: Fix addressing issues with
      'motherboard-bus' nodes") broke booting on a couple of 32-bit VExpress
      boards. The problem is #address-cells size changed, but interrupt-map
      was not updated. This results in the timer interrupt (and all the
      other motherboard interrupts) not getting mapped.
      
      As the 'interrupt-map' properties are all just duplicates across boards,
      just move them into vexpress-v2m.dtsi and vexpress-v2m-rs1.dtsi.
      Strictly speaking, 'interrupt-map' is dependent on the parent
      interrupt controller, but it's not likely we'll ever have a different
      parent than GICv2 on these old platforms. If there was one,
      'interrupt-map' can still be overridden.
      
      Link: https://lore.kernel.org/r/20210924214221.1877686-1-robh@kernel.org
      Fixes: 078fb7aa ("arm: dts: vexpress: Fix addressing issues with 'motherboard-bus' nodes")
      Cc: Guillaume Tucker <guillaume.tucker@collabora.com>
      Cc: Liviu Dudau <liviu.dudau@arm.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
      Cc: linux-arm-kernel@lists.infradead.org
      Reported-by: default avatarReported-by: "kernelci.org bot" <bot@kernelci.org>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarSudeep Holla <sudeep.holla@arm.com>
      319aeaf6
  7. 24 Sep, 2021 4 commits
  8. 22 Sep, 2021 3 commits