1. 30 Nov, 2018 18 commits
  2. 29 Nov, 2018 1 commit
    • Linus Walleij's avatar
      ARM: dts: Modernize the Vexpress PL111 integration · f1fe12c8
      Linus Walleij authored
      The Versatile Express was submitted with the actual display
      bridges unconnected (but defined in the device tree) and
      mock "panels" encoded in the device tree node of the PL111
      controller.
      
      This doesn't even remotely describe the actual Versatile
      Express hardware. Exploit the SiI9022 bridge by connecting
      the PL111 pads to it, making it use EDID or fallback values
      to drive the monitor.
      
      The  also has to use the reserved memory through the
      CMA pool rather than by open coding a memory region and
      remapping it explicitly in the driver. To achieve this,
      a reserved-memory node must exist in the root of the
      device tree, so we need to pull that out of the
      motherboard .dtsi include files, and push it into each
      top-level device tree instead.
      
      We do the same manouver for all the Versatile Express
      boards, taking into account the different location of the
      video RAM depending on which chip select is used on
      each platform.
      
      This plays nicely with the new PL111 DRM driver and
      follows the standard ways of assigning bridges and
      memory pools for graphics.
      
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
      Cc: Liviu Dudau <liviu.dudau@arm.com>
      Cc: Mali DP Maintainers <malidp@foss.arm.com>
      Cc: Robin Murphy <robin.murphy@arm.com>
      Tested-by: default avatarLiviu Dudau <liviu.dudau@arm.com>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      f1fe12c8
  3. 28 Nov, 2018 20 commits
  4. 26 Nov, 2018 1 commit
    • Viresh Kumar's avatar
      arm64: dts: renesas: Add all CPUs in cooling maps · 275e4eb3
      Viresh Kumar authored
      Each CPU can (and does) participate in cooling down the system but the
      DT only captures a handful of them, normally CPU0, in the cooling maps.
      Things work by chance currently as under normal circumstances its the
      first CPU of each cluster which is used by the operating systems to
      probe the cooling devices. But as soon as this CPU ordering changes and
      any other CPU is used to bring up the cooling device, we will start
      seeing failures.
      
      Also the DT is rather incomplete when we list only one CPU in the
      cooling maps, as the hardware doesn't have any such limitations.
      
      Update cooling maps to include all devices affected by individual trip
      points.
      Signed-off-by: default avatarViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: default avatarSimon Horman <horms+renesas@verge.net.au>
      275e4eb3