Searched refs:information (Results 1 – 25 of 1733) sorted by relevance
12345678910>>...70
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-hv_gpci | 88 This sysfs file exposes the system topology information by making HCALL
107 * "-EPERM" : Partition is not permitted to retrieve performance information,
110 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
112 more information.
114 * "-EFBIG" : System information exceeds PAGE_SIZE.
120 This sysfs file exposes the system topology information by making HCALL
139 * "-EPERM" : Partition is not permitted to retrieve performance information,
142 * "-EIO" : Can't retrieve system information because of invalid buffer length/invalid address
144 more information.
146 * "-EFBIG" : System information exceeds PAGE_SIZE.
[all …]
|
| D | sysfs-driver-intc_sar | 8 derived based on information like mcc (Mobile Country Code) and
32 This sysfs entry is used to retrieve Dynamic SAR information
35 The retrieved information is in the order given below:
41 The above information is sent as integer values separated
42 by a single space. This information can then be pushed to a
44 level using the Band/Antenna/SAR table index information.
53 this sysfs entry. Application can then read this information from
54 the sysfs node and consume the given information.
|
| D | sysfs-driver-ufs | 20 device descriptor parameters. The full information about
30 device descriptor parameters. The full information about
40 the UFS device descriptor parameters. The full information
51 The full information about the descriptor could be found
61 the UFS device descriptor parameters. The full information
72 The full information about the descriptor could be found
83 parameters. The full information about the descriptor could
95 parameters. The full information about the descriptor could
106 the UFS device descriptor parameters. The full information
116 the UFS device descriptor parameters. The full information
[all …]
|
| D | sysfs-kernel-btf | 6 Contains BTF type information and related data for kernel and
15 information with description of all internal kernel types. See
25 information as an add-on to the kernel's BTF (/sys/kernel/btf/vmlinux).
|
| D | sysfs-devices-removable | 8 devices that can support determining such information:
14 "unknown" The information is unavailable / cannot be deduced.
18 information from a combination of hub descriptor bits and
|
| D | sysfs-bus-i2c-devices-turris-omnia-mcu | 7 Only available if board information is burned in the MCU (older
8 revisions have board information burned in the ATSHA204-A chip).
20 Only available if board information is burned in the MCU (older
21 revisions have board information burned in the ATSHA204-A chip).
110 Only available if board information is burned in the MCU (older
111 revisions have board information burned in the ATSHA204-A chip).
|
| /linux-6.12.1/drivers/net/ethernet/intel/ |
| D | Kconfig | 32 Use the above information and the Adapter & Driver ID Guide that
39 More specific information on configuring the driver is in
50 adapters. For more information on how to identify your adapter, go
55 More specific information on configuring the driver is in
69 use the regular e1000 driver For more information on how to
75 More specific information on configuring the driver is in
98 adapters. For more information on how to identify your adapter, go
103 More specific information on configuring the driver is in
134 information on how to identify your adapter, go to the Adapter &
139 More specific information on configuring the driver is in
[all …]
|
| /linux-6.12.1/Documentation/fb/ |
| D | internals.rst | 25 Device independent unchangeable information about a frame buffer device and
31 Device independent changeable information about a frame buffer device and a
38 Device independent colormap information. You can get and set the colormap
46 Generic information, API and low level information about a specific frame
51 Device dependent information that uniquely defines the video mode for this
|
| D | api.rst | 24 Device and driver capabilities are reported in the fixed screen information
51 additional information, which are stored in the variable screen information
54 Visuals describe how color information is encoded and assembled to create
65 screen information line_length field.
83 belonging to different planes, is stored in the fixed screen information
89 stored in the variable screen information grayscale field.
94 specified by the variable screen information bpp field.
105 specified by the variable screen information bpp field.
120 information red, green, blue and transp fields.
129 screen information bits_per_pixel field.
[all …]
|
| /linux-6.12.1/fs/netfs/ |
| D | Kconfig | 11 bool "Gather statistical information on local caching"
14 This option causes statistical information to be gathered on local
42 See Documentation/filesystems/caching/fscache.rst for more information.
45 bool "Gather statistical information on local caching"
49 This option causes statistical information to be gathered on local
60 See Documentation/filesystems/caching/fscache.rst for more information.
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/intel/ |
| D | igbvf.rst | 27 Driver information can be obtained using ethtool, lspci, and ifconfig.
36 For information on how to identify your adapter, and for the latest Intel
47 diagnostics, as well as displaying statistical information. The latest ethtool
55 For general information, go to the Intel support website at:
59 with a supported adapter, email the specific information related to the issue
|
| /linux-6.12.1/drivers/platform/x86/amd/pmf/ |
| D | Kconfig | 23 bool "PMF debug information"
26 Enabling this option would give more debug information on the OEM fed
28 information after evaluating a ACPI method and the information is stored
|
| /linux-6.12.1/Documentation/tools/rtla/ |
| D | rtla-osnoise.rst | 19 The *osnoise* tracer outputs information in two ways. It periodically prints
21 the occurrence of the source of interference. It also provides information
23 mode displays information about the periodic summary from the *osnoise* tracer.
24 The **rtla osnoise hist** mode displays information about the noise using
|
| D | common_timerlat_description.rst | 4 the wakeup, they collect and generate useful information for the
7 The *timerlat* tracer outputs information in two ways. It periodically
9 handler. It also enable the trace of the most relevant information via
|
| /linux-6.12.1/Documentation/driver-api/pldmfw/ |
| D | file-format.rst | 53 contains information about the version of the format that the file uses. It
84 device, such as the PCI device and vendor information. It will also indicate
139 The component information area begins with a count of the number of
141 component information points to the location in the file where the component
195 Following the component information is a short 4-byte CRC calculated over
196 the contents of all of the header information.
201 The component images follow the package header information in the PLDM
|
| D | driver-ops.rst | 15 descriptors in the record with information from the device. Many record
35 information to the device. It is called once for each applicable component,
37 device driver should send the component information to the device firmware,
40 to firmware as part of the component table information. The driver should an
|
| /linux-6.12.1/drivers/thermal/intel/int340x_thermal/ |
| D | Kconfig | 22 Enable this to expose the temperature information and cooling ability
25 the information to the user or use this information for making
27 information to allow the user to select his laptop to run without
|
| /linux-6.12.1/mm/damon/ |
| D | Kconfig | 9 access frequency of each memory region. The information can be useful
13 more information.
22 For more information on KUnit and unit tests in general, please refer
50 For more information on KUnit and unit tests in general, please refer
69 For more information on KUnit and unit tests in general, please refer
99 For more information on KUnit and unit tests in general, please refer
|
| /linux-6.12.1/Documentation/userspace-api/gpio/ |
| D | gpio-v2-get-lineinfo-ioctl.rst | 12 GPIO_V2_GET_LINEINFO_IOCTL - Get the publicly available information for a line.
34 Get the publicly available information for a line.
36 This information is available independent of whether the line is in use.
|
| /linux-6.12.1/tools/bpf/bpftool/Documentation/ |
| D | bpftool-struct_ops.rst | 40 Show brief information about the struct_ops in the system. If
41 *STRUCT_OPS_MAP* is specified, it shows information only for the given
49 Dump details information about the struct_ops in the system. If
50 *STRUCT_OPS_MAP* is specified, it dumps information only for the given
|
| /linux-6.12.1/Documentation/arch/x86/ |
| D | zero-page.rst | 16 000/040 ALL screen_info Text mode or frame buffer information
18 040/014 ALL apm_bios_info APM BIOS information (struct apm_bios_info)
20 060/010 ALL ist_info Intel SpeedStep (IST) BIOS support information
33 1C0/020 ALL efi_info EFI 32 information (struct efi_info)
|
| /linux-6.12.1/drivers/thermal/mediatek/ |
| D | Kconfig | 7 information from thermal sensors or turn on throttle
17 information for MediaTek platforms.
26 information for supported MediaTek platforms.
|
| /linux-6.12.1/tools/perf/Documentation/ |
| D | jitdump-specification.txt | 17 …a information about the generated code, such as address, size, and name of generated functions, th…
63 * Value 2 : JIT_CODE_DEBUG_INFO: record describing the debug information for a jitted function
65 * Value 4 : JIT_CODE_UNWINDING_INFO: record describing a function unwinding information
119 …cord contains source lines debug information, i.e., a way to map a code address back to a source l…
122 * uint64_t code_addr: address of function for which the debug information is generated
126 The debug_entry describes the source line information. It is defined as follows in order:
127 * uint64_t code_addr: address of function for which the debug information is generated
146 …SE record does not have any specific fields, the record header contains all the information needed.
154 The record is used to describe the unwinding information for a jitted function.
170 …can be used to specify FP based unwinding for a function which does not have unwinding information.
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 15 By design, a FAN_FS_ERROR notification exposes sufficient information
28 important pieces of information are never lost.
52 The generic error record provides enough information for a file system
68 suppressed to preserve the original error information, since the last
76 specific application can use that information to attempt a recovery
|
| /linux-6.12.1/Documentation/devicetree/bindings/sound/ |
| D | max98373.txt | 13 - maxim,vmon-slot-no : slot number used to send voltage information
18 - maxim,imon-slot-no : slot number used to send current information
21 - maxim,spkfb-slot-no : slot number used to send speaker feedback information
|
12345678910>>...70