Searched full:dummy (Results 1 – 25 of 63) sorted by relevance
123
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-dummy-sink.yaml | 4 $id: http://devicetree.org/schemas/arm/arm,coresight-dummy-sink.yaml#
7 title: ARM Coresight Dummy sink component
17 The Coresight dummy sink component is for the specific coresight sink devices
20 debug and trace capabilities. For this device, a dummy driver is needed to
24 dummy source devices, such as enabling and disabling them. It also provides
25 the Coresight dummy source paths for debugging.
27 The primary use case of the coresight dummy sink is to build path in kernel
28 side for dummy sink component.
40 - arm,coresight-dummy-sink
48 dummy sink, such as Embedded USB debugger(EUD).
[all …]
|
| D | arm,coresight-dummy-source.yaml | 4 $id: http://devicetree.org/schemas/arm/arm,coresight-dummy-source.yaml#
7 title: ARM Coresight Dummy source component
17 The Coresight dummy source component is for the specific coresight source
20 are connected to AP processor via debug bus. For these devices, a dummy driver
22 created in the driver. It provides Coresight API for operations on dummy
24 Coresight dummy source paths for debugging.
26 The primary use case of the coresight dummy source is to build path in kernel
27 side for dummy source component.
39 - arm,coresight-dummy-source
57 # Minimum dummy source definition. Dummy source connect to coresight funnel.
[all …]
|
| D | linux,dummy-virt.yaml | 4 $id: http://devicetree.org/schemas/arm/linux,dummy-virt.yaml#
16 const: linux,dummy-virt
|
| /Documentation/trace/coresight/ |
| D | coresight-dummy.rst | 4 Coresight Dummy Trace Module
13 The Coresight dummy trace module is for the specific devices that kernel don't
15 platforms. For these devices, a dummy driver is needed to register them as
18 It provides Coresight API for operations on dummy devices, such as enabling and
19 disabling them. It also provides the Coresight dummy sink/source paths for
25 There are two types of nodes, dummy sink and dummy source. These nodes
30 $ ls -l /sys/bus/coresight/devices | grep dummy
|
| /Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 11 However, if you want to install a dummy policy for
29 Step 4 will create a new dummy policy valid for your
32 ``dummy`` in ``/etc/selinux/config``, install the compiled policy
33 as ``dummy``, and relabel your filesystem.
|
| /Documentation/ABI/testing/ |
| D | configfs-iio | 29 What: /config/iio/devices/dummy
33 Dummy IIO devices directory. Creating a directory here will result
34 in creating a dummy IIO device in the IIO subsystem.
|
| D | sysfs-bus-wmi | 11 driver_override file (echo wmi-event-dummy > driver_override).
|
| /Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 84 dummy cycles 0
88 dummy cycles 8
92 dummy cycles 8
96 dummy cycles 0
100 dummy cycles 8
104 dummy cycles 4
108 dummy cycles 4
125 dummy cycles 6
|
| /Documentation/i2c/ |
| D | old-module-parameters.rst | 48 # echo dummy 0x2f > /sys/bus/i2c/devices/i2c-1/new_device
51 Of course, it is important to instantiate the ``dummy`` device before loading
52 the driver. The dummy device will be handled by i2c-core itself, preventing
55 pass the name of the device in question instead of ``dummy``.
|
| /Documentation/devicetree/bindings/pci/ |
| D | xlnx,nwl-pcie.yaml | 35 - description: unused interrupt(dummy)
43 - const: dummy
140 interrupt-names = "misc", "dummy", "intx", "msi1", "msi0";
|
| /Documentation/sound/soc/ |
| D | dpcm.rst | 156 .codec_name = "snd-soc-dummy",
157 .codec_dai_name = "snd-soc-dummy-dai",
173 The FE DAI above sets the codec and code DAIs to dummy devices since the BE is
184 .platform_name = "snd-soc-dummy",
224 A BE DAI link can also set the codec to a dummy device if the codec is a device
227 Likewise a BE DAI can also set a dummy cpu DAI if the CPU DAI is managed by the
268 by the ASoC DAPM core. However, if the BE codec or BE DAI is a dummy then this
272 /* BE for codec Headset - DAI0 is dummy and managed by DSP FW */
|
| /Documentation/devicetree/bindings/sound/ |
| D | linux,spdif.yaml | 7 title: Dummy SPDIF Transmitter/Receiver
|
| D | mt2701-cs42448.txt | 8 - mediatek,audio-codec-bt-mrg the phandles of bt-sco dummy codec
|
| /Documentation/userspace-api/media/drivers/ |
| D | imx-uapi.rst | 35 sync by adding 1 dummy line every frame, which causes a rolling effect
46 While the reason for this observation isn't known (the IPU dummy
|
| /Documentation/devicetree/bindings/clock/ |
| D | allwinner,sun4i-a10-cpu-clk.yaml | 48 clocks = <&osc32k>, <&osc24M>, <&pll1>, <&dummy>;
|
| D | allwinner,sun7i-a20-gmac-clk.yaml | 26 The parent clocks shall be fixed rate dummy clocks at 25 MHz and
|
| D | imx31-clock.yaml | 19 dummy 0
|
| D | imx25-clock.yaml | 19 dummy 0
|
| /Documentation/usb/ |
| D | dwc3.rst | 20 to the device. If MSI provides per-endpoint interrupt this dummy
|
| /Documentation/devicetree/bindings/net/ |
| D | xlnx,gmii-to-rgmii.yaml | 58 clocks = <&dummy>;
|
| /Documentation/devicetree/bindings/mfd/ |
| D | netronix,ntxec.yaml | 73 backlight_regulator: regulator-dummy {
|
| /Documentation/trace/ |
| D | stm.rst | 53 These rules can be nested, for example, one can define a rule "dummy"
55 be used for trace sources with the id string of "user/dummy".
|
| /Documentation/networking/devlink/ |
| D | netdevsim.rst | 41 The ``netdevsim`` driver exposes a ``dummy`` region as an example of how the
|
| /Documentation/admin-guide/ |
| D | ldm.rst | 29 dummy MSDOS partition containing one disk-sized partition. This is what is
95 is a dummy MSDOS partition filling the whole disk. You won't be able to mount
|
| /Documentation/leds/ |
| D | leds-mt6370-rgb.rst | 34 "0 Tr1 0 Tr2 0 Tf1 0 Tf2 0 Ton 0 Toff" --> '0' for dummy brightness code
|
123