| /u-boot/drivers/firmware/scmi/ |
| A D | sandbox-scmi_devices.c | 36 struct sandbox_scmi_devices devices; member
44 return &priv->devices; in sandbox_scmi_devices_ctx()
51 struct sandbox_scmi_devices *devices = sandbox_scmi_devices_ctx(dev); in sandbox_scmi_devices_remove() local
55 if (!devices) in sandbox_scmi_devices_remove()
59 int ret2 = reset_free(devices->reset + n); in sandbox_scmi_devices_remove()
74 priv->devices = (struct sandbox_scmi_devices){ in sandbox_scmi_devices_probe()
82 ret = clk_get_by_index(dev, n, priv->devices.clk + n); in sandbox_scmi_devices_probe()
90 ret = reset_get_by_index(dev, n, priv->devices.reset + n); in sandbox_scmi_devices_probe()
101 reset_free(priv->devices.reset + n - 1); in sandbox_scmi_devices_probe()
|
| /u-boot/examples/api/ |
| A D | glue.c | 166 static struct device_info devices[UB_MAX_DEV]; variable
185 di = &devices[0]; in ub_dev_enum()
199 di->cookie = devices[n - 1].cookie; in ub_dev_enum()
221 di = &devices[handle]; in ub_dev_open()
236 di = &devices[handle]; in ub_dev_close()
257 if (devices[handle].state != DEV_STA_OPEN) in dev_valid()
268 if (!(devices[handle].type & DEV_TYP_STOR)) in dev_stor_valid()
284 di = &devices[handle]; in ub_dev_read()
299 if (devices[handle].type != DEV_TYP_NET) in dev_net_valid()
313 di = &devices[handle]; in ub_dev_recv()
[all …]
|
| /u-boot/drivers/block/ |
| A D | Kconfig | 2 bool "Support block devices"
6 Enable support for block devices, such as SCSI, MMC and USB
9 devices often have a partition table which allows the device to
16 Some devices require block support whether or not DM is enabled
19 bool "Support block devices in SPL"
23 Enable support for block devices, such as SCSI, MMC and USB
26 devices often have a partition table which allows the device to
31 bool "Support block devices in TPL"
35 Enable support for block devices, such as SCSI, MMC and USB
38 devices often have a partition table which allows the device to
[all …]
|
| /u-boot/drivers/pinctrl/intel/ |
| A D | Kconfig | 22 Enable this if the pinctrl devices are modelled as multiple,
23 separate ACPI devices in the ACPI tables. If enabled, the ACPI
24 devices match the U-Boot pinctrl devices and the pin 'offset' is
26 single ACPI pinctrl device which includes all U-Boot pinctrl devices
|
| /u-boot/doc/device-tree-bindings/misc/misc/ |
| A D | gdsys,io-endpoint.txt | 1 gdsys IO endpoint of IHS FPGA devices
3 The IO endpoint of IHS FPGA devices is a packet-based transmission interface
4 that allows interconnected gdsys devices to send and receive data over the
|
| A D | gdsys,iocon_fpga.txt | 1 gdsys IHS FPGA for CON devices
3 The gdsys IHS FPGA is the main FPGA on gdsys CON devices. This driver provides
|
| A D | gdsys,iocpu_fpga.txt | 1 gdsys IHS FPGA for CPU devices
3 The gdsys IHS FPGA is the main FPGA on gdsys CPU devices. This driver provides
|
| /u-boot/drivers/ufs/ |
| A D | Kconfig | 15 controller present on present TI's J721e devices.
18 bool "Glue Layer driver for UFS on TI J721E devices"
21 present on TI's J721E devices.
|
| /u-boot/doc/ |
| A D | README.virtio | 9 devices, including supported boards, build instructions, driver details etc.
23 spec. While VirtIO devices are commonly implemented as PCI devices on x86,
24 embedded devices models like ARM/RISC-V, which does not normally come with
63 [*] PCI driver for virtio devices
75 VirtIO net and block devices on ARM.
83 On x86, command is slightly different to create PCI VirtIO devices.
116 virtio - virtio block devices sub-system
120 virtio info - show all available virtio block devices
128 To probe all the VirtIO devices, type:
196 for all virtio devices.
[all …]
|
| A D | README.power-framework | 20 devices are now available on the board - namely power managers (PMIC), fuel
22 devices (MFD).
30 Power devices use not only I2C for communication, but SPI as well. Additionally
35 The "flat" hierarchy for power devices works well when each device performs only
39 the master and uses methods exported by other devices. We need to control MUIC
58 The framework classifies devices by their function - separate directories should
59 be maintained for different classes of devices.
66 devices.
92 To charge a battery, information from several "abstract" power devices is
140 Define devices as listed at 1.
[all …]
|
| /u-boot/drivers/dma/ |
| A D | Kconfig | 10 memory copies to and from devices like qspi, ethernet
11 etc Drivers provide methods to access the DMA devices
20 channels which can either transfer data to/from different devices.
35 This driver support data transfer from devices to
36 memory and from memory to devices.
|
| /u-boot/fs/jffs2/ |
| A D | Kconfig | 6 for use with flash memory devices. It supports raw NAND devices,
|
| /u-boot/drivers/fpga/ |
| A D | Kconfig | 12 This provides basic infrastructure to support Altera FPGA devices.
22 This provides common functionality for Gen5 and Arria10 devices.
30 This provides common functionality for Altera Cyclone II devices.
41 This provides common functionality for Intel FPGA devices.
43 devices through SDM (Secure Device Manager) Mailbox.
86 on Xilinx Zynq devices.
|
| /u-boot/drivers/memory/ |
| A D | Kconfig | 2 # Memory devices
13 devices (like SRAM, ethernet adapters, FPGAs, LCD displays, ...) on
23 asynchronuous memory devices like ASRAM, NOR and NAND memory. A total
|
| /u-boot/doc/driver-model/ |
| A D | pci-info.rst | 24 If there is no alias the devices will be numbered sequentially in the device
28 This does a scan of the bus to locate available devices. These devices are
32 After probing a bus, the available devices will appear in the device tree
38 PCI devices can appear in the flattened device tree. If they do, their node
46 Note we must describe PCI devices with the same bus hierarchy as the
48 relationship during PCI bus enumeration thus PCI devices won't be bound to
99 PCIe-to-PCI bridge and all the chipset integrated devices like the PCI UART
100 device are on the PCI bus. Like other devices in the device tree, if we want
101 to bind PCI devices before relocation, "u-boot,dm-pre-reloc" must be declared
104 If PCI devices are not listed in the device tree, U_BOOT_PCI_DEVICE can be used
[all …]
|
| /u-boot/board/freescale/mpc8568mds/ |
| A D | bcsr.c | 15 volatile uint* devices = (uint *)(CONFIG_SYS_CCSRBAR + 0xe0070); in enable_8568mds_duart() local
19 *devices = 0; /* Enable all peripheral devices */ in enable_8568mds_duart()
|
| /u-boot/doc/device-tree-bindings/timer/ |
| A D | fsl,mpc83xx-timer.txt | 1 MPC83xx timer devices
9 provided by one of the "fsl,mpc83xx-clk" devices
|
| /u-boot/doc/device-tree-bindings/axi/ |
| A D | gdsys,ihs_axi.txt | 1 gdsys AXI busses of IHS FPGA devices
4 the connected devices (usually IP cores) can be controlled via software.
|
| /u-boot/drivers/ram/ |
| A D | Kconfig | 33 STM32F7 family devices support flexible memory controller(FMC) to
50 K3 based AM654 devices has DDR memory subsystem that comprises
53 provides an interface to external SDRAM devices. Enabling this
55 SDRAM devices connected to DDR subsystem.
64 devices which can be utilized for storing program or data.
72 i.MXRT family devices support smart external memory controller(SEMC)
|
| /u-boot/drivers/bus/ |
| A D | Kconfig | 6 menu "Bus devices"
27 needed to use on-board devices connected to UniPhier SoCs.
|
| /u-boot/doc/device-tree-bindings/pwm/ |
| A D | pwm.txt | 1 Specifying PWM information for devices
7 PWM users should specify a list of PWM devices that they want to use
19 each of the PWM devices listed in the "pwms" property. If no "pwm-names"
22 Drivers for devices that use more than a single PWM device can use the
|
| /u-boot/board/freescale/ls1021aiot/ |
| A D | README | 10 devices(32-bit bus) with 4 bit ECC
11 - DDR power supplies 1.35V to all devices with
26 - Support for SDIO devices
|
| /u-boot/doc/android/ |
| A D | boot-image.rst | 21 * v0: it's called *legacy* boot image header; used in devices launched before
24 * v1: used in devices launched with Android 9; adds ``recovery_dtbo`` field,
25 which should be used for non-A/B devices in ``recovery.img`` (see [2]_ for
27 * v2: used in devices launched with Android 10; adds ``dtb`` field, which
148 .. [1] https://source.android.com/devices/bootloader/boot-image-header
149 .. [2] https://source.android.com/devices/bootloader/recovery-image
150 .. [3] https://source.android.com/devices/architecture/dto/partitions
154 .. [7] https://source.android.com/devices/bootloader
|
| /u-boot/doc/device-tree-bindings/memory-controllers/ |
| A D | k3-am654-ddrss.txt | 4 K3 based AM654 devices has DDR memory subsystem that comprises
7 provides an interface to external SDRAM devices. This DDRSS driver
8 adds support for the initialization of the external SDRAM devices by
|
| /u-boot/drivers/video/stm32/ |
| A D | Kconfig | 14 devices which have RGB TFT or DSI display connected.
23 devices which have DSI devices connected.
|