1. 15 Feb, 2021 3 commits
    • Tony Lindgren's avatar
      Merge branch 'fixes-v5.11' into fixes · 857de6fe
      Tony Lindgren authored
      857de6fe
    • Tony Lindgren's avatar
      ARM: OMAP2+: Fix smartreflex init regression after dropping legacy data · fbfa463b
      Tony Lindgren authored
      When I dropped legacy data for omap4 and dra7 smartreflex in favor of
      device tree based data, it seems I only testd for the "SmartReflex Class3
      initialized" line in dmesg. I missed the fact that there is also
      omap_devinit_smartreflex() that happens later, and now it produces an
      error on boot for "No Voltage table for the corresponding vdd. Cannot
      create debugfs entries for n-values".
      
      This happens as we no longer have the smartreflex instance legacy data,
      and have not yet moved completely to device tree based booting for the
      driver. Let's fix the issue by changing the smartreflex init to use names.
      This should all eventually go away in favor of doing the init in the
      driver based on devicetree compatible value.
      
      Note that dra7xx_init_early() is not calling any voltage domain init like
      omap54xx_voltagedomains_init(), or a dra7 specific voltagedomains init.
      This means that on dra7 smartreflex is still not fully initialized, and
      also seems to be missing the related devicetree nodes.
      
      Fixes: a6b1e717 ("ARM: OMAP2+: Drop legacy platform data for omap4 smartreflex")
      Fixes: e54740b4 ("ARM: OMAP2+: Drop legacy platform data for dra7 smartreflex")
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      fbfa463b
    • Tony Lindgren's avatar
      soc: ti: omap-prm: Fix reboot issue with invalid pcie reset map for dra7 · a249ca66
      Tony Lindgren authored
      Yongqin Liu <yongqin.liu@linaro.org> reported an issue where reboot hangs
      on beagleboard-x15. This started happening after commit 7078a5ba
      ("soc: ti: omap-prm: Fix boot time errors for rst_map_012 bits 0 and 1").
      
      We now assert any 012 type resets on init to prevent unconfigured
      accelerator MMUs getting enabled on init depending on the bootloader or
      kexec configured state.
      
      Turns out that we now also wrongly assert dra7 l3init domain PCIe reset
      bits causing a hang during reboot. Let's fix the l3init reset bits to
      use a 01 map instead of 012 map. There are only two rstctrl bits and not
      three. This is documented in TRM "Table 3-1647. RM_PCIESS_RSTCTRL".
      
      Fixes: 5a68c87a ("soc: ti: omap-prm: dra7: add genpd support for remaining PRM instances")
      Fixes: 7078a5ba ("soc: ti: omap-prm: Fix boot time errors for rst_map_012 bits 0 and 1")
      Cc: Kishon Vijay Abraham I <kishon@ti.com>
      Reported-by: default avatarYongqin Liu <yongqin.liu@linaro.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      a249ca66
  2. 14 Feb, 2021 7 commits
  3. 13 Feb, 2021 12 commits
  4. 12 Feb, 2021 13 commits
  5. 11 Feb, 2021 5 commits