| /arm-trusted-firmware-2.8.0/drivers/usb/ |
| A D | usb_device.c | 49 pdev->driver->ep_set_stall(hpcd->instance, ep); in usb_core_set_stall()
51 pdev->driver->ep0_out_start(hpcd->instance); in usb_core_set_stall()
554 pdev->driver->read_packet(pdev->data->instance, in usb_core_handle_it()
563 pdev->driver->read_packet(pdev->data->instance, in usb_core_handle_it()
621 pdev->driver->ep0_start_xfer(handle, ep); in usb_core_start_xfer()
623 pdev->driver->ep_start_xfer(handle, ep); in usb_core_start_xfer()
769 pdev->driver->start_device(pdev->data->instance); in usb_core_start()
786 pdev->driver->stop_device(pdev->data->instance); in usb_core_stop()
802 const struct usb_driver *driver, in register_usb_driver() argument
809 assert(driver != NULL); in register_usb_driver()
[all …]
|
| /arm-trusted-firmware-2.8.0/plat/brcm/board/stingray/ |
| A D | platform.mk | 198 plat/${SOC_DIR}/driver/plat_emmc.c \
207 PLAT_BL_COMMON_SOURCES += plat/${SOC_DIR}/driver/usb.c \
208 plat/${SOC_DIR}/driver/usb_phy.c
211 BL2_SOURCES += plat/${SOC_DIR}/driver/ihost_pll_config.c \
213 plat/${SOC_DIR}/driver/swreg.c
216 PLAT_INCLUDES += -Iplat/${SOC_DIR}/driver/ddr/soc/include
218 PLAT_INCLUDES += -Iplat/${SOC_DIR}/driver/ext_sram_init
219 BL2_SOURCES += plat/${SOC_DIR}/driver/ext_sram_init/ext_sram_init.c
234 plat/${SOC_DIR}/driver/ihost_pll_config.c \
|
| /arm-trusted-firmware-2.8.0/fdts/ |
| A D | juno-ethosn.dtsi | 10 * Refer to the Arm(R) Ethos(TM)-N driver stack for complete device tree examples.
11 * https://github.com/ARM-software/ethos-n-driver-stack
|
| /arm-trusted-firmware-2.8.0/docs/components/measured_boot/ |
| A D | event_log.rst | 11 Measured Boot driver expects a *tpm_event_log* node with the following field
19 can be used by Measured Boot driver. Each property is named according
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | debugfs-design.rst | 57 - mount(): create a link between a driver and spec.
73 - This permits direct access to a firmware driver, mainly for test purposes
105 - Notice, a physical device driver if exposed by the firmware may conflict with
106 the higher level OS if the latter implements its own driver for the same
115 - a Linux kernel driver running at NS-EL1
116 - a Linux userspace application through the kernel driver
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/misc/ |
| A D | mvebu-ccu.rst | 4 CCU configuration driver (1st stage address translation) for Marvell Armada 8K and 8K+ SoCs.
|
| A D | mvebu-amb.rst | 4 AXI to M-bridge decoding unit driver for Marvell Armada 8K and 8K+ SoCs.
|
| A D | mvebu-io-win.rst | 4 IO Window configuration driver (2nd stage address translation) for Marvell Armada 8K and 8K+ SoCs.
|
| A D | mvebu-iob.rst | 4 IO bridge configuration driver (3rd stage address translation) for Marvell Armada 8K and 8K+ SoCs.
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | code-review-guidelines.rst | 70 For example, if some existing piece of code - say a driver - does not quite
187 - Generally speaking, new driver code should be placed in the generic
188 layer. There are cases where a driver has to stay into the platform layer but
191 - Existing common drivers (in particular for Arm IPs like the GIC driver) should
194 duplicate driver is less likely to benefit from bug fixes and future
195 enhancements. In most cases, it is possible to rework a generic driver to
199 - When a platform specific driver really is required, the burden lies with the
|
| A D | platform-ports-policy.rst | 11 documented in the :ref:`Porting Guide`), driver APIs (like the GICv3 drivers) or
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | xilinx-versal-net.rst | 25 * `VERSAL_NET_CONSOLE`: Select the console driver. Options:
|
| A D | meson-axg.rst | 13 - GICv2 driver set up.
|
| A D | meson-g12a.rst | 13 - GICv2 driver set up.
|
| A D | meson-gxbb.rst | 13 - GICv2 driver set up.
|
| A D | meson-gxl.rst | 13 - GICv2 driver set up.
|
| A D | xilinx-versal.rst | 40 * `VERSAL_CONSOLE`: Select the console driver. Options:
|
| A D | intel-agilex.rst | 81 INFO: ARM GICv2 driver initialized
|
| A D | xilinx-zynqmp.rst | 39 - ``ZYNQMP_CONSOLE``: Select the console driver. Options:
|
| A D | intel-stratix10.rst | 88 INFO: ARM GICv2 driver initialized
|
| /arm-trusted-firmware-2.8.0/include/drivers/ |
| A D | usb_device.h | 256 const struct usb_driver *driver; member
273 const struct usb_driver *driver,
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | change-log.md | 3158 - generic timer driver
3676 - Added Broadcom RNG driver
3785 - Added RNG driver
3980 - STM32MP1 Clock driver
4180 - brcm: Add iproc SPI Nor flash support, spi driver, emmc driver, and support
4215 QSPI, FMC2 driver
4547 - intel: Add ncore ccu driver
4638 driver
6109 - Changed FVP default interrupt driver to be the GICv3-only driver. **Note**
6237 common driver. The standalone CCI-400 driver has been deprecated.
[all …]
|
| /arm-trusted-firmware-2.8.0/plat/st/stm32mp1/ |
| A D | platform.mk | 490 echo "No boot device driver is enabled"; \
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/fvp/ |
| A D | index.rst | 112 - ``FVP_INTERCONNECT_DRIVER``: Selects the interconnect driver to be built. The
113 default interconnect driver depends on the value of ``FVP_CLUSTER_COUNT`` as
116 - ``FVP_CCI`` : The CCI driver is selected. This is the default
118 - ``FVP_CCN`` : The CCN driver is selected. This is the default
128 - ``FVP_USE_GIC_DRIVER`` : Selects the GIC driver to be built. Options:
130 - ``FVP_GICV2`` : The GICv2 only driver is selected
131 - ``FVP_GICV3`` : The GICv3 only driver is selected (default option)
|
| /arm-trusted-firmware-2.8.0/docs/components/spd/ |
| A D | tlk-dispatcher.rst | 44 • Linux kernel driver
|