Searched full:information (Results 1 – 25 of 7430) sorted by relevance
12345678910>>...298
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 19 device descriptor parameters. The full information about
28 device descriptor parameters. The full information about
37 the UFS device descriptor parameters. The full information
47 The full information about the descriptor could be found
56 the UFS device descriptor parameters. The full information
66 The full information about the descriptor could be found
76 parameters. The full information about the descriptor could
87 parameters. The full information about the descriptor could
97 the UFS device descriptor parameters. The full information
106 the UFS device descriptor parameters. The full information
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/ |
| D | Kconfig | 29 Use the above information and the Adapter & Driver ID Guide that
36 More specific information on configuring the driver is in
47 adapters. For more information on how to identify your adapter, go
52 More specific information on configuring the driver is in
66 use the regular e1000 driver For more information on how to
72 More specific information on configuring the driver is in
95 adapters. For more information on how to identify your adapter, go
100 More specific information on configuring the driver is in
131 information on how to identify your adapter, go to the Adapter &
136 More specific information on configuring the driver is in
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 64 :ref:`Documentation/admin-guide/security-bugs.rst <securitybugs>` for more information.
69 information on the linux-kernel mailing list see
88 Gather information
91 The most important information in a bug report is how to reproduce the
92 bug. This includes system information, and (most importantly)
98 bug report. This explains what you should do with the "Oops" information
104 information they're really interested in. If some information is not
111 Use that information to fill in all fields of the bug report form, and
118 [4.] Kernel information
122 [6.] Output of Oops.. message (if applicable) with symbolic information
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/qedf/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/clk/ingenic/ |
| D | cgu.h | 18 * struct ingenic_cgu_pll_info - information about a PLL
62 * struct ingenic_cgu_mux_info - information about a clock mux
75 * struct ingenic_cgu_div_info - information about a divider
102 * struct ingenic_cgu_fixdiv_info - information about a fixed divider
110 * struct ingenic_cgu_gate_info - information about a clock gate
124 * struct ingenic_cgu_custom_info - information about a custom (SoC) clock
132 * struct ingenic_cgu_clk_info - information about a clock
138 * @pll: information valid if type includes CGU_CLK_PLL
139 * @gate: information valid if type includes CGU_CLK_GATE
140 * @mux: information valid if type includes CGU_CLK_MUX
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 26 NSLU2 NAS device. For more information on this platform,
34 Avila Network Platform. For more information on this platform,
51 information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
58 7001 Access Point. For more information on this platform,
66 WG302 v2 or WAG302 v2 Access Points. For more information
74 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
81 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
88 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
101 For more information on this platform, see <file:Documentation/arm/ixp4xx.rst>.
117 PrPCM1100 Processor Mezanine Module. For more information on
[all …]
|
| /kernel/linux/linux-5.10/fs/fscache/ |
| D | Kconfig | 11 See Documentation/filesystems/caching/fscache.rst for more information.
14 bool "Gather statistical information on local caching"
17 This option causes statistical information to be gathered on local
28 See Documentation/filesystems/caching/fscache.rst for more information.
31 bool "Gather latency information on local caching"
34 This option causes latency information to be gathered on local
45 See Documentation/filesystems/caching/fscache.rst for more information.
55 See Documentation/filesystems/caching/fscache.rst for more information.
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| 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 …]
|
| /kernel/linux/linux-5.10/arch/h8300/ |
| D | Kconfig.cpu | 37 More Information. (Japanese Only)
40 More Information.
50 More Information. (Japanese Only)
59 More Information. (Japanese Only)
68 More Information.
77 More Information.
87 More Information.
|
| /kernel/linux/linux-5.10/drivers/scsi/isci/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/broadcom/brcm80211/brcmfmac/ |
| D | cfg80211.h | 116 /* security information with currently associated ap */
145 * struct brcmf_cfg80211_profile - profile information.
148 * @sec: security information.
149 * @key: key information
207 * struct brcmf_cfg80211_vif - virtual interface specific information.
211 * @profile: profile information.
265 * struct brcmf_cfg80211_vif_event - virtual interface event information.
281 * struct brcmf_cfg80211_wowl - wowl related information.
307 * @p2p: peer-to-peer specific information.
308 * @btcoex: Bluetooth coexistence information.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/sound/designs/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/net/ipa/ |
| D | ipa_qmi_msg.h | 24 * information for each field. The qmi_send_*() interfaces require
117 /* The message for the IPA_QMI_INIT_DRIVER request contains information
124 /* Modem header table information. This defines the IPA shared
130 /* Routing table information. These define the location and maximum
140 /* Filter table information. These define the location of the
149 /* Modem memory information. This defines the location and
171 /* Processing context memory information. This defines the memory in
177 /* Compression command memory information. This defines the memory
183 /* Routing table information. These define the location and maximum
193 /* Filter table information. These define the location and size
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | page_owner.rst | 12 When allocation happens, information about allocation such as call stack
15 this information.
25 fragmentation statistics can be obtained through gfp flag information of
33 doesn't require memory to store owner information, so there is no runtime
59 stores information into the memory from struct page extension. This memory
62 they would have no owner information. To fix it up, these early allocated
64 Although it doesn't mean that they have the right owner information,
83 4) Analyze information from page owner::
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/sound/soc/sof/imx/ |
| D | imx-common.c | 15 * in order to gather information about the registers, filename and
18 * @xoops: Stores information about registers.
19 * @panic_info: Stores information about filename and line number.
58 /* Get information about the panic status from the debug box area. in imx8_dump()
63 /* Get information about the registers, the filename and line in imx8_dump()
69 /* Print the information to the console */ in imx8_dump()
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | yuv-formats.rst | 10 separates the brightness information (Y) from the color information (U
11 and V or Cb and Cr). The color information consists of red and blue
15 early television would only transmit brightness information. To add
21 to brightness information.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/auxdisplay/ |
| 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.
|
| /kernel/linux/linux-5.10/security/ |
| D | Kconfig.hardening | 16 information at:
61 and information exposures.
70 uninitialized stack variable exploits and information
83 of uninitialized stack variable exploits and information
101 of uninitialized stack variable exploits and information
116 information exposures, even variables that were warned about
134 information exposures, even variables that were warned
164 potential for uninitialized stack variable exploits or information
176 This plugin was ported from grsecurity/PaX. More information at:
200 previous syscalls. Although this information is not precise, it
|
| /kernel/linux/build/test/moduletest/runtest/bin/mem_debug_t/testcases/bin/ |
| D | mem_debug08.sh | 16 # Description: Ashmem information display test
41 # Confirm that each process ashmem information is correct
44 tst_res TINFO "now going to check $p ashmem information"
58 … tst_res TFAIL "Cannot find ashmem information of $pid .Ashmem information display test failed!"
60 …tst_res TPASS "$pid totally found $ashmem_info_lines ashmem messages.Ashmem information display te…
|
| /kernel/linux/linux-5.10/drivers/mtd/ubi/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/staging/comedi/drivers/ni_routing/ |
| 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 …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-s3c/ |
| D | iotiming-s3c2410.c | 205 * s3c2410_calc_bank - calculate bank timing information
207 * @bt: The bank timing information.
210 * setting for the @cfg timing. This updates the timing information
284 * s3c2410_iotiming_getbank - turn BANKCON into cycle time information
289 * in @cfg, update the cycle timing information.
305 * s3c2410_iotiming_debugfs - debugfs show io bank timing information
308 * @iob: The IO bank information to decode.
351 * @iot: The IO timing information to fill out.
354 * frequency information in @cfg. This is then used by s3c2410_iotiming_set()
393 * @iot: The IO timing information to use.
[all …]
|
| /kernel/linux/linux-5.10/drivers/scsi/megaraid/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_hw_catalog.h | 215 * MACRO DPU_HW_BLK_INFO - information of HW blocks inside DPU
230 * MACRO DPU_HW_SUBBLK_INFO - information of HW sub-block inside DPU
252 * struct dpu_scaler_blk: Scaler information
266 * struct dpu_pp_blk : Pixel processing sub-blk information
384 * struct dpu_lm_sub_blks: information of mixer block
398 * struct dpu_dspp_sub_blks: Information of DSPP block
471 * struct dpu_sspp_cfg - information of source pipes
475 * @sblk: SSPP sub-blocks information
489 * struct dpu_lm_cfg - information of layer mixer blocks
493 * @sblk: LM Sub-blocks information
[all …]
|
12345678910>>...298