/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-event_source-devices-hv_gpci | 88 This sysfs file exposes the system topology information by making HCALL 100 runtime by setting "Enable Performance Information Collection" option. 107 * "-EPERM" : Partition is not permitted to retrieve performance information, 108 required to set "Enable Performance Information Collection" option. 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 132 runtime by setting "Enable Performance Information Collection" option. 139 * "-EPERM" : Partition is not permitted to retrieve performance information, [all …]
|
H A 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 …]
|
H A 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.
|
/linux/drivers/net/ethernet/intel/ |
H A 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/drivers/scsi/qedf/ |
H A D | qedf_hsi.h | 25 * FCoE CQ element ABTS information 47 * FCoE CMDQ element control information 92 * FCoE CQ element response information 112 * FCoE CQ element Target completion information 136 * FCoE CQ element middle path information 146 * FCoE CQ element unsolicited information 149 /* BD information: Physical address and opaque data */ 160 /* BD information: Physical address and opaque data */ 169 * FCoE CQ element information 172 struct fcoe_cqe_rsp_info rsp_info /* Response completion information */; [all …]
|
/linux/Documentation/fb/ |
H A 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/drivers/media/platform/mediatek/vcodec/decoder/ |
H A D | vdec_msg_queue.h | 60 * @private_data: shared information used to lat and core hardware 61 * @ctx: mtk vcodec context information 87 * @lat_buf: lat buffer used to store lat buffer information 101 * @ctx: mtk vcodec context information 124 * vdec_msg_queue_init - init lat buffer information. 125 * @msg_queue: used to store the lat buffer information 137 * vdec_msg_queue_init_ctx - used to init msg queue context information. 162 * @msg_queue: used to store the lat buffer information 169 * @msg_queue: used to store the lat buffer information 177 * @msg_queue: used to store the lat buffer information [all …]
|
/linux/drivers/scsi/isci/ |
H A D | phy.h | 232 * optional information that can be retrieved for a specific phy. 238 * This PHY information field tracks the number of frames received. 243 * This PHY information field tracks the number of frames transmitted. 248 * This PHY information field tracks the number of DWORDs received. 253 * This PHY information field tracks the number of DWORDs transmitted. 258 * This PHY information field tracks the number of times DWORD 264 * This PHY information field tracks the number of received DWORDs with 270 * This PHY information field tracks the number of received frames with a 276 * This PHY information field tracks the number of DONE (ACK/NAK TIMEOUT) 282 * This PHY information field tracks the number of DONE (ACK/NAK TIMEOUT) [all …]
|
/linux/include/uapi/linux/ |
H A D | pfrut.h | 69 * Retrieve information on the Platform Firmware Runtime Update capability. 70 * The information is a struct pfru_update_cap_info. 106 * struct pfru_update_cap_info - Runtime update capability information. 118 * @oem_info_len: Length of the buffer containing the vendor specific information. 139 * struct pfru_com_buf_info - Communication buffer information. 158 * struct pfru_updated_result - Platform firmware runtime update result information. 210 * struct pfrt_log_info - Telemetry log information. 230 * Set the PFRT log level and log type. The input information is 244 * Retrieve log level and log type of the telemetry. The information is 255 * * -EINVAL - fail to get the log buffer information [all …]
|
H A D | sctp.h | 186 * This cmsghdr structure provides information for initializing new 202 /* 5.3.2 SCTP Header Information Structure (SCTP_SNDRCV) 205 * describes SCTP header information about a received message through 224 /* 5.3.4 SCTP Send Information Structure (SCTP_SNDINFO) 240 /* 5.3.5 SCTP Receive Information Structure (SCTP_RCVINFO) 242 * This cmsghdr structure describes SCTP receive information 260 /* 5.3.6 SCTP Next Receive Information Structure (SCTP_NXTINFO) 262 * This cmsghdr structure describes SCTP receive information 264 * if this information is already available when delivering 279 /* 5.3.7 SCTP PR-SCTP Information Structure (SCTP_PRINFO) [all …]
|
/linux/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
H A D | cfg80211.h | 118 /* security information with currently associated ap */ 162 * struct brcmf_cfg80211_profile - profile information. 165 * @sec: security information. 166 * @key: key information 224 * struct brcmf_cfg80211_vif - virtual interface specific information. 228 * @profile: profile information. 294 * struct brcmf_cfg80211_vif_event - virtual interface event information. 310 * struct brcmf_cfg80211_wowl - wowl related information. 336 * @p2p: peer-to-peer specific information. 337 * @btcoex: Bluetooth coexistence information. [all …]
|
/linux/drivers/net/ipa/ |
H A D | ipa_qmi_msg.h | 25 * information for each field. The qmi_send_*() interfaces require 122 /* The message for the IPA_QMI_INIT_DRIVER request contains information 129 /* Modem header table information. This defines the IPA shared 135 /* Routing table information. These define the location and maximum 145 /* Filter table information. These define the location of the 154 /* Modem memory information. This defines the location and 176 /* Processing context memory information. This defines the memory in 182 /* Compression command memory information. This defines the memory 188 /* Routing table information. These define the location and maximum 198 /* Filter table information. These define the location and size [all …]
|
/linux/Documentation/sound/designs/ |
H A D | procfile.rst | 10 ALSA has its own proc tree, /proc/asound. Many useful information are 18 Global Information 67 like pcm0p or pcm1c. They hold the PCM information for each PCM 89 The general information of this PCM device: card #, device #, 124 The general information of this PCM sub-stream. 137 The buffer pre-allocation information. 144 AC97 Codec Information 148 Shows the general information of this AC97 codec chip, such as 168 of the given card. This information is very useful for debugging. 175 Shows the general codec information and the attribute of each [all …]
|
/linux/arch/powerpc/perf/ |
H A D | hv-gpci.c | 105 /* Interface attribute array index to store system information */ 113 /* Counter request value to retrieve system information */ 149 * all the information and a partial buffer returned. in systeminfo_gpci_request() 153 * performance information, and required to set in systeminfo_gpci_request() 154 * "Enable Performance Information Collection" option. in systeminfo_gpci_request() 185 pr_info("System information exceeds PAGE_SIZE\n"); in systeminfo_gpci_request() 205 * the system topology information. in processor_bus_topology_show() 220 * implies that buffer can't accommodate all information, and a partial buffer in processor_bus_topology_show() 224 * to buffer util we get all the information. in processor_bus_topology_show() 273 * the system processor information. in processor_config_show() [all …]
|
/linux/fs/netfs/ |
H A 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/sound/soc/sof/ |
H A D | ipc4-fw-reg.h | 15 * struct sof_ipc4_pipeline_registers - Pipeline start and end information in fw 34 * struct sof_ipc4_peak_volume_regs - Volume information in fw 46 * struct sof_ipc4_llp_reading - Llp information in fw 61 * @llp_reading: Llp information in memory window 72 * struct sof_ipc4_llp_reading_slot - Llp slot information in memory window 74 * @reading: Llp information in memory window 81 /* ROM information */ 111 * DSP / FW state information to the driver
|
/linux/tools/perf/Documentation/ |
H A 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/drivers/mtd/ubi/ |
H A D | attach.c | 14 * The attaching information is represented by a &struct ubi_attach_info' 15 * object. Information about volumes is represented by &struct ubi_ainf_volume 88 * @ai: attaching information 152 * ubi_find_or_add_av - search for a volume in the attaching information and 154 * @ai: attaching information 169 * @ai: attaching information 173 * Allocate an aeb object and initialize the pnum and ec information. 197 * @ai: attaching information 210 * @ai: attaching information 259 * @ai: attaching information [all …]
|
/linux/fs/vboxsf/ |
H A D | shfl_hostintf.h | 36 SHFL_FN_INFORMATION = 9, /* Query/set object information. */ 139 /** The available additional information in a shfl_fsobjattr object. */ 141 /** No additional information is available / requested. */ 184 * the information isn't available. 190 * on (st_dev). This field is 0 if this information is not available. 198 * This field is 0 if the information is not available. 204 * This field is 0 if this information is not available. 210 * This field is 0 if this information is not available. 253 /** Filesystem object information structure. */ 413 /** Shared Folder directory information */ [all …]
|
/linux/drivers/scsi/megaraid/ |
H A D | mbox_defs.h | 220 * @reqsensearea : Sense information buffer 273 * @reqsensearea : Sense information buffer 304 * mraid_pinfo_t - product info, static information about the controller 321 * This structures holds the information about the controller which is not 424 * mraid_inquiry3_t - enquiry for device information 477 * mraid_adapinfo_t - information about the adapter 526 * mraid_ldrv_info_t - information about the logical drives 543 * mraid_pdrv_info_t - information about the physical drives 554 * @mraid_adapinfo_t : adapter information 555 * @mraid_ldrv_info_t : logical drives information [all …]
|
/linux/drivers/comedi/drivers/ni_routing/ |
H A D | README | 30 One additional major challenge is that this information does not seem to be 34 information is through the proprietary NI-MAX software, which currently only 35 runs on Windows platforms. A further challenge is that this information 43 information _and_ the knowledge of valid routes per device, a few specific 49 documentation, (b) NI's user-level code, (c) the information as provided by 96 As noted above, the only known consistent source of information for 98 Windows software, NI-MAX. Also, as noted above, this information can 109 ni_device_routes.c to include this information into comedi. 119 As noted above, the only consistent source of information of valid 121 software, NI-MAX. Also, as noted above, this information can only be [all …]
|
/linux/Documentation/process/ |
H A D | security-bugs.rst | 12 information beyond what was initially provided in a report and rely on 21 As it is with any bug, the more information provided the easier it 24 information is helpful. Any exploit code is very helpful and will not 43 Disclosure and embargoed information 61 While embargoed information may be shared with trusted individuals in 62 order to develop a fix, such information will not be published alongside 65 and followup discussions (if any), exploits, CVE information or the 69 information submitted to the security list and any followup discussions
|
/linux/Documentation/admin-guide/auxdisplay/ |
H A D | ks0108.rst | 13 1. DRIVER INFORMATION 14 2. DEVICE INFORMATION 18 1. Driver Information 24 2. Device Information 48 your LCD specific wiring information in the same folder.
|
/linux/drivers/net/wireless/intel/iwlwifi/pcie/ |
H A D | iwl-context-info-v2.h | 53 * @IWL_PRPH_SCRATCH_RB_SIZE_EXT_MASK: RB size full information, ignored 98 * @version: prph scratch information version id 99 * @size: the size of the context information in DWs 111 * @control_flags: context information flags see &enum iwl_prph_scratch_flags 112 * @control_flags_ext: context information for extended flags, 191 * @version: version information of context info and HW 239 * struct iwl_prph_info - peripheral information 254 * @version: version of the context information 255 * @size: size of context information in DWs 258 * @prph_info_base_addr: the peripheral information structure start address [all …]
|
/linux/drivers/gpu/drm/xe/ |
H A D | xe_survivability_mode.c | 47 * debug information:: 51 * Capability Information: 53 * Postcode Information: 54 * Provides information about the failure 55 * Overflow Information 57 * Auxiliary Information 58 * Certain failures may have information in addition to postcode information 252 * Initialize survivability information and enable survivability mode 277 /* Only log debug information and exit if it is a critical failure */ in xe_survivability_mode_enable()
|