| /u-boot/drivers/pci/ |
| A D | pci-emul-uclass.c | 40 upriv->client = dev; in sandbox_pci_get_emul()
56 if (!upriv->client) in sandbox_pci_get_client()
58 *devp = upriv->client; in sandbox_pci_get_client()
|
| /u-boot/doc/device-tree-bindings/mailbox/ |
| A D | mailbox.txt | 1 * Generic Mailbox Controller and client driver bindings
4 assign appropriate mailbox channel to client drivers.
|
| A D | nvidia,tegra186-hsp.txt | 32 The mbox specifier of the "mboxes" property in the client node should
34 one should be the ID that the client is going to use. Those information
49 client {
|
| A D | k3-secure-proxy.txt | 31 client:
|
| /u-boot/doc/device-tree-bindings/pinctrl/ |
| A D | pinctrl-bindings.txt | 9 designated client devices. Again, each client device must be represented as a
12 For a client device to operate correctly, certain pin controllers must
13 set up certain specific pin configurations. Some client devices need a
16 device is inactive. Hence, each client device can define a set of named
17 states. The number and names of those states is defined by the client device's
21 for client device device tree nodes to map those state names to the pin
27 in a single place, rather than splitting it across multiple client device
33 == Pinctrl client devices ==
35 For each client device individually, every pin state is assigned an integer
41 Each client device's own binding determines the set of states that must be
[all …]
|
| A D | bcm6838-pinctrl.txt | 10 common pinctrl bindings used by client devices.
|
| A D | nexell,s5pxx18-pinctrl.txt | 10 common pinctrl bindings used by client devices, including the meaning of the
73 - used by client devices
|
| A D | intel,apl-pinctrl.txt | 12 common pinctrl bindings used by client devices.
|
| A D | marvell,armada-37xx-pinctrl.txt | 12 common pinctrl bindings used by client devices, including the meaning
144 and the common GPIO bindings used by client devices.
|
| /u-boot/arch/arm/dts/ |
| A D | kirkwood-openrd-client.dts | 8 * client variant of the Marvell Kirkwood Development Board.
17 …compatible = "marvell,openrd-client", "marvell,openrd", "marvell,kirkwood-88f6281", "marvell,kirkw…
|
| /u-boot/doc/android/ |
| A D | fastboot.rst | 37 The counterpart to this is the fastboot client which can be found in
39 folder. It runs on Windows, Linux and OSX. The fastboot client is
59 supported by the fastboot client. The list of vendor IDs supported can
60 be found in the fastboot client source code.
190 On the client side you can fetch the bootloader version for instance::
200 and once the client comes back, the board should reset.
204 fastboot client wrap the Android suite around it. On OMAP for instance you
205 take zImage kernel and pass it to the fastboot client::
|
| A D | fastboot-protocol.rst | 47 3. Data phase. Depending on the command, the host or client will
50 until the client has sent or received the number of bytes indicated
118 by "boot", "ramdisk", "flash", etc. The client
155 The ``getvar:%s`` command is used to read client variables which
|
| /u-boot/doc/device-tree-bindings/phy/ |
| A D | no-op.txt | 4 This is useful when the 'client' driver (USB, SATA, ...) uses the PHY framework
|
| /u-boot/arch/arm/mach-socfpga/include/mach/ |
| A D | mailbox_s10.h | 44 #define MBOX_CMD_HEADER(client, id, len, indirect, cmd) \ argument
49 (((client) << MBOX_HDR_CLIENT_LSB) & MBOX_HDR_CLIENT_MSK))
|
| /u-boot/doc/ |
| A D | README.esbc_validate | 10 signature of images (Boot Script and ESBC uboot client).
22 2. ESBC uboot client can be linux. Additionally, rootfs and device
|
| A D | README.nvme | 11 for enterprise and client solid state drives, typically attached to the PCI
13 address the needs of enterprise and client systems that utilize PCI express
|
| A D | README.tee | 25 A client finds the TEE device via tee_find_device(). Other important functions
31 - tee_get_version() lets the client know which the capabilities of the TEE
|
| /u-boot/configs/ |
| A D | openrd_client_defconfig | 12 CONFIG_DEFAULT_DEVICE_TREE="kirkwood-openrd-client"
|
| /u-boot/drivers/firmware/scmi/ |
| A D | Kconfig | 16 Communications between agent (client) and the SCMI server are
|
| /u-boot/doc/device-tree-bindings/gpio/ |
| A D | gpio-samsung.txt | 9 - #gpio-cells: Should be 4. The syntax of the gpio specifier used by client nodes
|
| A D | intel,apl-gpio.txt | 8 - #gpio-cells: Should be 2. The syntax of the gpio specifier used by client
|
| /u-boot/drivers/firmware/ |
| A D | Kconfig | 27 This protocol library is used by client drivers to use the features
|
| /u-boot/drivers/ddr/marvell/a38x/ |
| A D | ddr3_training_ip.h | 129 u8 client; member
|
| /u-boot/doc/device-tree-bindings/clock/ |
| A D | snps,hsdk-cgu.txt | 13 Each clock is assigned an identifier and client nodes can use this identifier
|
| /u-boot/doc/device-tree-bindings/interrupt-controller/ |
| A D | interrupts.txt | 4 1) Interrupt client nodes
22 interrupt client node or in any of its parent nodes. Interrupts listed in the
|