Searched refs:gets (Results 1 – 25 of 339) sorted by relevance
12345678910>>...14
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/leds/ |
| D | ledtrig-transient.rst | 11 gets deactivated. There is no provision for one time activation to implement
26 routine for the default trigger gets called. During registration of an led
36 that are active at the time driver gets suspended, continue to run, without
50 During trigger unregistration, LED state gets changed to LED_OFF.
56 non-transient state. When driver gets suspended, irrespective of the transient
99 state gets changed to the non-transient state which is the
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 107 This measurement is monotonically increased, as the frontend gets more
135 This measurement is monotonically increased, as the frontend gets more
164 This measurement is monotonically increased, as the frontend gets more
192 This measurement is monotonically increased, as the frontend gets more
213 This measurement is monotonically increased, as the frontend gets more
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/tools/perf/tests/ |
| D | make | 251 # FIXME nothing gets installed
255 # FIXME nothing gets installed
259 # FIXME nothing gets installed
263 # FIXME nothing gets installed
267 # FIXME nothing gets installed
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-light-tsl2583 | 12 This property gets/sets the table of coefficients
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | system-state.rst | 19 This is where the livepatch system state tracking gets useful. It
89 - Modify the system state when the livepatch gets enabled and the state
119 the new code even before the transition gets finished.
|
| /kernel/linux/linux-5.10/drivers/zorro/ |
| D | Kconfig | 12 15KB, but it gets freed after the system boots up, so it doesn't
|
| /kernel/linux/linux-5.10/scripts/ |
| D | subarch.include | 4 # then ARCH is assigned, getting whatever value it gets normally, and
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | nvmem-reboot-mode.txt | 3 This driver gets reboot mode magic value from reboot-mode driver
|
| /kernel/linux/linux-5.10/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 */
278 /* compatible gets set in SoC specific dtsi file */
339 /* compatible gets set in SoC specific dtsi file */
623 /* compatible gets set in SoC specific dtsi file */
647 /* compatible gets set in SoC specific dtsi file */
679 /* compatible gets set in SoC specific dtsi file */
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | Kconfig | 6 It is not uncommon that a document gets renamed.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | wm8962.txt | 13 of R51 (Class D Control 2) gets set, indicating that the speaker is
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/accessibility/speakup/ |
| D | TODO | 12 gets garbled because a lock is not set. This bug happens regularly, but no one
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/cpufreq/ |
| D | nvidia,tegra20-cpufreq.txt | 21 matches, the OPP gets enabled.
|
| /kernel/linux/linux-5.10/Documentation/filesystems/spufs/ |
| D | spu_run.rst | 27 ate(2) to address a specific SPU context. When the context gets sched-
42 gets filled when spu_run returns. It can be one of the following con-
|
| D | spu_create.rst | 29 system (spufs). When spu_create is successful, a directory gets cre-
111 convention, it gets mounted in /spu.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | usb-nop-xceiv.txt | 40 hsusb1_phy is a NOP USB PHY device that gets its clock from an oscillator
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | qlogicfas.rst | 75 realbig.doc realbig.doc". Then do it after the computer gets warm.
80 that it gets a false ACK causing an extra byte to be inserted into the
|
12345678910>>...14