Searched refs:identify (Results 1 – 16 of 16) sorted by relevance
| /u-boot/doc/ |
| A D | README.fsl-dpaa | 9 so we introduce CONFIG_FSL_FM_10GEC_REGULAR_NOTATION to identify the new SoCs on
|
| A D | README.LED | 23 CONFIG_STATUS_LED_BIT is passed into the __led_* functions to identify which LED
|
| A D | README.Heterogeneous-SoCs | 34 Added top level CONFIG to identify presence of HETEROGENUOUS clusters
|
| A D | README.usb | 170 The 'usb start' command should identify the adapter something like this:
|
| /u-boot/doc/device-tree-bindings/pci_endpoint/ |
| A D | cdns,cdns-pcie-ep.txt | 4 - compatible: Should contain "cdns,cdns-pcie-ep" to identify the IP used.
|
| /u-boot/drivers/soc/ |
| A D | Kconfig | 16 This allows Texas Instruments Keystone 3 SoCs to identify
|
| /u-boot/drivers/led/ |
| A D | Kconfig | 126 CONFIG_LED_STATUS_BIT is passed into the __led_* functions to identify
161 identify which LED is being acted on. As such, the chosen value must
196 identify which LED is being acted on. As such, the chosen value must
231 identify which LED is being acted on. As such, the chosen value must
266 identify which LED is being acted on. As such, the chosen value must
301 identify which LED is being acted on. As such, the chosen value must
|
| /u-boot/drivers/nvme/ |
| A D | nvme.c | 463 c.identify.opcode = nvme_admin_identify; in nvme_identify()
464 c.identify.nsid = cpu_to_le32(nsid); in nvme_identify()
465 c.identify.prp1 = cpu_to_le64(dma_addr); in nvme_identify()
469 c.identify.prp2 = 0; in nvme_identify()
472 c.identify.prp2 = cpu_to_le64(dma_addr); in nvme_identify()
475 c.identify.cns = cpu_to_le32(cns); in nvme_identify()
|
| A D | nvme.h | 456 struct nvme_identify identify; member
|
| /u-boot/doc/uImage.FIT/ |
| A D | multi_spl.its | 9 * is used to identify images to be loaded into memory. If falcon boot is
|
| A D | source_file_format.txt | 87 To identify FIT sub-nodes representing images, hashes, configurations (which
300 identify which format is used.
|
| A D | signature.txt | 580 GnuPG needs to construct a user ID to identify your key.
|
| /u-boot/doc/develop/ |
| A D | menus.rst | 14 Menus are composed of items. Each item has a key used to identify it in
|
| /u-boot/common/spl/ |
| A D | Kconfig | 787 bool "Use chip ID to identify NAND flash"
789 SPL uses the chip ID list to identify the NAND flash.
921 sent by the client to identify the vendor type and configuration
|
| /u-boot/drivers/net/ |
| A D | Kconfig | 211 adapters. For more information on how to identify your adapter, go
|
| /u-boot/ |
| A D | README | 2209 SPL uses the chip ID list to identify the NAND flash.
2929 are used to identify the storage device (NOR flash, SPI, etc) and the address
2973 are used to identify the storage device (NOR flash, SPI, etc) and the address
|
Completed in 23 milliseconds