Searched full:generated (Results 1 – 25 of 345) sorted by relevance
12345678910>>...14
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-dqevent.rst | 144 - Generated when the CEC Adapter's state changes. When open() is
145 called an initial event will be generated for that filehandle with
151 - Generated if one or more CEC messages were lost because the
157 - Generated if the CEC pin goes from a high voltage to a low voltage.
164 - Generated if the CEC pin goes from a low voltage to a high voltage.
171 - Generated if the HPD pin goes from a high voltage to a low voltage.
174 if the HPD is low, then an initial event will be generated for that
180 - Generated if the HPD pin goes from a low voltage to a high voltage.
183 if the HPD is high, then an initial event will be generated for that
189 - Generated if the 5V pin goes from a high voltage to a low voltage.
[all …]
|
| /Documentation/filesystems/ |
| D | gfs2-uevents.rst | 7 During the lifetime of a GFS2 mount, a number of uevents are generated.
18 uevent generated by the newly created filesystem. If the mount
30 The ONLINE uevent is generated after a successful mount or remount. It
34 be generated by older kernels.
48 success (or otherwise) of the operation. These uevents are generated
63 The OFFLINE uevent is only generated due to filesystem errors and is used
71 The REMOVE uevent is generated at the end of an unsuccessful mount
74 and unlike the other uevents is generated automatically by the kernel's
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 20 The kernel version that generated the dump (UTS_RELEASE).
23 The module that generated the crashdump.
29 Comm string for the binary that generated the fault.
32 Command line for the binary that generated the fault.
35 ID of the GPU that generated the crash formatted as
|
| /Documentation/arm/samsung/ |
| D | clksrc-change-registers.awk | 128 generated = mask
129 sub(reg_src, reg_div, generated)
136 printf "/* generated " generated " */\n"
142 printf ".shift = " dmask[generated,1] ", "
143 printf ".size = " dmask[generated,0] ", "
|
| /Documentation/core-api/ |
| D | memory-hotplug.rst | 15 Generated before new memory becomes available in order to be able to
20 Generated if MEM_GOING_ONLINE fails.
23 Generated when memory has successfully brought online. The callback may
27 Generated to begin the process of offlining memory. Allocations are no
33 Generated if MEM_GOING_OFFLINE fails. Memory is available again from
37 Generated after offlining memory is complete.
|
| /Documentation/devicetree/bindings/clock/ |
| D | pistachio-clock.txt | 30 "audio_clk_in_gate", "enet_clk_in_gate" which are generated by the
48 peripherals. The peripheral system clock ("periph_sys") generated by the core
58 - clock-names: Must include "periph_sys", the peripheral system clock generated
76 control registers. The system clock ("sys") generated by the peripheral clock
86 - clock-names: Must include "sys", the system clock generated by the peripheral
|
| D | samsung,s3c2412-clock.txt | 24 There are several clocks that are generated outside the SoC. It is expected
38 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rk3036-cru.txt | 28 There are several clocks that are generated outside the SoC. It is expected
46 Example: UART controller node that consumes the clock generated by the clock
|
| D | actions,owl-cmu.txt | 28 The hosc clock used as input for the plls is generated outside the SoC. It is
44 Example: UART controller node that consumes clock generated by the clock
|
| D | samsung,s3c2410-clock.txt | 27 The xti clock used as input for the plls is generated outside the SoC. It is
39 Example: UART controller node that consumes the clock generated by the clock
|
| D | samsung,s3c2443-clock.txt | 27 There are several clocks that are generated outside the SoC. It is expected
43 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rk3228-cru.txt | 28 There are several clocks that are generated outside the SoC. It is expected
48 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rk3128-cru.txt | 30 There are several clocks that are generated outside the SoC. It is expected
48 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rk3328-cru.txt | 28 There are several clocks that are generated outside the SoC. It is expected
48 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rv1108-cru.txt | 28 There are several clocks that are generated outside the SoC. It is expected
49 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rk3308-cru.txt | 28 There are several clocks that are generated outside the SoC. It is expected
48 Example: UART controller node that consumes the clock generated by the clock
|
| D | rockchip,rk3368-cru.txt | 28 There are several clocks that are generated outside the SoC. It is expected
51 Example: UART controller node that consumes the clock generated by the clock
|
| /Documentation/devicetree/bindings/ipmi/ |
| D | aspeed-kcs-bmc.txt | 12 - interrupts : interrupt generated by the controller
22 - interrupts : interrupt generated by the controller
|
| /Documentation/devicetree/bindings/sound/ |
| D | brcm,bcm63xx-audio.txt | 12 - "i2sclk" (generated clock) Required.
15 (1) : The generated clock is required only when any of TX and RX
|
| D | mchp-i2s-mcc.txt | 16 - "gclk" (generated clock) Optional (1).
23 (1) : Only the peripheral clock is required. The generated clock is optional
|
| D | atmel-i2s.txt | 17 - "gclk" (generated clock) Optional (1).
25 (1) : Only the peripheral clock is required. The generated clock and the I2S
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 6 file using a randomly generated File Encryption Key (FEK).
25 authentication token in its payload with a FEKEK randomly generated by the
34 required key can be securely generated by an Administrator and provided at boot
|
| /Documentation/w1/ |
| D | w1-netlink.rst | 10 1. Events. They are generated each time a new master or slave device
75 Currently replies to userspace commands are only generated for read
76 command request. One reply is generated exactly for one w1_netlink_cmd
147 If reply is generated for master or root command (which do not have
157 Status reply is generated for every w1_netlink_cmd embedded in the
159 reply will be generated for the w1_netlink_msg.
|
| /Documentation/ABI/testing/ |
| D | sysfs-uevent | 7 are generated by writing /sys/.../uevent file.
28 If UUID is not passed in, the generated synthetic uevent gains
|
| D | evm | 11 an HMAC-sha1 generated locally with a
14 generated either locally or remotely using an
96 to be added at runtime. Any signatures generated after
|
12345678910>>...14