1. 08 Nov, 2019 30 commits
  2. 06 Nov, 2019 1 commit
  3. 29 Oct, 2019 4 commits
    • Ross Lagerwall's avatar
      xen/efi: Set nonblocking callbacks · 90a886b6
      Ross Lagerwall authored
      [ Upstream commit df359f0d
      
       ]
      
      Other parts of the kernel expect these nonblocking EFI callbacks to
      exist and crash when running under Xen. Since the implementations of
      xen_efi_set_variable() and xen_efi_query_variable_info() do not take any
      locks, use them for the nonblocking callbacks too.
      Signed-off-by: default avatarRoss Lagerwall <ross.lagerwall@citrix.com>
      Reviewed-by: default avatarJuergen Gross <jgross@suse.com>
      Signed-off-by: default avatarJuergen Gross <jgross@suse.com>
      Signed-off-by: default avatarSasha Levin <sashal@kernel.org>
      90a886b6
    • Peter Ujfalusi's avatar
      ARM: dts: am4372: Set memory bandwidth limit for DISPC · 1cd24f5e
      Peter Ujfalusi authored
      [ Upstream commit f90ec6cd
      
       ]
      
      Set memory bandwidth limit to filter out resolutions above 720p@60Hz to
      avoid underflow errors due to the bandwidth needs of higher resolutions.
      
      am43xx can not provide enough bandwidth to DISPC to correctly handle
      'high' resolutions.
      Signed-off-by: default avatarPeter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarSasha Levin <sashal@kernel.org>
      1cd24f5e
    • Tony Lindgren's avatar
      ARM: OMAP2+: Fix warnings with broken omap2_set_init_voltage() · ec3817c6
      Tony Lindgren authored
      [ Upstream commit cf395f7d ]
      
      This code is currently unable to find the dts opp tables as ti-cpufreq
      needs to set them up first based on speed binning.
      
      We stopped initializing the opp tables with platform code years ago for
      device tree based booting with commit 92d51856
      
       ("ARM: OMAP3+: do not
      register non-dt OPP tables for device tree boot"), and all of mach-omap2
      is now booting using device tree.
      
      We currently get the following errors on init:
      
      omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu
      omap2_set_init_voltage: unable to set vdd_mpu
      omap2_set_init_voltage: unable to find boot up OPP for vdd_core
      omap2_set_init_voltage: unable to set vdd_core
      omap2_set_init_voltage: unable to find boot up OPP for vdd_iva
      omap2_set_init_voltage: unable to set vdd_iva
      
      Let's just drop the unused code. Nowadays ti-cpufreq should be used to
      to initialize things properly.
      
      Cc: Adam Ford <aford173@gmail.com>
      Cc: André Roth <neolynx@gmail.com>
      Cc: "H. Nikolaus Schaller" <hns@goldelico.com>
      Cc: Nishanth Menon <nm@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Tested-by: Adam Ford <aford173@gmail.com> #logicpd-torpedo-37xx-devkit
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarSasha Levin <sashal@kernel.org>
      ec3817c6
    • Tony Lindgren's avatar
      ARM: OMAP2+: Fix missing reset done flag for am3 and am43 · a23cd06c
      Tony Lindgren authored
      [ Upstream commit 8ad8041b
      
       ]
      
      For ti,sysc-omap4 compatible devices with no sysstatus register, we do have
      reset done status available in the SOFTRESET bit that clears when the reset
      is done. This is documented for example in am437x TRM for DMTIMER_TIOCP_CFG
      register. The am335x TRM just says that SOFTRESET bit value 1 means reset is
      ongoing, but it behaves the same way clearing after reset is done.
      
      With the ti-sysc driver handling this automatically based on no sysstatus
      register defined, we see warnings if SYSC_HAS_RESET_STATUS is missing in the
      legacy platform data:
      
      ti-sysc 48042000.target-module: sysc_flags 00000222 != 00000022
      ti-sysc 48044000.target-module: sysc_flags 00000222 != 00000022
      ti-sysc 48046000.target-module: sysc_flags 00000222 != 00000022
      ...
      
      Let's fix these warnings by adding SYSC_HAS_RESET_STATUS. Let's also
      remove the useless parentheses while at it.
      
      If it turns out we do have ti,sysc-omap4 compatible devices without a
      working SOFTRESET bit we can set up additional quirk handling for it.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarSasha Levin <sashal@kernel.org>
      a23cd06c
  4. 17 Oct, 2019 1 commit
  5. 07 Oct, 2019 4 commits