Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

at master 76 lines 3.2 kB view raw
1// SPDX-License-Identifier: GPL-2.0 2 3//! GPU Firmware (`GFW`) support, a.k.a `devinit`. 4//! 5//! Upon reset, the GPU runs some firmware code from the BIOS to setup its core parameters. Most of 6//! the GPU is considered unusable until this step is completed, so we must wait on it before 7//! performing driver initialization. 8//! 9//! A clarification about devinit terminology: devinit is a sequence of register read/writes after 10//! reset that performs tasks such as: 11//! 1. Programming VRAM memory controller timings. 12//! 2. Power sequencing. 13//! 3. Clock and PLL configuration. 14//! 4. Thermal management. 15//! 16//! devinit itself is a 'script' which is interpreted by an interpreter program typically running 17//! on the PMU microcontroller. 18//! 19//! Note that the devinit sequence also needs to run during suspend/resume. 20 21use kernel::{ 22 io::{ 23 poll::read_poll_timeout, 24 Io, // 25 }, 26 prelude::*, 27 time::Delta, // 28}; 29 30use crate::{ 31 driver::Bar0, 32 regs, // 33}; 34 35/// Wait for the `GFW` (GPU firmware) boot completion signal (`GFW_BOOT`), or a 4 seconds timeout. 36/// 37/// Upon GPU reset, several microcontrollers (such as PMU, SEC2, GSP etc) run some firmware code to 38/// setup its core parameters. Most of the GPU is considered unusable until this step is completed, 39/// so it must be waited on very early during driver initialization. 40/// 41/// The `GFW` code includes several components that need to execute before the driver loads. These 42/// components are located in the VBIOS ROM and executed in a sequence on these different 43/// microcontrollers. The devinit sequence typically runs on the PMU, and the FWSEC runs on the 44/// GSP. 45/// 46/// This function waits for a signal indicating that core initialization is complete. Before this 47/// signal is received, little can be done with the GPU. This signal is set by the FWSEC running on 48/// the GSP in Heavy-secured mode. 49pub(crate) fn wait_gfw_boot_completion(bar: &Bar0) -> Result { 50 // Before accessing the completion status in `NV_PGC6_AON_SECURE_SCRATCH_GROUP_05`, we must 51 // first check `NV_PGC6_AON_SECURE_SCRATCH_GROUP_05_PRIV_LEVEL_MASK`. This is because 52 // `NV_PGC6_AON_SECURE_SCRATCH_GROUP_05` becomes accessible only after the secure firmware 53 // (FWSEC) lowers the privilege level to allow CPU (LS/Light-secured) access. We can only 54 // safely read the status register from CPU (LS/Light-secured) once the mask indicates 55 // that the privilege level has been lowered. 56 // 57 // TIMEOUT: arbitrarily large value. GFW starts running immediately after the GPU is put out of 58 // reset, and should complete in less time than that. 59 read_poll_timeout( 60 || { 61 Ok( 62 // Check that FWSEC has lowered its protection level before reading the GFW_BOOT 63 // status. 64 bar.read(regs::NV_PGC6_AON_SECURE_SCRATCH_GROUP_05_PRIV_LEVEL_MASK) 65 .read_protection_level0() 66 && bar 67 .read(regs::NV_PGC6_AON_SECURE_SCRATCH_GROUP_05_0_GFW_BOOT) 68 .completed(), 69 ) 70 }, 71 |&gfw_booted| gfw_booted, 72 Delta::from_millis(1), 73 Delta::from_secs(4), 74 ) 75 .map(|_| ()) 76}