| /rk3399_rockchip-uboot/doc/device-tree-bindings/mailbox/ |
| H A D | mailbox.txt | 1 * Generic Mailbox Controller and client driver bindings 4 assign appropriate mailbox channel to client drivers.
|
| H 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 {
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/pinctrl/ |
| H 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 24 Note that pin controllers themselves may also be client devices of themselves. 27 in a single place, rather than splitting it across multiple client device 30 bindings for the individual client devices in use by that board, i.e. whether 33 == Pinctrl client devices == [all …]
|
| H A D | atmel,at91-pio4-pinctrl.txt | 11 common pinctrl bindings used by client devices.
|
| H A D | rockchip,pinctrl.txt | 9 common pinctrl bindings used by client devices, including the meaning of the
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.android-fastboot | 14 The counterpart to this gadget is the fastboot client which can 42 the fastboot client. The list of vendor IDs supported can be found in the 43 fastboot client source code (fastboot.c) mentioned above. 106 On the client side you can fetch the bootloader version for instance: 114 and once the client comes back, the board should reset. 118 fastboot client wrap the Android suite around it. On OMAP for instance you 119 take zImage kernel and pass it to the fastboot client:
|
| H A D | README.esbc_validate | 11 signature of images (Boot Script and ESBC uboot client). 23 2. ESBC uboot client can be linux. Additionally, rootfs and device
|
| H A D | README.android-fastboot-protocol | 46 3. Data phase. Depending on the command, the host or client will 49 until the client has sent or received the number of bytes indicated 113 by "boot", "ramdisk", "flash", etc. The client 147 The "getvar:%s" command is used to read client variables which
|
| H A D | README.nvme | 13 for enterprise and client solid state drives, typically attached to the PCI 15 address the needs of enterprise and client systems that utilize PCI express
|
| H A D | README.usb | 75 client. In that case your board is pretending to be an Ethernet adapter 192 DHCP client bound to address 172.22.73.81
|
| H A D | README.pxe | 202 When a pxe client retrieves and boots the default pxe file,
|
| H A D | README.odroid | 194 DHCP client bound to address 192.168.1.10 (524 ms)
|
| /rk3399_rockchip-uboot/Documentation/devicetree/bindings/phy/ |
| H A D | no-op.txt | 4 This is useful when the 'client' driver (USB, SATA, ...) uses the PHY framework
|
| /rk3399_rockchip-uboot/drivers/firmware/scmi/ |
| H A D | Kconfig | 16 Communications between agent (client) and the SCMI server are
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/gpio/ |
| H A D | gpio-samsung.txt | 9 - #gpio-cells: Should be 4. The syntax of the gpio specifier used by client nodes
|
| H A D | gpio-pcf857x.txt | 58 bindings used by client devices.
|
| H A D | nvidia,tegra186-gpio.txt | 27 documentation for rationale. Any particular GPIO client is expected to access
|
| /rk3399_rockchip-uboot/drivers/ddr/marvell/a38x/ |
| H A D | ddr3_training_ip.h | 159 u8 client; member
|
| /rk3399_rockchip-uboot/include/ |
| H A D | config_distro_bootcmd.h | 241 #error Please specify an EFI client identifier
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/clock/ |
| H A D | rockchip,rk3288-cru.txt | 20 Each clock is assigned an identifier and client nodes can use this identifier
|
| H A D | rockchip,rk3188-cru.txt | 21 Each clock is assigned an identifier and client nodes can use this identifier
|
| /rk3399_rockchip-uboot/board/bosch/shc/ |
| H A D | README | 94 DHCP client bound to address 192.168.20.91 (258 ms)
|
| /rk3399_rockchip-uboot/board/intel/ |
| H A D | Kconfig | 56 a USB client port.
|
| /rk3399_rockchip-uboot/doc/SPL/ |
| H A D | README.am335x-network | 49 Identifier (VCI) set by BOOTP client (RBL sets VCI to "DM814x ROM v1.0"
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/gpu/ |
| H A D | nvidia,tegra20-host1x.txt | 20 of the following host1x client modules:
|