Searched full:following (Results 1 – 25 of 5904) sorted by relevance
12345678910>>...237
/linux-6.15/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-6.15/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-6.15/Documentation/hwmon/ |
D | mp9941.rst | 29 The driver exports the following attributes via the 'sysfs' files 40 The driver provides the following attributes for output voltage: 54 The driver provides the following attributes for input current: 64 The driver provides the following attributes for output current: 70 The driver provides the following attributes for input power: 76 The driver provides the following attributes for output power: 82 The driver provides the following attributes for temperature:
|
D | tps25990.rst | 38 The driver exports the following attributes via the 'sysfs' files 59 The driver provides the following attributes for main input voltage: 89 The driver provides the following attributes for auxiliary input voltage: 95 The driver provides the following attributes for output voltage: 111 The driver provides the following attributes for input power: 127 The driver provides the following attributes for temperature: 145 The driver provides the following attributes for sampling:
|
D | mp2993.rst | 29 The driver exports the following attributes via the 'sysfs' files 52 The driver provides the following attributes for output voltage: 78 The driver provides the following attributes for input current: 88 The driver provides the following attributes for output current: 114 The driver provides the following attributes for input power: 120 The driver provides the following attributes for output power: 130 The driver provides the following attributes for temperature:
|
D | mp2891.rst | 34 The driver exports the following attributes via the 'sysfs' files 53 The driver provides the following attributes for output voltage: 87 The driver provides the following attributes for input current: 105 The driver provides the following attributes for output current: 131 The driver provides the following attributes for input power: 149 The driver provides the following attributes for output power: 159 The driver provides the following attributes for temperature:
|
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:
|
D | mp5990.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:
|
D | xdp710.rst | 32 The driver exports the following attributes via the 'sysfs' files 47 The driver provides the following attributes for output voltage: 55 The driver provides the following attributes for output current: 65 The driver provides the following attributes for input power: 73 The driver provides the following attributes for temperature:
|
D | mp5920.rst | 34 The driver exports the following attributes via the 'sysfs' files 49 The driver provides the following attributes for output voltage: 61 The driver provides the following attributes for output current: 73 The driver provides the following attributes for input power: 83 The driver provides the following attributes for temperature:
|
D | ina233.rst | 33 The driver provides the following attributes for input voltage: 47 The driver provides the following attributes for shunt voltage: 53 The driver provides the following attributes for output voltage: 61 The driver provides the following attributes for output current: 71 The driver provides the following attributes for input power:
|
/linux-6.15/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-6.15/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 …]
|
/linux-6.15/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-6.15/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-6.15/tools/perf/Documentation/ |
D | perf-c2c.txt | 89 Following fields are available: tid,pid,iaddr,dso 144 Following perf record options are configured by default: 149 Unless specified otherwise with '-e' option, following events are monitored by 155 following on AMD: 159 and following on PowerPC: 176 The report command workflow is following: 186 For each cacheline in the 1) list we display following data: 235 For each offset in the 2) list we display following data: 285 - node IDs with stats for each ID, in following format: 288 - 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-6.15/drivers/gpu/drm/tiny/ |
D | Kconfig | 125 DRM driver for the following HX8357D panels: 139 DRM driver for the following Ilitek ILI9163 panels: 152 DRM driver for the following Ilitek ILI9225 panels: 166 DRM driver for the following Ilitek ILI9341 panels: 180 DRM driver for the following Ilitek ILI9486 panels: 205 DRM driver for the following Pervasive Displays panels: 220 DRM Driver for the following Sharp Memory Panels: 242 DRM driver for the following Sitronix ST7586 panels: 256 DRM driver for Sitronix ST7715R/ST7735R with one of the following
|
/linux-6.15/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-6.15/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 …]
|
/linux-6.15/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-6.15/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 */
|
12345678910>>...237