Home
last modified time | relevance | path

Searched full:trm (Results 1 – 24 of 24) sorted by relevance

/qemu/include/hw/dma/
H A Dpl080.h15 * The PL080 TRM is:
17 * and the PL081 TRM is:
/qemu/include/hw/ssi/
H A Dpl022.h14 * The PL022 TRM is:
H A Dxlnx-versal-ospi.h34 * https://www.xilinx.com/support/documentation/architecture-manuals/am011-versal-acap-trm.pdf
/qemu/docs/system/arm/
H A Dxlnx-zynq.rst8 https://docs.amd.com/r/en-US/ug585-zynq-7000-SoC-TRM/Zynq-7000-SoC-Technical-Reference-Manual
/qemu/include/hw/misc/
H A Dtz-mpc.h13 * It is documented in the ARM CoreLink SIE-200 System IP for Embedded TRM
H A Dxlnx-versal-pmc-iou-slcr.h34 * https://www.xilinx.com/support/documentation/architecture-manuals/am011-versal-acap-trm.pdf
H A Dtz-msc.h14 * It is documented in the ARM CoreLink SIE-200 System IP for Embedded TRM
H A Dtz-ppc.h13 * It is documented in the ARM CoreLink SIE-200 System IP for Embedded TRM
H A Dxlnx-versal-cfu.h12 * https://www.xilinx.com/support/documentation/architecture-manuals/am011-versal-acap-trm.pdf
H A Dxlnx-versal-cframe-reg.h12 * https://www.xilinx.com/support/documentation/architecture-manuals/am011-versal-acap-trm.pdf
/qemu/hw/cpu/
H A Darm11mpcore.c136 /* The ARM11 MPCORE TRM says the on-chip controller may have
/qemu/hw/gpio/
H A Domap_gpio.c164 case 0x18: /* PIN_CONTROL (not in OMAP310 TRM) */ in omap_gpio_write()
H A Dpl061.c454 /* reset values from PL061 TRM, Stellaris LM3S5P31 & LM3S8962 Data Sheet */ in pl061_enter_reset()
/qemu/hw/misc/
H A Dtz-msc.c113 * The TRM isn't clear on behaviour if irq_clear is high when a in tz_msc_check()
H A Dmps2-scc.c15 * Documentation of it can be found in the MPS2 TRM:
/qemu/hw/arm/
H A Dmps2-tz.c22 * Links to the TRM for the board itself and to the various Application
26 * Board TRM:
40 * Similarly, the AN521 and AN524 use the SSE-200, and the SSE-200 TRM defines
43 * and the AN547 uses the SSE-300, whose layout is in the SSE-300 TRM:
H A Dxilinx_zynq.c379 * Refer to the ug585-Zynq-7000-TRM manual B.3 (Module Summary) and in zynq_init()
H A Dmps2.c22 * Links to the TRM for the board itself and to the various Application
H A Domap1.c628 /* Bits 0 and 1 seem to be confused in the OMAP 310 TRM */ in omap_ulpd_pm_write()
685 /* XXX: OMAP310 TRM claims bit 3 is PLL_ENABLE, and bit 4 is in omap_ulpd_pm_write()
/qemu/rust/hw/char/pl011/src/
H A Dregisters.rs118 /// The TRM confusingly describes this offset as UARTRSR for reads
/qemu/target/arm/tcg/
H A Dcpu64.c707 * The Neoverse-V1 r1p2 TRM lists 32-bit format CCSIDR_EL1 values, in aarch64_neoverse_v1_initfn()
710 * information in chapter 2 of the TRM: in aarch64_neoverse_v1_initfn()
951 * The cortex-a710 TRM does not list CCSIDR values. The layout of in aarch64_a710_initfn()
1052 * The Neoverse N2 TRM does not list CCSIDR values. The layout of in aarch64_neoverse_n2_initfn()
/qemu/hw/char/
H A Dcadence_uart.c5 * - http://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf
/qemu/include/standard-headers/drm/
H A Ddrm_fourcc.h878 * Chapter 20 "Pixel Memory Formats" of the Tegra X1 TRM describes this format
992 * Chapter 20 "Pixel Memory Formats" of the Tegra X1 TRM describes this format
/qemu/hw/net/can/
H A Dxlnx-zynqmp-can.c4 * https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf