mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
f1fe12c8bf
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: Liviu Dudau <liviu.dudau@arm.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> |
||
---|---|---|
.. | ||
foundation-v8-gicv2.dtsi | ||
foundation-v8-gicv3-psci.dts | ||
foundation-v8-gicv3.dts | ||
foundation-v8-gicv3.dtsi | ||
foundation-v8-psci.dts | ||
foundation-v8-psci.dtsi | ||
foundation-v8-spin-table.dtsi | ||
foundation-v8.dts | ||
foundation-v8.dtsi | ||
juno-base.dtsi | ||
juno-clocks.dtsi | ||
juno-cs-r1r2.dtsi | ||
juno-motherboard.dtsi | ||
juno-r1.dts | ||
juno-r2.dts | ||
juno.dts | ||
Makefile | ||
rtsm_ve-aemv8a.dts | ||
rtsm_ve-motherboard.dtsi | ||
vexpress-v2f-1xv7-ca53x2.dts | ||
vexpress-v2m-rs1.dtsi |