Home
last modified time | relevance | path

Searched full:expose (Results 1 – 25 of 1196) sorted by relevance

12345678910>>...48

/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-tty29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
Dsysfs-ibft5 files that expose the iSCSI Boot Firmware Table initiator data.
12 files that expose the iSCSI Boot Firmware Table target data.
22 files that expose the iSCSI Boot Firmware Table NIC data.
29 that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-tty29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
Dsysfs-ibft5 files that expose the iSCSI Boot Firmware Table initiator data.
12 files that expose the iSCSI Boot Firmware Table target data.
22 files that expose the iSCSI Boot Firmware Table NIC data.
29 that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the
/kernel/linux/linux-6.6/drivers/usb/typec/ucsi/
DKconfig34 This driver enables UCSI support on platforms that expose a
44 This driver enables UCSI support on platforms that expose UCSI
56 This driver enables UCSI support on platforms that expose a STM32G0
66 This driver enables UCSI support on platforms that expose UCSI
/kernel/linux/linux-6.6/drivers/soc/amlogic/
DKconfig37 Say yes to expose Amlogic Meson GX Power Domains as
48 Say yes to expose Amlogic Meson Everything-Else Power Domains as
61 Say yes to expose Amlogic Meson Secure Power Domains as Generic
/kernel/linux/linux-5.10/drivers/soc/amlogic/
DKconfig37 Say yes to expose Amlogic Meson GX Power Domains as
48 Say yes to expose Amlogic Meson Everything-Else Power Domains as
61 Say yes to expose Amlogic Meson Secure Power Domains as Generic
/kernel/linux/linux-6.6/drivers/soundwire/
Ddmi-quirks.c19 * Some TigerLake devices based on an initial Intel BIOS do not expose
36 * The initial version of the Dell SKU 0A3E did not expose the devices
59 * The HP Omen 16-k0005TX does not expose the correct version of RT711 on link0
60 * and does not expose a RT1316 on link3
/kernel/linux/linux-6.6/drivers/firmware/google/
DKconfig28 BIOS. These data structures expose things like the verified
33 kernel to search for Coreboot CBMEM entries, and expose the
81 This option enables the kernel to expose the content of Google VPD
/kernel/linux/linux-6.6/drivers/iommu/
Diommu-debugfs.c20 * Provide base enablement for using debugfs to expose internal data of an
29 * to expose internal data.
41 pr_warn("** This means that this kernel is built to expose internal **\n"); in iommu_debugfs_setup()
/kernel/linux/linux-5.10/drivers/iommu/
Diommu-debugfs.c20 * Provide base enablement for using debugfs to expose internal data of an
29 * to expose internal data.
41 pr_warn("** This means that this kernel is built to expose internal **\n"); in iommu_debugfs_setup()
/kernel/linux/linux-5.10/drivers/clk/meson/
Dg12a-aoclk.h14 * It has now been decided to expose everything by default in the DT header:
16 * to expose, such as the internal muxes and dividers of composite clocks,
/kernel/linux/linux-5.10/drivers/remoteproc/
Dremoteproc_debugfs.c41 /* Expose the current coredump configuration via debugfs */
119 * memory buffer. We expose this trace buffer using debugfs, so users
154 /* expose the name of the remote processor via debugfs */
174 /* expose recovery flag via debugfs */
250 /* expose the crash trigger via debugfs */
274 /* Expose resource table content via debugfs */
361 /* Expose carveout content via debugfs */
Dremoteproc_sysfs.c79 /* Expose the current coredump configuration via debugfs */
130 /* Expose the loaded / running firmware name via sysfs */
208 /* Expose the state of the remote processor via sysfs */
247 /* Expose the name of the remote processor via sysfs */
/kernel/linux/linux-6.6/drivers/remoteproc/
Dremoteproc_debugfs.c41 /* Expose the current coredump configuration via debugfs */
119 * memory buffer. We expose this trace buffer using debugfs, so users
154 /* expose the name of the remote processor via debugfs */
174 /* expose recovery flag via debugfs */
250 /* expose the crash trigger via debugfs */
274 /* Expose resource table content via debugfs */
361 /* Expose carveout content via debugfs */
Dremoteproc_sysfs.c79 /* Expose the current coredump configuration via debugfs */
130 /* Expose the loaded / running firmware name via sysfs */
177 /* Expose the state of the remote processor via sysfs */
212 /* Expose the name of the remote processor via sysfs */
/kernel/linux/linux-6.6/Documentation/sound/hd-audio/
Drealtek-pc-beep.rst10 to hide a mixer behind an undocumented vendor register than to just expose it
27 When zero, expose the PC Beep line (from the internal beep generator, when
29 external PCBEEP pin) on the 1Ah pin node. When nonzero, expose the headphone
106 about the input that 1Ah would otherwise expose or if the PCBEEP trace is
/kernel/linux/linux-5.10/Documentation/sound/hd-audio/
Drealtek-pc-beep.rst10 to hide a mixer behind an undocumented vendor register than to just expose it
27 When zero, expose the PC Beep line (from the internal beep generator, when
29 external PCBEEP pin) on the 1Ah pin node. When nonzero, expose the headphone
106 about the input that 1Ah would otherwise expose or if the PCBEEP trace is
/kernel/linux/linux-5.10/drivers/usb/typec/ucsi/
DKconfig32 This driver enables UCSI support on platforms that expose a
42 This driver enables UCSI support on platforms that expose UCSI
/kernel/linux/linux-6.6/Documentation/accel/
Dintroduction.rst7 The Linux compute accelerators subsystem is designed to expose compute
85 To expose your device as an accelerator, two changes are needed to
91 to expose both graphics and compute device char files should be handled by
/kernel/linux/linux-5.10/lib/
Dtest_hmm_uapi.h4 * of the kernel. It allows a userspace program to expose its entire address
31 /* Expose the address space of the calling process through hmm device file */
/kernel/linux/linux-6.6/Documentation/hwmon/
Daquacomputer_d5next.rst28 The Aquaero devices expose eight physical, eight virtual and four calculated
29 virtual temperature sensors, as well as two flow sensors. The fans expose their
54 The Farbwerk and Farbwerk 360 expose four temperature sensors. Additionally,
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/progs/
Dconnect_force_port4.c61 /* Expose local server as 1.2.3.4:60000 to client. */ in getsockname4()
74 /* Expose service 1.2.3.4:60000 as peer instead of backend. */ in getpeername4()
/kernel/linux/linux-6.6/Documentation/arch/x86/
Dmds.rst23 buffer is repartitioned which can expose data from one thread to the other.
105 the microcode updated, but the hypervisor does not (yet) expose the
111 itself are not required because the necessary gadgets to expose the leaked
128 hypervisor does not expose MD_CLEAR in CPUID. It's a best
/kernel/linux/linux-5.10/Documentation/x86/
Dmds.rst23 buffer is repartitioned which can expose data from one thread to the other.
105 the microcode updated, but the hypervisor does not (yet) expose the
111 itself are not required because the necessary gadgets to expose the leaked
128 hypervisor does not expose MD_CLEAR in CPUID. It's a best

12345678910>>...48