Home
last modified time | relevance | path

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

123

/rk3399_ARM-atf/docs/plat/arm/fvp/
H A Dfvp-build-options.rst10 - ``FVP_INTERCONNECT_DRIVER``: Selects the interconnect driver to be built. The
11 default interconnect driver depends on the value of ``FVP_CLUSTER_COUNT`` as
14 - ``FVP_CCI`` : The CCI driver is selected. This is the default
16 - ``FVP_CCN`` : The CCN driver is selected. This is the default
26 - ``FVP_USE_GIC_DRIVER`` : Selects the GIC driver to be built. Options:
28 - ``FVP_GICV2`` : The GICv2 only driver is selected
29 - ``FVP_GICV3`` : The GICv3 only driver is selected (default option)
30 - ``FVP_GICV5`` : The GICv5 only driver is selected
/rk3399_ARM-atf/drivers/usb/
H A Dusb_device.c39 pdev->driver->ep_set_stall(hpcd->instance, ep); in usb_core_set_stall()
41 pdev->driver->ep0_out_start(hpcd->instance); in usb_core_set_stall()
245 pdev->driver->set_address(((struct pcd_handle *)(pdev->data))->instance, in usb_core_set_address()
530 switch (pdev->driver->it_handler(pdev->data->instance, &param)) { in usb_core_handle_it()
551 pdev->driver->read_packet(pdev->data->instance, ep->xfer_buff, in usb_core_handle_it()
560 pdev->driver->read_packet(pdev->data->instance, in usb_core_handle_it()
598 pdev->driver->write_empty_tx_fifo( in usb_core_handle_it()
618 pdev->driver->ep0_start_xfer(handle, ep); in usb_core_start_xfer()
620 pdev->driver->ep_start_xfer(handle, ep); in usb_core_start_xfer()
774 pdev->driver->start_device(pdev->data->instance); in usb_core_start()
[all …]
/rk3399_ARM-atf/plat/brcm/board/stingray/
H A 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 \
/rk3399_ARM-atf/docs/components/
H A 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
/rk3399_ARM-atf/docs/design/
H A Dconsole-framework.rst9 that the driver of the UART that is needed is already implemented. If not, a driver
28 The supported UART list is non-exhaustive. Check if the UART driver has
62 UART driver API is defined in ``include/drivers/arm/pl011.h``.
64 A skeleton console driver (assembly) is provided in TF-A ``drivers/console/aarch64/
89 The ``xxx`` in the function name is replaced with the console driver
91 ``console_pl011_register`` in the driver for pl011.
149 xxx : name of the console driver
156 driver's register function. It takes ``putc``, ``getc`` and ``flush`` macro
157 arguments. It will register all of the driver's callbacks in the ``console_t``
171 Currently there is no C template for implementing a console driver in C but it can
[all …]
/rk3399_ARM-atf/docs/components/measured_boot/
H A 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
/rk3399_ARM-atf/docs/plat/marvell/armada/misc/
H A Dmvebu-ccu.rst4 CCU configuration driver (1st stage address translation) for Marvell Armada 8K and 8K+ SoCs.
H A Dmvebu-amb.rst4 AXI to M-bridge decoding unit driver for Marvell Armada 8K and 8K+ SoCs.
H A Dmvebu-io-win.rst4 IO Window configuration driver (2nd stage address translation) for Marvell Armada 8K and 8K+ SoCs.
H A Dmvebu-iob.rst4 IO bridge configuration driver (3rd stage address translation) for Marvell Armada 8K and 8K+ SoCs.
/rk3399_ARM-atf/docs/plat/st/
H A Dstm32mp2.rst117 To compile the correct DDR driver, one flag must be set among:
119 - | ``STM32MP_DDR3_TYPE``: to compile DDR3 driver and DT.
121 - | ``STM32MP_DDR4_TYPE``: to compile DDR4 driver and DT.
123 - | ``STM32MP_LPDDR4_TYPE``: to compile LpDDR4 driver and DT.
/rk3399_ARM-atf/docs/process/
H A 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
H A 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
/rk3399_ARM-atf/fdts/
H A 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
/rk3399_ARM-atf/docs/plat/
H A Dmeson-axg.rst13 - GICv2 driver set up.
H A Dmeson-gxbb.rst13 - GICv2 driver set up.
H A Dmeson-g12a.rst13 - GICv2 driver set up.
H A Dmeson-gxl.rst13 - GICv2 driver set up.
H A Dintel-agilex.rst81 INFO: ARM GICv2 driver initialized
H A Dintel-stratix10.rst88 INFO: ARM GICv2 driver initialized
H A Dxilinx-versal-net.rst40 * `VERSAL_NET_CONSOLE`: Select the console driver. Options:
/rk3399_ARM-atf/include/drivers/
H A Dusb_device.h268 const struct usb_driver *driver; member
285 const struct usb_driver *driver,
/rk3399_ARM-atf/docs/design_documents/
H A Ddtpm_drivers.rst52 The following diagram illustrates the Discrete TPM driver stack for the Raspberry
55 |rpi3 dtpm driver stack|
117 .. |rpi3 dtpm driver stack| image::
H A Dmeasured_boot.rst92 Log driver implemented in TF-A covers later part.
139 driver, and also to write header information in the Event Log
209 measurement using the Measured Boot backend driver.
259 platform helper that wraps it) so that the common Event Log driver
/rk3399_ARM-atf/docs/about/
H A Dfeatures.rst37 - A generic |SCMI| driver to interface with conforming power controllers, for
130 - RSE comms driver ``drivers/arm/rse``
131 - GICv5 driver ``drivers/arm/gicv5`` via ``USE_GIC_DRIVER=5``

123