Lines Matching full:hardware

6 <dcn_blocks>` pages, you learned about the hardware components and how they
10 abstractions and operations to connect different APIs with the hardware
12 to access and configure DCN/DCE hardware (DCE is also part of DC, but for
21 From the display hardware perspective, it is plausible to expect that if a
22 problem is well-defined, it will probably be implemented at the hardware level.
27 implemented in hardware are enabled via DC configuration.
29 In terms of hardware management, DCN has multiple instances of the same block
33 quite simple: minimize the hardware shuffle when the driver performs some
35 easier to maneuver if the hardware resource is still used for the same set of
46 variables related to this problem (e.g., many different DCN/DCE hardware
69 the hardware configuration block; the main file describing it is
71 the hardware sequencer folder. Almost at the end, you can see the block level
111 `dc_state`, which represents the logic state within the hardware at the moment;
126 basic hardware/software operations. Let's start with the `dc_create()`
130 that this operation does not touch any hardware configuration; it is only a
134 struct. Its main function is to put the hardware in a valid state. It is worth
135 highlighting that the hardware might initialize in an unknown state, and it is
137 for the hardware-specific initialization, whereas `dc_hardware_init` does the
138 hardware initialization and is the first point where we touch hardware.
152 and, based on that, validates whether the hardware can support it or not. It is
154 it does not mean the DCN hardware can support it.