Home
last modified time | relevance | path

Searched refs:driver (Results 1 – 25 of 49) sorted by relevance

12

/trusted-firmware-a-latest/drivers/usb/
Dusb_device.c49 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()
252 pdev->driver->set_address(((struct pcd_handle *)(pdev->data))->instance, dev_addr); in usb_core_set_address()
533 switch (pdev->driver->it_handler(pdev->data->instance, &param)) { in usb_core_handle_it()
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()
601 pdev->driver->write_empty_tx_fifo(pdev->data->instance, param, 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()
[all …]
/trusted-firmware-a-latest/plat/brcm/board/stingray/
Dplatform.mk198 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 \
217 PLAT_INCLUDES += -Iplat/${SOC_DIR}/driver/ddr/soc/include
219 PLAT_INCLUDES += -Iplat/${SOC_DIR}/driver/ext_sram_init
220 BL2_SOURCES += plat/${SOC_DIR}/driver/ext_sram_init/ext_sram_init.c
235 plat/${SOC_DIR}/driver/ihost_pll_config.c \
/trusted-firmware-a-latest/docs/plat/st/
Dstm32mp2.rst72 To compile the correct DDR driver, one flag must be set among:
74 - | ``STM32MP_DDR3_TYPE``: to compile DDR3 driver and DT.
76 - | ``STM32MP_DDR4_TYPE``: to compile DDR4 driver and DT.
78 - | ``STM32MP_LPDDR4_TYPE``: to compile LpDDR4 driver and DT.
Dstm32mpus.rst55 - | ``STM32MP_EARLY_CONSOLE``: to enable early traces before clock driver is setup.
/trusted-firmware-a-latest/docs/components/
Ddebugfs-design.rst57 - 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
/trusted-firmware-a-latest/docs/components/measured_boot/
Devent_log.rst11 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
/trusted-firmware-a-latest/docs/plat/marvell/armada/misc/
Dmvebu-ccu.rst4 CCU configuration driver (1st stage address translation) for Marvell Armada 8K and 8K+ SoCs.
Dmvebu-amb.rst4 AXI to M-bridge decoding unit driver for Marvell Armada 8K and 8K+ SoCs.
Dmvebu-io-win.rst4 IO Window configuration driver (2nd stage address translation) for Marvell Armada 8K and 8K+ SoCs.
Dmvebu-iob.rst4 IO bridge configuration driver (3rd stage address translation) for Marvell Armada 8K and 8K+ SoCs.
/trusted-firmware-a-latest/fdts/
Djuno-ethosn.dtsi10 * 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
/trusted-firmware-a-latest/docs/process/
Dplatform-ports-policy.rst11 documented in the :ref:`Porting Guide`), driver APIs (like the GICv3 drivers) or
38 If a platform, driver or library interface is no longer maintained, it is best
Dcode-review-guidelines.rst91 For example, if some existing piece of code - say a driver - does not quite
216 - Generally speaking, new driver code should be placed in the generic
217 layer. There are cases where a driver has to stay into the platform layer but
220 - Existing common drivers (in particular for Arm IPs like the GIC driver) should
223 duplicate driver is less likely to benefit from bug fixes and future
224 enhancements. In most cases, it is possible to rework a generic driver to
228 - When a platform specific driver really is required, the burden lies with the
/trusted-firmware-a-latest/docs/plat/
Dmeson-axg.rst13 - GICv2 driver set up.
Dmeson-g12a.rst13 - GICv2 driver set up.
Dmeson-gxbb.rst13 - GICv2 driver set up.
Dmeson-gxl.rst13 - GICv2 driver set up.
Dxilinx-versal-net.rst35 * `VERSAL_NET_CONSOLE`: Select the console driver. Options:
Dintel-agilex.rst81 INFO: ARM GICv2 driver initialized
Dxilinx-versal.rst45 * `VERSAL_CONSOLE`: Select the console driver. Options:
Dintel-stratix10.rst88 INFO: ARM GICv2 driver initialized
/trusted-firmware-a-latest/include/drivers/
Dusb_device.h256 const struct usb_driver *driver; member
273 const struct usb_driver *driver,
/trusted-firmware-a-latest/docs/plat/arm/fvp/
Dindex.rst111 - ``FVP_INTERCONNECT_DRIVER``: Selects the interconnect driver to be built. The
112 default interconnect driver depends on the value of ``FVP_CLUSTER_COUNT`` as
115 - ``FVP_CCI`` : The CCI driver is selected. This is the default
117 - ``FVP_CCN`` : The CCN driver is selected. This is the default
127 - ``FVP_USE_GIC_DRIVER`` : Selects the GIC driver to be built. Options:
129 - ``FVP_GICV2`` : The GICv2 only driver is selected
130 - ``FVP_GICV3`` : The GICv3 only driver is selected (default option)
/trusted-firmware-a-latest/docs/design_documents/
Dmeasured_boot.rst92 Log driver implemented in TF-A covers later part.
131 driver, and also to write header information in the Event Log
200 measurement using the Measured Boot backend driver.
/trusted-firmware-a-latest/docs/about/
Dfeatures.rst37 - A generic |SCMI| driver to interface with conforming power controllers, for
131 - RSS comms driver ``drivers/arm/rss``

12