Searched refs:probing (Results 1 – 25 of 26) sorted by relevance
12
| /u-boot/drivers/video/stm32/ |
| A D | Kconfig | 32 framebuffer during device-model binding/probing.
41 framebuffer during device-model binding/probing.
50 framebuffer during device-model binding/probing.
|
| /u-boot/drivers/video/rockchip/ |
| A D | Kconfig | 30 framebuffer during device-model binding/probing.
40 framebuffer during device-model binding/probing.
|
| /u-boot/doc/SPI/ |
| A D | status.txt | 8 - sf_probe.c: SPI flash probing code.
|
| A D | README.ti_qspi_am43x_test | 8 - probing the flash device
|
| /u-boot/doc/device-tree-bindings/net/ |
| A D | mdio.txt | 16 requires no compatible property for probing.
|
| /u-boot/arch/arm/dts/ |
| A D | rk3566-anbernic-rgxx3-u-boot.dtsi | 60 * probing to fail so we remove them for U-Boot.
|
| A D | sun50i-h6-pine-h64.dts | 303 * flash and eMMC at the same time, as one of them would fail probing.
|
| A D | rk3288-veyron.dtsi | 672 * Causes jerry to hang when probing bus 0
|
| /u-boot/doc/device-tree-bindings/gpu/ |
| A D | nvidia,tegra20-host1x.txt | 128 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
154 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
190 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
214 - nvidia,ddc-i2c-bus: phandle of an I2C controller used for DDC EDID probing
|
| /u-boot/board/boundary/nitrogen6x/ |
| A D | README | 57 this code auto-detects panel by probing the HDMI Phy for Hot Plug Detect
|
| /u-boot/drivers/mtd/ |
| A D | Kconfig | 46 for probing the capabilities of flash devices. If you wish to
96 for probing the capabilities of flash devices. If you wish to
|
| /u-boot/doc/develop/driver-model/ |
| A D | ethernet.rst | 63 Device probing and instantiation will be handled by the driver model framework,
218 Registering the driver and probing a device is handled very differently,
321 not checking its state or doing random probing.
|
| A D | pci-info.rst | 32 After probing a bus, the available devices will appear in the device tree
|
| A D | design.rst | 763 before probing starts. Thus devices go through two distinct states when
764 probing: reading platform data and actually touching the hardware to bring
767 Having probing separate from ofdata-reading helps deal with of-platdata, where
799 probing them takes time, requires memory, may add delays to the main loop, etc.
944 error probing the device or for any other purpose, lest driver model get
1031 probing devices.
|
| A D | usb-info.rst | 105 driver is actually set up. When probing the bus this structure is
|
| /u-boot/doc/usage/cmd/ |
| A D | bootdev.rst | 54 no error. If you use -p and an error occurs when probing, then this shows
|
| /u-boot/board/ea/ea-lpc3250devkitv2/ |
| A D | README.rst | 152 see what potential devices are found with rudimentary probing on i2c1:
|
| /u-boot/fs/ubifs/ |
| A D | ubifs.h | 657 if (!(c)->probing) \
2053 unsigned int probing:1; member
|
| A D | io.c | 1024 if (!c->probing) { in ubifs_read_node()
|
| A D | super.c | 1348 c->probing = !!(c->vfs_sb->s_flags & MS_SILENT); in mount_ubifs()
1425 c->probing = 0; in mount_ubifs()
|
| /u-boot/drivers/mtd/spi/ |
| A D | Kconfig | 34 standard support for things like probing, read / write, and
|
| /u-boot/drivers/block/ |
| A D | Kconfig | 159 connected is determined by probing.
|
| /u-boot/board/qualcomm/dragonboard820c/ |
| A D | readme.txt | 323 [ 0.000000] psci: probing for conduit method from DT.
|
| /u-boot/doc/board/google/ |
| A D | chromebook_coral.rst | 294 using the SPI driver, to avoid probing PCI and causing an autoconfig, so
|
| /u-boot/drivers/serial/ |
| A D | Kconfig | 139 correctly. With this option set, we make successful probing
151 With this option set, we make probing and searching for
|
Completed in 68 milliseconds
12