| /trusted-firmware-a/plat/st/stm32mp1/ |
| A D | stm32mp1_boot_device.c | 132 device->nand_dev->ecc.mode = NAND_ECC_HW; in plat_get_raw_nand_data()
133 device->nand_dev->ecc.size = SZ_512; in plat_get_raw_nand_data()
135 return get_data_from_otp(device->nand_dev, true); in plat_get_raw_nand_data()
145 device->spi_read_cache_op.addr.nbytes = 2U; in plat_get_spi_nand_data()
147 device->spi_read_cache_op.dummy.nbytes = 1U; in plat_get_spi_nand_data()
152 return get_data_from_otp(device->nand_dev, false); in plat_get_spi_nand_data()
157 int plat_get_nor_data(struct nor_device *device) in plat_get_nor_data() argument
159 device->size = SZ_64M; in plat_get_nor_data()
164 device->read_op.addr.nbytes = 3U; in plat_get_nor_data()
166 device->read_op.dummy.nbytes = 1U; in plat_get_nor_data()
[all …]
|
| /trusted-firmware-a/drivers/brcm/emmc/ |
| A D | emmc_csl_sdcard.c | 196 handle->device->ctrl.argReg = 0; in abort_err()
205 handle->device->ctrl.cmdIndex, in abort_err()
211 handle->device->cfg.wfe_retry); in abort_err()
425 handle->device->ctrl.ocr = ocr; in init_mmc_card()
479 handle->device->cfg.blockSize = 512; in init_mmc_card()
505 handle->device->ctrl.rca = 0; in reset_card()
671 if (handle->device->ctrl.cmdStatus) { in write_buffer()
734 if (handle->device->ctrl.cmdStatus) { in read_buffer()
986 handle->device)); in wait_for_event()
1004 handle->device->ctrl.cmdStatus = in wait_for_event()
[all …]
|
| A D | emmc_pboot_hal_memory_drv.c | 59 if (sd_handle->device == 0) { in emmc_partition_select()
134 p_sdhandle->device->cfg.blockSize)) { in bcm_emmc_init()
158 emmc_global_vars_ptr->sdHandle.device = 0; in emmc_deinit()
170 if (sd_handle->device == 0) { in emmc_read()
186 if (sd_handle->device == 0) { in emmc_block_erase()
236 if (sd_handle->device == 0) { in emmc_write()
254 if (sd_handle->device == 0) { in send_sdio_cmd()
480 p_sdhandle->device->cfg.blockSize; in sdio_write()
510 p_sdhandle->device->cfg.blockSize)) { in sdio_write()
532 if (p_sdhandle->device->ctrl.ocr & in sdio_write()
[all …]
|
| A D | emmc_csl_sdcmd.c | 76 handle->device->ctrl.rca = 0x5; in sd_cmd3()
87 handle->device->ctrl.rca = 0; in sd_cmd3()
295 handle->device->cfg.retryLimit); in sd_cmd16()
336 handle->device->cfg.retryLimit); in sd_cmd17()
433 handle->device->ctrl.rca, res); in card_sts_resp()
759 handle->device); in send_cmd()
768 handle->device)); in send_cmd()
792 handle->device); in send_cmd()
828 handle->device)); in send_cmd()
837 handle->device->ctrl.blkReg = 0; in send_cmd()
[all …]
|
| /trusted-firmware-a/docs/resources/diagrams/plantuml/ |
| A D | io_dev_init_and_check.puml | 8 group init and check device (image_id)
20 ref over io_storage : dev_init() on fip device
23 ref over io_storage : io_open() on fip device
26 ref over io_storage : io_close() on fip device
45 ref over io_storage : dev_init() on memmap device
48 ref over io_storage : io_open() on memmap device
51 ref over io_storage : io_close() on memmap device
|
| A D | io_framework_usage_overview.puml | 13 ref over arm_io_storage, io_storage : io device registration
33 ref over arm_io_storage, io_storage : init and check device (BL2_IMAGE_ID)
37 ref over io_storage : io_open() on fip device
40 ref over io_storage : io_size() on fip device
42 ref over io_storage : io_read() on fip device
44 ref over io_storage : io_close() on fip device
46 ref over io_storage : io_dev_close() on fip device
|
| A D | io_dev_registration.puml | 29 opt dev_open() on fip device
43 opt dev_open() on memmap device
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/fconf/ |
| A D | index.rst.txt | 16 platform-defined tables. In the future, it may be provided as part of a device
19 functionality for platforms that cannot / don't want to use device tree.
39 properties originate from a different backend source such as a device tree,
46 captures the hardware topology of the platform from the HW_CONFIG device tree.
49 configuration properties which is usually a device tree file.
90 Loading the property device tree
96 device (FIP).
103 Once a valid device tree is available, the ``fconf_populate(config)`` function
|
| A D | mpmm-bindings.rst.txt | 6 the ``HW_CONFIG`` device tree blob.
|
| A D | fconf_properties.rst.txt | 4 This document describes the device tree format of |FCONF| properties. These
|
| /trusted-firmware-a/docs/components/fconf/ |
| A D | index.rst | 16 platform-defined tables. In the future, it may be provided as part of a device
19 functionality for platforms that cannot / don't want to use device tree.
39 properties originate from a different backend source such as a device tree,
46 captures the hardware topology of the platform from the HW_CONFIG device tree.
49 configuration properties which is usually a device tree file.
90 Loading the property device tree
96 device (FIP).
103 Once a valid device tree is available, the ``fconf_populate(config)`` function
|
| A D | mpmm-bindings.rst | 6 the ``HW_CONFIG`` device tree blob.
|
| A D | fconf_properties.rst | 4 This document describes the device tree format of |FCONF| properties. These
|
| /trusted-firmware-a/docs/components/ |
| A D | ffa-manifest-binding.rst | 1 FF-A manifest binding to device tree
16 minor versions of the device tree binding for the FFA manifest represented
195 - Must be the string "arm,ffa-manifest-device-regions".
199 - Name of the device region e.g. for debugging purposes.
203 - A (address, num-pages) pair describing the device, where:
205 - address: The physical base address <u64> value of the device MMIO
221 identifier is used to inform the partition manager which SMMU the device is
222 upstream of. If the field is omitted then it is assumed that the device is
233 - A list of (id, attributes) pair describing the device interrupts, where:
248 access and ownership of this device's MMIO region.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | ffa-manifest-binding.rst.txt | 1 FF-A manifest binding to device tree
16 minor versions of the device tree binding for the FFA manifest represented
195 - Must be the string "arm,ffa-manifest-device-regions".
199 - Name of the device region e.g. for debugging purposes.
203 - A (address, num-pages) pair describing the device, where:
205 - address: The physical base address <u64> value of the device MMIO
221 identifier is used to inform the partition manager which SMMU the device is
222 upstream of. If the field is omitted then it is assumed that the device is
233 - A list of (id, attributes) pair describing the device interrupts, where:
248 access and ownership of this device's MMIO region.
|
| A D | debugfs-design.rst.txt | 74 (e.g. a hardware device that may not be accessible to non-privileged/
105 - Notice, a physical device driver if exposed by the firmware may conflict with
107 physical device.
|
| /trusted-firmware-a/plat/arm/board/fvp/fdts/ |
| A D | optee_sp_manifest.dts | 35 device-regions {
36 compatible = "arm,ffa-manifest-device-regions";
|
| /trusted-firmware-a/plat/brcm/board/stingray/driver/ |
| A D | usb_phy.c | 504 int32_t usb_phy_init(usb_platform_dev *device) in usb_phy_init() argument
510 phy_info = (usb_phy_t *)device->pcd_id; in usb_phy_init()
537 void usb_phy_shutdown(usb_platform_dev *device) in usb_phy_shutdown() argument
542 phy_info = (usb_phy_t *)device->pcd_id; in usb_phy_shutdown()
564 int32_t usb_xhci_init(usb_platform_dev *device) in usb_xhci_init() argument
568 status = usb_phy_init(device); in usb_xhci_init()
|
| /trusted-firmware-a/include/drivers/ |
| A D | spi_nand.h | 47 int plat_get_spi_nand_data(struct spinand_device *device);
|
| A D | spi_nor.h | 56 int plat_get_nor_data(struct nor_device *device);
|
| /trusted-firmware-a/fdts/ |
| A D | juno-ethosn.dtsi | 8 * For examples of multi-core and multi-device NPU, refer to the examples given in the
|
| A D | corstone700_fvp.dts | 24 device-width= <2>;
|
| /trusted-firmware-a/docs/plat/ |
| A D | stm32mp1.rst | 33 The ROM code boot sequence loads the TF-A binary image from boot device
45 device tree blobs.
54 It can then be copied in the first partition of the boot device.
144 To build TF-A BL32, and its device tree file:
161 with the desired device flag.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | stm32mp1.rst.txt | 33 The ROM code boot sequence loads the TF-A binary image from boot device
45 device tree blobs.
54 It can then be copied in the first partition of the boot device.
144 To build TF-A BL32, and its device tree file:
161 with the desired device flag.
|
| A D | rpi4.rst.txt | 42 The BL31 code will patch the provided device tree blob in memory to advertise
72 But before doing that, it will also load a "kernel" and the device tree into
83 register x0. If the payload has other means of finding the device tree, it
|