Home
last modified time | relevance | path

Searched refs:dm (Results 1 – 25 of 64) sorted by relevance

123

/u-boot/doc/api/
A Ddm.rst9 .. kernel-doc:: include/dm/uclass.h
10 .. kernel-doc:: include/dm/root.h
11 .. kernel-doc:: include/dm/lists.h
12 .. kernel-doc:: include/dm/platdata.h
17 .. kernel-doc:: include/dm/device.h
18 .. kernel-doc:: include/dm/devres.h
19 .. kernel-doc:: include/dm/read.h
24 .. kernel-doc:: include/dm/of.h
25 .. kernel-doc:: include/dm/ofnode.h
28 .. kernel-doc:: include/dm/of_addr.h
[all …]
A Dpinctrl.rst6 .. kernel-doc:: include/dm/pinctrl.h
A Dindex.rst11 dm
/u-boot/doc/usage/cmd/
A Ddm.rst3 dm command
11 dm compat
12 dm devres
13 dm drivers
14 dm static
16 dm uclass
25 dm compat
33 dm devres
44 dm drivers
52 dm mem
[all …]
A Dunbind.rst42 => dm tree
69 => dm tree
77 => dm tree
A Dbind.rst45 => dm tree
74 => dm tree
80 => dm tree
A Dut.rst41 test to break. This can sometimes be seen when using 'ut dm' or similar. To
73 dm - driver model
/u-boot/doc/develop/driver-model/
A Dbind.rst35 - <class> is one of the class available in the list given by the "dm uclass"
36 command or first column of "dm tree" command.
37 - <index> is the index of the parent's node (second column of "dm tree" output).
38 - <driver> is the driver name to bind given by the "dm drivers" command or the by
39 the fourth column of "dm tree" output.
/u-boot/doc/develop/
A Dtests_sandbox.rst56 $ ./u-boot -T -c "ut dm gpio"
80 $ ./u-boot -c "ut dm gpio"
106 $ gdb --args u-boot -T -c "ut dm gpio"
110 (gdb) run -T -c "ut dm gpio"
111 Starting program: u-boot -T -c "ut dm gpio"
115 at files/test/dm/gpio.c:37
134 => ut dm -r1000 dm_test_rtc_set_get
159 => ut dm
180 $ ./u-boot -T -c "ut dm -I300:dm_test_host"
191 $ ./u-boot -T -c "ut dm -I75:dm_test_host"
[all …]
/u-boot/doc/device-tree-bindings/firmware/
A Dti,j721e-dm-sci.txt7 - compatible: should be "ti,j721e-dm-sci"
25 dm_tifs: dm-tifs {
26 compatible = "ti,j721e-dm-sci";
/u-boot/arch/mips/mach-jz47xx/jz4780/
A DTODO1 - dm gpio driver
/u-boot/board/sipeed/maix/
A DMAINTAINERS11 F: test/dm/k210_pll.c
/u-boot/test/dm/
A DKconfig5 This enables the 'ut dm' command which runs a series of unit
/u-boot/test/common/
A Devent.c53 test_state->dev = event->data.dm.dev; in h_probe()
/u-boot/test/
A DMakefile18 obj-y += dm/
/u-boot/cmd/
A Ddm.c99 U_BOOT_CMD_WITH_SUBCMDS(dm, "Driver model low level access", dm_help_text,
/u-boot/include/
A Devent.h60 } dm; member
/u-boot/tools/
A Dk3_fit_atf.sh63 dm {
/u-boot/arch/arm/dts/
A Dk3-am62a7-r5-sk.dts63 dm_tifs: dm-tifs {
64 compatible = "ti,j721e-dm-sci";
A Dk3-am625-r5-sk.dts63 dm_tifs: dm-tifs {
64 compatible = "ti,j721e-dm-sci";
A Dk3-am68-sk-r5-base-board.dts88 dm_tifs: dm-tifs {
89 compatible = "ti,j721e-dm-sci";
A Dk3-j721s2-r5-common-proc-board.dts89 dm_tifs: dm-tifs {
90 compatible = "ti,j721e-dm-sci";
/u-boot/doc/imx/clk/
A Dccf.txt75 * For tests the new ./test/dm/clk_ccf.c and ./drivers/clk/clk_sandbox_ccf.c
89 => ut dm clk
92 ./u-boot --fdt arch/sandbox/dts/test.dtb --command "ut dm clk_ccf" -v
/u-boot/doc/android/
A Davb2.rst19 * ``system``/``vendor`` partitions: verifying root hash of dm-verity hashtrees
55 Boot or system/vendor (dm-verity metadata section) is tampered::
/u-boot/doc/usage/
A Dindex.rst48 cmd/dm

Completed in 33 milliseconds

123