Home
last modified time | relevance | path

Searched refs:gets (Results 1 – 25 of 370) sorted by relevance

12345678910>>...15

/linux-5.19.10/Documentation/ABI/testing/
Dsysfs-kernel-mm-damon109 Description: Writing to and reading from this file sets and gets the pid of
126 Description: Writing to and reading from this file sets and gets the start
132 Description: Writing to and reading from this file sets and gets the end
145 Description: Writing to and reading from this file sets and gets the action
151 Description: Writing to and reading from this file sets and gets the mimimum
157 Description: Writing to and reading from this file sets and gets the maximum
163 Description: Writing to and reading from this file sets and gets the manimum
169 Description: Writing to and reading from this file sets and gets the maximum
175 Description: Writing to and reading from this file sets and gets the minimum
181 Description: Writing to and reading from this file sets and gets the maximum
[all …]
Dsysfs-bus-iio-light-tsl258312 This property gets/sets the table of coefficients
Dsysfs-devices-removable19 platform-specific data such as ACPI) and PCI (which gets this
/linux-5.19.10/Documentation/security/tpm/
Dtpm_event_log.rst13 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-5.19.10/arch/arm64/boot/dts/qcom/
Dsc7280-herobrine-villager-r0.dts88 * - If a pin goes to herobrine board and is named it gets that name.
89 * - If a pin goes to herobrine board and is not named, it gets no name.
90 * - If a pin is totally internal to Qcard then it gets Qcard name.
91 * - If a pin is not hooked up on Qcard, it gets no name.
Dsc7280-herobrine-crd.dts141 * - If a pin goes to CRD board and is named it gets that name.
142 * - If a pin goes to CRD board and is not named, it gets no name.
143 * - If a pin is totally internal to Qcard then it gets Qcard name.
144 * - If a pin is not hooked up on Qcard, it gets no name.
Dsc7280-herobrine-herobrine-r1.dts135 * - If a pin goes to herobrine board and is named it gets that name.
136 * - If a pin goes to herobrine board and is not named, it gets no name.
137 * - If a pin is totally internal to Qcard then it gets Qcard name.
138 * - If a pin is not hooked up on Qcard, it gets no name.
/linux-5.19.10/tools/lib/traceevent/Documentation/
Dlibtraceevent-record_parse.txt33 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_.
Dlibtraceevent-host_endian.txt28 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-5.19.10/Documentation/networking/dsa/
Dbcm_sf2.rst46 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-5.19.10/drivers/staging/pi433/Documentation/
Dpi433.txt13 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-5.19.10/Documentation/leds/
Dledtrig-transient.rst11 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
/linux-5.19.10/Documentation/userspace-api/media/dvb/
Dfrontend-stat-properties.rst107 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
/linux-5.19.10/Documentation/vm/
Dactive_mm.rst54 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-5.19.10/tools/perf/tests/
Dmake253 # FIXME nothing gets installed
257 # FIXME nothing gets installed
261 # FIXME nothing gets installed
265 # FIXME nothing gets installed
269 # FIXME nothing gets installed
/linux-5.19.10/fs/unicode/
DKconfig10 be a separate loadable module that gets requested only when a file
/linux-5.19.10/Documentation/livepatch/
Dsystem-state.rst19 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.
/linux-5.19.10/scripts/
Dsubarch.include4 # then ARCH is assigned, getting whatever value it gets normally, and
/linux-5.19.10/drivers/zorro/
DKconfig12 15KB, but it gets freed after the system boots up, so it doesn't
/linux-5.19.10/arch/arm/boot/dts/
Dsun8i-a23-a33.dtsi72 /* 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 */
625 /* compatible gets set in SoC specific dtsi file */
649 /* compatible gets set in SoC specific dtsi file */
681 /* compatible gets set in SoC specific dtsi file */
/linux-5.19.10/Documentation/devicetree/bindings/power/reset/
Dnvmem-reboot-mode.txt3 This driver gets reboot mode magic value from reboot-mode driver
/linux-5.19.10/Documentation/
DKconfig6 It is not uncommon that a document gets renamed.
/linux-5.19.10/Documentation/filesystems/
Dntfs3.rst19 - *system.ntfs_security* gets/sets security
23 - *system.ntfs_attrib* gets/sets ntfs file/dir attributes.
/linux-5.19.10/Documentation/networking/
Dskbuff.rst23 get copied, but caller gets a new metadata struct (struct sk_buff).
/linux-5.19.10/Documentation/driver-api/
Dsync_file.rst53 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

12345678910>>...15