Home
last modified time | relevance | path

Searched refs:devices (Results 1 – 25 of 354) sorted by relevance

12345678910>>...15

/u-boot/drivers/firmware/scmi/
A Dsandbox-scmi_devices.c41 struct sandbox_scmi_devices devices; member
49 return &priv->devices; in sandbox_scmi_devices_ctx()
56 struct sandbox_scmi_devices *devices = sandbox_scmi_devices_ctx(dev); in sandbox_scmi_devices_remove() local
60 if (!devices) in sandbox_scmi_devices_remove()
64 int ret2 = reset_free(devices->reset + n); in sandbox_scmi_devices_remove()
79 priv->devices = (struct sandbox_scmi_devices){ in sandbox_scmi_devices_probe()
89 ret = clk_get_by_index(dev, n, priv->devices.clk + n); in sandbox_scmi_devices_probe()
97 ret = reset_get_by_index(dev, n, priv->devices.reset + n); in sandbox_scmi_devices_probe()
111 priv->devices.regul + n); in sandbox_scmi_devices_probe()
124 reset_free(priv->devices.reset + n - 1); in sandbox_scmi_devices_probe()
/u-boot/examples/api/
A Dglue.c166 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/pinctrl/intel/
A DKconfig22 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/drivers/block/
A DKconfig2 bool # "Support block devices"
7 Enable support for block devices, such as SCSI, MMC and USB
23 devices consisting of 'struct blk_desc' records.
26 bool "Support block devices in SPL"
30 Enable support for block devices, such as SCSI, MMC and USB
38 bool "Support block devices in TPL"
49 bool "Support block devices in VPL"
71 bool "Composable virtual block devices (blkmap)"
129 devices, for example.
153 hex "Maximum number of IDE devices"
[all …]
/u-boot/doc/usage/cmd/
A Dconinfo.rst17 devices and their assignment as stdin, stdout, stderr console devices.
29 List of available devices
38 List of available devices
/u-boot/doc/device-tree-bindings/misc/misc/
A Dgdsys,io-endpoint.txt1 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 Dgdsys,iocon_fpga.txt1 gdsys IHS FPGA for CON devices
3 The gdsys IHS FPGA is the main FPGA on gdsys CON devices. This driver provides
A Dgdsys,iocpu_fpga.txt1 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/clk/ti/
A DKconfig46 bool "PLL clock support for K3 SoC family of devices"
49 Enables PLL clock support for K3 SoC family of devices.
52 bool "PLL clock support for K3 SoC family of devices"
55 Enables PLL clock support for K3 SoC family of devices.
58 bool "Clock support for K3 SoC family of devices"
64 bool "Clock support for K3 SoC family of devices"
/u-boot/drivers/ufs/
A DKconfig16 controller present on present TI's J721e devices.
19 bool "Glue Layer driver for UFS on TI J721E devices"
22 present on TI's J721E devices.
/u-boot/doc/develop/driver-model/
A Dvirtio.rst8 devices, including supported boards, build instructions, driver details etc.
22 spec. While VirtIO devices are commonly implemented as PCI devices on x86,
23 embedded devices models like ARM/RISC-V, which does not normally come with
66 [*] PCI driver for virtio devices
78 VirtIO net and block devices on ARM.
88 On x86, command is slightly different to create PCI VirtIO devices.
129 virtio - virtio block devices sub-system
133 virtio info - show all available virtio block devices
141 To probe all the VirtIO devices, type:
217 for all virtio devices.
[all …]
A Dnvmxip.rst9 Non-Volatile Memory devices with addressable memory (e.g: QSPI NOR flash) could
39 For example, if we have two NVMXIP devices described in the DT
40 The devices hierarchy is as follows:
66 on top of a direct access non volatile memory XIP flash devices.
70 multiple flash devices at the same time.
74 Any platform that needs to emulate one or multiple QSPI XIP flash devices can turn this
82 Multiple QSPI XIP flash devices can be used at the same time by describing them through DT
A Dpci-info.rst24 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, "bootph-all" must be declared
104 If PCI devices are not listed in the device tree, U_BOOT_PCI_DEVICE can be used
[all …]
/u-boot/drivers/memory/
A DKconfig2 # Memory devices
11 Enable driver model for Memory Controller devices.
12 These devices provide Memory bus interface to various devices like
37 devices (like SRAM, ethernet adapters, FPGAs, LCD displays, ...) on
47 asynchronuous memory devices like ASRAM, NOR and NAND memory. A total
/u-boot/doc/arch/sandbox/
A Dblock_impl.rst5 Sandbox block devices (implementation)
10 Sandbox block devices are implemented using the `UCLASS_HOST` uclass. Only one
11 driver is provided (`host_sb_drv`) so all devices in the uclass use the same
30 There is no arbitrary limit to the number of host devices that can be created.
/u-boot/drivers/ata/
A DKconfig15 other storage devices.
28 Sets the maximum number of ports to scan when looking for devices.
37 bool "Enable SCSI interface to SATA devices"
40 Enable this to allow interfacing SATA devices via the SCSI layer.
66 Enable this driver to support Sata devices through
87 Enable this driver to support Sata devices through
118 ZynqMP. Support up to 2 external devices. Compliant with SATA 3.1 and
155 int "Maximum number of SATA devices"
158 Sets the maximum number of SATA devices which can be supported
/u-boot/doc/
A DREADME.power-framework20 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/fuzz/
A DKconfig2 bool "Driver support for fuzzing engine devices"
5 Enable driver model for fuzzing engine devices. This interface is
/u-boot/drivers/ram/
A DKconfig33 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.
76 devices which can be utilized for storing program or data.
86 devices which can be utilized for storing program or data.
95 subsystem is used to provide an interface to external SDRAM devices
106 i.MXRT family devices support smart external memory controller(SEMC)
/u-boot/drivers/fwu-mdata/
A DKconfig10 bool "FWU Metadata access for GPT partitioned Block devices"
16 block devices.
/u-boot/doc/device-tree-bindings/timer/
A Dfsl,mpc83xx-timer.txt1 MPC83xx timer devices
9 provided by one of the "fsl,mpc83xx-clk" devices
/u-boot/doc/device-tree-bindings/axi/
A Dgdsys,ihs_axi.txt1 gdsys AXI busses of IHS FPGA devices
4 the connected devices (usually IP cores) can be controlled via software.
/u-boot/drivers/fpga/
A DKconfig12 This provides basic infrastructure to support Altera FPGA devices.
22 This provides common functionality for Gen5 and Arria10 devices.
48 This provides common functionality for Altera Cyclone II devices.
59 This provides common functionality for Intel FPGA devices.
61 devices through SDM (Secure Device Manager) Mailbox.
120 on Xilinx Zynq devices.
154 Enable driver model for Field-Programmable Gate Array (FPGA) devices.
155 The devices cover a wide range of applications and are configured at
169 int "Maximum number of FPGA devices"
/u-boot/doc/android/
A Dboot-image.rst21 * 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
30 * v3: used in devices launched with Android 11; adds ``vendor_boot`` partition
35 * v4: used in devices launched with Android 12; provides a boot signature in boot
158 .. [1] https://source.android.com/devices/bootloader/boot-image-header
159 .. [2] https://source.android.com/devices/bootloader/recovery-image
160 .. [3] https://source.android.com/devices/architecture/dto/partitions
164 .. [7] https://source.android.com/devices/bootloader
/u-boot/drivers/dma/
A DKconfig10 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.

Completed in 734 milliseconds

12345678910>>...15