Searched full:following (Results 1 – 25 of 6119) sorted by relevance
12345678910>>...245
| /Linux-v6.1/sound/pci/cs46xx/ |
| D | cs46xx.h | 22 * The following define the offsets of the registers accessed via base address
150 * The following define the offsets of the registers and memories accessed via
173 * The following defines are for the flags in the host interrupt status
208 * The following defines are for the flags in the host signal register 0.
245 * The following defines are for the flags in the host interrupt control
252 * The following defines are for the flags in the DMA status register.
260 * The following defines are for the flags in the host DMA source address
275 * The following defines are for the flags in the host DMA destination address
290 * The following defines are for the flags in the host DMA control register.
299 * The following defines are for the flags in the host DMA control register.
[all …]
|
| /Linux-v6.1/net/netlabel/ |
| D | netlabel_mgmt.h | 23 * The following NetLabel payloads are supported by the management interface.
33 * If IPv4 is specified the following attributes are required:
38 * If IPv6 is specified the following attributes are required:
43 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required:
48 * however the following attribute may optionally be sent:
64 * The kernel should respond with a series of the following messages.
71 * If the IP address selectors are not used the following attribute is
76 * If the IP address selectors are used then the following attritbute is
81 * If the mapping is using the NETLBL_NLTYPE_CIPSOV4 type then the following
97 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required:
[all …]
|
| D | netlabel_unlabeled.h | 22 * The following NetLabel payloads are supported by the Unlabeled subsystem.
33 * If IPv4 is specified the following attributes are required:
38 * If IPv6 is specified the following attributes are required:
51 * If IPv4 is specified the following attributes are required:
56 * If IPv6 is specified the following attributes are required:
65 * The kernel should response with a series of the following messages.
72 * If IPv4 is specified the following attributes are required:
77 * If IPv6 is specified the following attributes are required:
90 * If IPv4 is specified the following attributes are required:
95 * If IPv6 is specified the following attributes are required:
[all …]
|
| D | netlabel_cipso_v4.h | 22 * The following NetLabel payloads are supported by the CIPSO subsystem.
33 * If using CIPSO_V4_MAP_TRANS the following attributes are required:
51 * success the kernel should send a response using the following format.
65 * If using CIPSO_V4_MAP_TRANS the following attributes are required:
77 * the following messages.
124 * each of the following types: NLBL_CIPSOV4_A_MLSLVLLOC and
139 * the following types: NLBL_CIPSOV4_A_MLSCATLOC and
|
| /Linux-v6.1/scripts/kconfig/tests/preprocess/escape/ |
| D | Kconfig | 7 # delimiters. You can use the following trick to do so.
12 # The following prints the text as-is.
23 # The following should print "$(X)". It should not be expanded further.
28 # The following should print "(".
33 # The following should print "$(X)". It should not be expanded further.
37 # The following should print "$(X)" as well.
41 # The following should print "$(".
|
| /Linux-v6.1/Documentation/admin-guide/device-mapper/ |
| D | dm-ima.rst | 37 system needs to be updated to have following line, and the system needs
52 Then IMA ASCII measurement log has the following format:
89 Following device state changes will trigger IMA measurements:
103 The IMA measurement log has the following format for 'dm_table_load':
149 For instance, if a linear device is created with the following table entries,
156 Then IMA ASCII measurement log will have the following entry:
173 The IMA measurement log has the following format for 'dm_device_resume':
194 For instance, if a linear device is resumed with the following command,
211 The IMA measurement log has the following format for 'dm_device_remove':
232 For instance, if a linear device is removed with the following command,
[all …]
|
| D | dm-dust.rst | 17 Writes of blocks in the "bad block list will result in the following:
161 following message command::
174 following message command::
178 The following message will print if the block is in the list::
182 The following message will print if the block is not in the list::
196 following message command::
200 After clearing the bad block list, the following message will appear::
204 If there were no bad blocks to clear, the following message will
213 with blocks 1 and 2 in the bad block list), run the following message
260 This can be done by enabling "quiet mode" via the following message::
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 43 To reduce its OS jitter, do any of the following:
62 To reduce its OS jitter, do the following:
73 To reduce its OS jitter, do one of the following:
93 Do all of the following:
109 Do all of the following:
121 Do all of the following:
133 Do all of the following:
145 Do one or more of the following:
156 Do all of the following:
178 Do all of the following:
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/clock/ |
| D | mvebu-core-clock.txt | 7 The following is a list of provided IDs and clock names on Armada 370/XP:
14 The following is a list of provided IDs and clock names on Armada 375:
20 The following is a list of provided IDs and clock names on Armada 380/385:
26 The following is a list of provided IDs and clock names on Armada 39x:
34 The following is a list of provided IDs and clock names on 98dx3236:
40 The following is a list of provided IDs and clock names on Kirkwood and Dove:
46 The following is a list of provided IDs and clock names on Orion5x:
52 - compatible : shall be one of the following:
|
| D | mvebu-gated-clock.txt | 10 The following is a list of provided IDs for Armada 370:
27 The following is a list of provided IDs for Armada 375:
54 The following is a list of provided IDs for Armada 380/385:
81 The following is a list of provided IDs for Armada 39x:
95 The following is a list of provided IDs for Armada XP:
122 The following is a list of provided IDs for 98dx3236:
132 The following is a list of provided IDs for Dove:
155 The following is a list of provided IDs for Kirkwood:
176 - compatible : shall be one of the following:
|
| /Linux-v6.1/tools/perf/Documentation/ |
| D | perf-c2c.txt | 85 Following fields are available: tid,pid,iaddr,dso
134 Following perf record options are configured by default:
139 Unless specified otherwise with '-e' option, following events are monitored by
145 following on AMD:
149 and following on PowerPC:
166 The report command workflow is following:
176 For each cacheline in the 1) list we display following data:
225 For each offset in the 2) list we display following data:
275 - node IDs with stats for each ID, in following format:
278 - node IDs with list of affected CPUs in following format:
[all …]
|
| D | jitdump-specification.txt | 36 Each jitdump file starts with a fixed size header containing the following fields in order:
60 The following record types are defined:
72 The record has the following fields following the fixed-size record header in order:
98 The record has the following fields following the fixed-size record header in order:
121 The record has the following fields following the fixed-size record header in order:
156 The record has the following fields following the fixed-size record header in order:
|
| /Linux-v6.1/drivers/staging/media/deprecated/saa7146/av7110/ |
| D | audio_data_types.rst | 15 and can take the following values, depending on whether we are replaying
34 The following values can be returned by the AUDIO_GET_STATUS call
50 the following values.
66 The AUDIO_GET_STATUS call returns the following structure informing
85 The following structure is used by the AUDIO_SET_MIXER call to set the
103 following bits set according to the hardwares capabilities.
|
| /Linux-v6.1/Documentation/crypto/ |
| D | userspace-if.rst | 16 The following covers the user space interface exported by the kernel
32 following ciphers are accessible:
44 header files do not export these flags yet, use the following macros:
65 The following API calls assume that the socket descriptor is already
69 To initialize the socket interface, the following sequence has to be
122 the following flags to be specified:
166 following information specified with a separate header instances:
176 The send system call family allows the following flag to be specified:
225 following information specified with a separate header instances:
239 The send system call family allows the following flag to be specified:
[all …]
|
| D | architecture.rst | 7 The kernel crypto API provides different API calls for the following
85 following semantics:
103 the following implementations: AES-NI, assembler implementation, or
121 ciphers. Each block listed in /proc/crypto may contain the following
189 of a type and mask flag. Both parameters have the following meaning (and
194 Otherwise, the caller may provide the following selections which match
242 The following subsections explain the internal structure based on
249 The following ASCII art decomposes the kernel crypto API layers when
268 following ASCII art applies too. However, the decomposition of GCM into
272 Each block in the following ASCII art is an independent cipher instance
[all …]
|
| /Linux-v6.1/drivers/gpu/drm/tiny/ |
| D | Kconfig | 94 DRM driver for the following HX8357D panels:
107 DRM driver for the following Ilitek ILI9163 panels:
119 DRM driver for the following Ilitek ILI9225 panels:
132 DRM driver for the following Ilitek ILI9341 panels:
145 DRM driver for the following Ilitek ILI9486 panels:
168 DRM driver for the following Pervasive Displays panels:
183 DRM driver for the following Sitronix ST7586 panels:
196 DRM driver for Sitronix ST7715R/ST7735R with one of the following
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | mp5023.rst | 33 The driver exports the following attributes via the 'sysfs' files
48 The driver provides the following attributes for output voltage:
56 The driver provides the following attributes for output current:
66 The driver provides the following attributes for input power:
74 The driver provides the following attributes for temperature:
|
| /Linux-v6.1/include/linux/ |
| D | watchdog.h | 127 /* Use the following function to check whether or not the watchdog is active */
134 * Use the following function to check whether or not the hardware watchdog
142 /* Use the following function to set the nowayout feature */
149 /* Use the following function to stop the watchdog on reboot */
155 /* Use the following function to stop the watchdog when unregistering it */
161 /* Use the following function to stop the wdog ping worker when suspending */
167 /* Use the following function to check if a timeout value is invalid */
186 /* Use the following function to check if a pretimeout value is invalid */
193 /* Use the following functions to manipulate watchdog driver specific data */
204 /* Use the following functions to report watchdog pretimeout event */
|
| /Linux-v6.1/Documentation/x86/x86_64/ |
| D | uefi.rst | 23 - Build the kernel with the following configuration::
28 If EFI runtime services are expected, the following configuration should
35 - Copy the following to the VFAT partition:
44 - If some or all EFI runtime services don't work, you can try following
55 physical RAM by using the following kernel command line parameter.
|
| /Linux-v6.1/Documentation/devicetree/bindings/net/ |
| D | snps,dwc-qos-ethernet.txt | 25 - clock-names: May contain any/all of the following depending on the IP
60 following clocks to this list in the future: clk_rx_125_i, clk_tx_125_i,
71 The following compatible values require the following set of clocks:
90 - reset-names: May contain any/all of the following depending on the IP
95 The following compatible values require the following set of resets:
121 mdio, there must be device tree subnode with the following
127 For each phy on the mdio bus, there must be a node with the following
|
| /Linux-v6.1/arch/alpha/include/asm/ |
| D | wrperfmon.h | 9 /* Following commands are implemented on all CPUs */
14 /* Following commands on EV5/EV56/PCA56 only */
17 /* Following commands are on EV5 and better CPUs */
20 /* Following command are on EV6 and better CPUs */
22 /* Following command are on EV67 and better CPUs */
|
| /Linux-v6.1/LICENSES/deprecated/ |
| D | Linux-OpenIB | 4 To use the Linux Kernel Variant of OpenIB.org license put the following
11 modification, are permitted provided that the following conditions are met:
14 notice, this list of conditions and the following disclaimer.
17 notice, this list of conditions and the following disclaimer in the
|
| /Linux-v6.1/Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 17 This driver supports the following features:
47 …Run-time configuration the role of driver is to allow the software application to do the following:
59 the software application to do the following:
75 The driver defines the following driver file operations to provide user
81 …- unlocked_ioctl: Provides the following ioctl commands that allows the application configure the …
107 The following outlines the flow the user should perform:
138 Setting the order can only be done if the following restrictions are met:
146 The following steps indicate how to add LDPC codes to the SD-FEC core:
155 Adding LDPC codes can only be done if the following restrictions are met:
166 Adding Turbo decode can only be done if the following restrictions are met:
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/msm/ |
| D | mdp5.txt | 14 - reg-names: The names of register regions. The following regions are required:
24 - clock-names: the following clocks are required.
33 - clock-names: the following clocks are optional:
41 - reg-names: The names of register regions. The following regions are required:
45 - clock-names: the following clocks are required.
77 - clock-names: the following clocks are optional:
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | dcdbas.rst | 13 Dell OpenManage requires this driver on the following Dell PowerEdge systems:
32 The driver creates the following sysfs entries for systems management
40 Systems management software must perform the following steps to execute
59 The driver creates the following sysfs entries for systems management software
67 Dell OpenManage performs the following steps to execute a power cycle or
81 The following table shows the value to write to host_control_smi_type to
|
12345678910>>...245
