Searched refs:gets (Results 1 – 25 of 306) sorted by relevance
12345678910>>...13
| /Linux-v5.4/Documentation/security/tpm/ |
| D | tpm_event_log.rst | 13 The preboot firmware maintains an event log that gets new entries every
14 time something gets hashed by it to any of the PCR registers. The events
41 out this issue. Events gets mirrored to this table after the first time
42 EFI_TCG2_PROTOCOL.GetEventLog() gets called.
45 before the Linux EFI stub gets to run. Thus, it needs to calculate and save the
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-record_parse.txt | 33 The _tep_data_type()_ function gets the event id from the record _rec_.
37 The _tep_data_pid()_ function gets the process id from the record _rec_.
41 The _tep_data_preempt_count()_ function gets the preemption count from the
45 The _tep_data_flags()_ function gets the latency flags from the record _rec_.
|
| D | libtraceevent-host_endian.txt | 28 The _tep_is_bigendian()_ gets the endianness of the machine, executing
31 The _tep_is_local_bigendian()_ function gets the endianness of the local
|
| /Linux-v5.4/Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 46 which gets inserted by the switch for every packet forwarded to the CPU
58 provided in ``net/dsa/dsa.c``. The reason for that is because the DSA subsystem gets
83 gets loaded onto the MoCA processor(s) for packet processing. The switch
85 the MoCA interface whenever the MoCA coaxial cable gets disconnected or the
86 firmware gets reloaded. The SF2 driver relies on such events to properly set its
113 capabilities is done and the intersection result gets configured. During
|
| /Linux-v5.4/arch/mips/include/asm/ |
| D | pmon.h | 22 char* (*gets) (char*); member
40 #define pmon_gets(s) debug_vectors->gets(s)
|
| /Linux-v5.4/drivers/staging/pi433/Documentation/ |
| D | pi433.txt | 13 until something gets received terminates the read request.
29 corresponding parameter set gets written to the kfifo.
31 kfifo is empty. If not, it gets one set of config and data from the kfifo. If
33 the air, the rf module is set to standby, the parameters for transmission gets
34 set, the hardware fifo of the rf chip gets preloaded and the transmission gets
35 started. Upon hardware fifo threshold interrupt it gets reloaded, thus enabling
45 configuration set is written to the rf module and it gets set into receiving mode.
51 dynamically. Upon each hardware fifo threshold interrupt, a portion of data gets
185 time the receiver gets more and more sensitive. This value
|
| /Linux-v5.4/Documentation/leds/ |
| D | ledtrig-transient.rst | 11 gets deactivated. There is no provision for one time activation to implement
32 routine for the default trigger gets called. During registration of an led
42 that are active at the time driver gets suspended, continue to run, without
56 During trigger unregistration, LED state gets changed to LED_OFF.
62 non-transient state. When driver gets suspended, irrespective of the transient
105 state gets changed to the non-transient state which is the
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-light | 42 This property gets/sets the last known external
49 This property gets/sets the sensors ADC analog integration time.
55 This property gets/sets the table of coefficients
|
| /Linux-v5.4/tools/perf/tests/ |
| D | make | 237 # FIXME nothing gets installed
241 # FIXME nothing gets installed
245 # FIXME nothing gets installed
249 # FIXME nothing gets installed
253 # FIXME nothing gets installed
|
| /Linux-v5.4/Documentation/media/uapi/dvb/ |
| D | frontend-stat-properties.rst | 114 This measurement is monotonically increased, as the frontend gets more
142 This measurement is monotonically increased, as the frontend gets more
171 This measurement is monotonically increased, as the frontend gets more
199 This measurement is monotonically increased, as the frontend gets more
220 This measurement is monotonically increased, as the frontend gets more
|
| /Linux-v5.4/Documentation/ |
| D | Kconfig | 6 It is not uncommon that a document gets renamed.
|
| /Linux-v5.4/Documentation/vm/ |
| D | active_mm.rst | 54 anonymous process gets scheduled away, the borrowed address space is
66 gets scheduled away in favour of a real thread, the "zombie" mm gets
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-tsl2583 | 12 This property gets/sets the table of coefficients
|
| /Linux-v5.4/scripts/ |
| D | subarch.include | 4 # then ARCH is assigned, getting whatever value it gets normally, and
|
| /Linux-v5.4/drivers/zorro/ |
| D | Kconfig | 12 15KB, but it gets freed after the system boots up, so it doesn't
|
| /Linux-v5.4/Documentation/devicetree/bindings/sram/ |
| D | rockchip-smp-sram.txt | 5 of the cores. Once the core gets powered up it executes the code that is
|
| D | samsung-sram.txt | 5 of the secondary cores. Once the core gets powered up it executes the
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/reset/ |
| D | nvmem-reboot-mode.txt | 3 This driver gets reboot mode magic value from reboot-mode driver
|
| D | syscon-reboot-mode.txt | 3 This driver gets reboot mode magic value form reboot-mode driver
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | sun8i-a23-a33.dtsi | 72 /* compatible gets set in SoC specific dtsi file */
182 /* compatible gets set in SoC specific dtsi file */
273 /* compatible gets set in SoC specific dtsi file */
334 /* compatible gets set in SoC specific dtsi file */
618 /* compatible gets set in SoC specific dtsi file */
642 /* compatible gets set in SoC specific dtsi file */
674 /* compatible gets set in SoC specific dtsi file */
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/amlogic/ |
| D | smp-sram.txt | 5 Once the core gets powered up it executes the code that is residing at a
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | wm8962.txt | 13 of R51 (Class D Control 2) gets set, indicating that the speaker is
|
| D | wm8960.txt | 13 R24 (Additional control 2) gets set, indicating that ADCLRC and DACLRC pins
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | sync_file.rst | 53 The caller pass the out-fence and gets back the sync_file. That is just the
54 first step, next it needs to install an fd on sync_file->file. So it gets an
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | bus.rst | 91 Each bus gets a directory in the bus directory, along with two default
109 Each device that is discovered on a bus of that type gets a symlink in
|
12345678910>>...13
