Tianocore/edk2-platforms.git/Platform/RaspberryPi/AcpiTables/GpuDevs.asl, branch CodeCleanup

Platform/RaspberryPi/RPi4: Fix non-standard ACPI CIDs

2021-07-22T10:38:18+00:00

Remove non-standard RPI ACPI _CIDs that are not needed. This also fixes the FWTS failure reported in https://github.com/pftf/RPi4/issues/67 The windows drivers at https://github.com/raspberrypi/windows-drivers are still able to match the ACPI objects using the HIDs which are supported in the drivers, with these two recent changes needed: 6469702898789e555c6947e50216a3f79e0ddeb9 and 5c5e2742b4c983b3001c473b168b0dae2fcba0c2 Cc: Leif Lindholm Cc: Ard Biesheuvel Cc: Pete Batard Cc: Andrei Warkentin Cc: Mario Bălănică Signed-off-by: Samer El-Haj-Mahmoud Tested-by: Mario Bălănică Reviewed-by: Sunny Wang Tested-by: Sunny Wang Reviewed-by: Andrei Warkentin

Platform/RPi/AcpiTables: Describe DMA constraints for devices behind GPU

2020-03-26T12:34:55+00:00

Legacy devices on a Raspberry Pi sit behind GPU/VideoCore and can only address the first GB of RAM. This address range of 0xc0000000-0xffffffff requires a translation, since it is aliased to the first GB of memory 0x00000000-0x3fffffff, which is what this commit accomplishes by introducing a new "GDV0" device along with a "_DMA" ResourceTemplate that performs the address translation. Note that this translation does not apply to the ARM cores, PCIe, GENET, and 40-bit DMA channels, that all have a wider view of the address space. Signed-off-by: Pete Batard Reviewed-by: Ard Biesheuvel

Platform/RPi/AcpiTables: Move GPU devices into a separate ASL file

2020-03-26T12:34:52+00:00

In order to describe the DMA constraints of legacy devices behind the Raspberry Pi GPU/VideoCore, we move them into their own separate ASL file. This is a straight copy of the existing content from Dsdt.asl, with no alteration, so that the changes applied in the next patch are made more obvious. Signed-off-by: Pete Batard Reviewed-by: Ard Biesheuvel