/Linux-v5.4/include/acpi/ |
D | acrestyp.h | 186 /* Values for Width field above */ 349 u8 producer_consumer; /* For values, see Producer/Consumer above */ 351 u8 shareable; /* For values, see Interrupt Attributes above */ 352 u8 wake_capable; /* For values, see Interrupt Attributes above */ 354 u8 triggering; /* For values, see Interrupt Attributes above */ 355 u8 polarity; /* For values, see Interrupt Attributes above */ 365 /* Values for GPIO connection_type field above */ 370 /* Values for pin_config field above */ 377 /* Values for io_restriction field above */ 389 … producer_consumer; /* For values, see Producer/Consumer above */\ [all …]
|
D | actbl1.h | 128 /* Values for Type field above */ 155 /* Masks for Flags field above */ 234 /* Boot Error Region (not a subtable, pointed to by Address field above) */ 244 /* Values for block_status flags above */ 252 /* Values for error_severity above */ 263 * Note: The generic error data that follows the error_severity field above 284 /* Flags for Status field above */ 441 /* Types for port_type field above */ 448 /* Subtypes for port_subtype field above */ 496 /* Masks for Flags field above */ [all …]
|
D | actbl2.h | 94 /* Values for subtable Type above */ 113 /* Masks for Flags field above for IORT subtable */ 124 /* Values for cache_coherency field above */ 129 /* Masks for Hints field above */ 136 /* Masks for memory_flags field above */ 156 /* Masks for Flags field above */ 169 /* Values for ats_attribute field above */ 187 /* Values for Model field above */ 196 /* Masks for Flags field above */ 224 /* Values for Model field above */ [all …]
|
/Linux-v5.4/tools/perf/pmu-events/arch/x86/ivybridge/ |
D | memory.json | 42 "PublicDescription": "Loads with latency value being above 4.", 50 "BriefDescription": "Loads with latency value being above 4", 56 "PublicDescription": "Loads with latency value being above 8.", 64 "BriefDescription": "Loads with latency value being above 8", 70 "PublicDescription": "Loads with latency value being above 16.", 78 "BriefDescription": "Loads with latency value being above 16", 84 "PublicDescription": "Loads with latency value being above 32.", 92 "BriefDescription": "Loads with latency value being above 32", 98 "PublicDescription": "Loads with latency value being above 64.", 106 "BriefDescription": "Loads with latency value being above 64", [all …]
|
/Linux-v5.4/drivers/staging/speakup/ |
D | Kconfig | 13 There is also a mailing list at the above url that you 51 help on the Speakup choice above for more info. 60 help on the Speakup choice above for more info. 68 help on the Speakup choice above for more info. 76 Speakup choice above for more info. 84 help on the Speakup choice above for more info. 93 help on the Speakup choice above for more info. 102 configuration help on the Speakup choice above for more 114 choice above for more info. choice 136 configuration help on the Speakup choice above for more [all …]
|
/Linux-v5.4/drivers/misc/lkdtm/ |
D | refcount.c | 32 * A refcount_inc() above the maximum value of the refcount implementation, 50 /* refcount_add() should behave just like refcount_inc() above. */ 68 /* refcount_inc_not_zero() should behave just like refcount_inc() above. */ 80 /* refcount_add_not_zero() should behave just like refcount_inc() above. */ 164 * A refcount_dec_and_test() should act like refcount_dec() above when 180 * above when going negative. 237 * A refcount_add() should act like refcount_inc() above when starting 289 /* Should act like refcount_inc() above from saturated. */ 300 /* Should act like refcount_inc() above from saturated. */ 311 /* Should act like refcount_inc() above from saturated. */ [all …]
|
/Linux-v5.4/tools/perf/pmu-events/arch/x86/broadwellde/ |
D | memory.json | 315 "BriefDescription": "Loads with latency value being above 4", 322 "PublicDescription": "This event counts loads with latency value being above four.", 330 "BriefDescription": "Loads with latency value being above 8", 337 "PublicDescription": "This event counts loads with latency value being above eight.", 345 "BriefDescription": "Loads with latency value being above 16", 352 "PublicDescription": "This event counts loads with latency value being above 16.", 360 "BriefDescription": "Loads with latency value being above 32", 367 "PublicDescription": "This event counts loads with latency value being above 32.", 375 "BriefDescription": "Loads with latency value being above 64", 382 "PublicDescription": "This event counts loads with latency value being above 64.", [all …]
|
/Linux-v5.4/tools/perf/pmu-events/arch/x86/ivytown/ |
D | memory.json | 33 "PublicDescription": "Loads with latency value being above 4.", 41 "BriefDescription": "Loads with latency value being above 4", 47 "PublicDescription": "Loads with latency value being above 8.", 55 "BriefDescription": "Loads with latency value being above 8", 61 "PublicDescription": "Loads with latency value being above 16.", 69 "BriefDescription": "Loads with latency value being above 16", 75 "PublicDescription": "Loads with latency value being above 32.", 83 "BriefDescription": "Loads with latency value being above 32", 89 "PublicDescription": "Loads with latency value being above 64.", 97 "BriefDescription": "Loads with latency value being above 64", [all …]
|
/Linux-v5.4/Documentation/ |
D | unaligned-memory-access.txt | 28 The above may seem a little vague, as memory access can happen in different 39 The rule mentioned above forms what we refer to as natural alignment: 71 It should be obvious from the above that if your code causes unaligned 79 At first, the concepts above may seem a little hard to relate to actual 93 Let us assume that an instance of the above structure resides in memory 101 above case it would insert 2 bytes of padding in between field1 and field2. 114 On a related topic, with the above considerations in mind you may observe 118 above example is:: 148 With the above in mind, let's move onto a real life example of a function 167 In the above function, when the hardware has efficient unaligned access [all …]
|
/Linux-v5.4/include/linux/mfd/ |
D | si476x-reports.h | 20 * false - Indicatedes that the value is above 25 * false - Indicatedes that the value is above 30 * false - Indicatedes that the value is above 35 * false - Indicatedes that the value is above 40 * false - Indicatedes that the value is above 45 * false - Indicatedes that the value is above
|
/Linux-v5.4/drivers/usb/serial/ |
D | whiteheat.h | 94 __u8 parity; /* see WHITEHEAT_PAR_* above */ 95 __u8 sflow; /* see WHITEHEAT_SFLOW_* above */ 98 __u8 hflow; /* see WHITEHEAT_HFLOW_* above */ 145 __u8 mem_type; /* see WHITEHEAT_DUMP_* above */ 146 __u16 addr; /* address, see restrictions above */ 192 __u8 test; /* see WHITEHEAT_TEST_* above*/ 224 see WHITEHEAT_EVENT_* above */ 229 above */ 292 see WHITEHEAT_DO_TEST above */ 293 __u8 status; /* see WHITEHEAT_TEST_* above */
|
/Linux-v5.4/tools/perf/pmu-events/arch/x86/amdfam17h/ |
D | floating-point.json | 53 …LOPS. The number of events logged per cycle can vary from 0 to 64. This event can count above 15.", 60 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Double precisi… 67 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Double precisi… 74 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Double precisi… 81 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Double precisi… 88 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Single precisi… 95 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Single-precisi… 102 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Single-precisi… 109 …er of events logged per cycle can vary from 0 to 64. This event can count above 15. Single-precisi…
|
/Linux-v5.4/Documentation/x86/x86_64/ |
D | 5level-paging.rst | 43 above 47-bit by default. 46 specifying hint address (with or without MAP_FIXED) above 47-bits. 48 If hint address set above 47-bit, but MAP_FIXED is not specified, we try 65 MPX (without MAWA extension) cannot handle addresses above 47-bit, so we 66 need to make sure that MPX cannot be enabled we already have VMA above
|
/Linux-v5.4/drivers/net/ethernet/intel/i40e/ |
D | i40e_lan_hmc.h | 21 u16 cpuid; /* bigger than needed, see above for reason */ 25 u16 dbuff; /* bigger than needed, see above for reason */ 27 u16 hbuff; /* bigger than needed, see above for reason */ 36 u32 rxmax; /* bigger than needed, see above for reason */ 41 u16 lrxqthresh; /* bigger than needed, see above for reason */
|
/Linux-v5.4/Documentation/media/uapi/dvb/ |
D | dvb-frontend-parameters.rst | 72 fe_code_rate_t fec_inner; /* forward error correction (see above) */ 88 fe_code_rate_t fec_inner; /* forward error correction (see above) */ 89 fe_modulation_t modulation; /* modulation type (see above) */ 104 fe_modulation_t modulation; /* modulation type (see above) */ 122 fe_modulation_t constellation; /* modulation type (see above) */
|
/Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
D | gpio-xilinx.txt | 22 - xlnx,all-inputs-2 : as above but for the second channel 23 - xlnx,dout-default-2 : as above but the second channel 24 - xlnx,gpio2-width : as above but for the second channel 25 - xlnx,tri-default-2 : as above but for the second channel
|
/Linux-v5.4/include/uapi/drm/ |
D | vmwgfx_drm.h | 14 * The above copyright notice and this permission notice (including the 236 * @rep: Output data as described above. 237 * @req: Input data as described above. 264 * @rep: Output data as described above. 265 * @req: Input data as described above. 403 * referenced. See not above. 405 * referenced. See note above. 422 * @req: Input data as described above. 423 * @rep: Output data as described above. 472 * @src: Source rect, must be within the defined area above. [all …]
|
/Linux-v5.4/Documentation/networking/ |
D | lapb-module.txt | 112 above. The return values are: 133 variables, the lapb_parms_struct is described above. The valid return values 143 variables, the lapb_parms_struct is described above. The values of t1timer, 200 module with lapb_register (see above) in the structure lapb_register_struct 201 (see above). 207 being requested by a call to lapb_connect_request (see above). The reason is 220 driver has called lapb_disconnect_request (see above). The reason indicates 234 returned in response to a lapb_connect_request (see above) if the remote
|
/Linux-v5.4/include/uapi/linux/ |
D | tee.h | 8 * 1. Redistributions of source code must retain the above copyright notice, 11 * 2. Redistributions in binary form must reproduce the above copyright notice, 69 * @gen_caps: [out] Generic capabilities, defined by TEE_GEN_CAPS_* above 71 * Identifies the TEE implementation, @impl_id is one of TEE_IMPL_ID_* above. 97 * with actual flags as defined by TEE_IOCTL_SHM_* above. 123 * @buf_len: [in] Length of the buffer above 207 * @clnt_login: [in] Login class of client, TEE_IOCTL_LOGIN_* above 351 * with actual flags as defined by TEE_IOCTL_SHM_* above. 375 * ioctl(): as described above operating on the file descriptor from open()
|
/Linux-v5.4/Documentation/ABI/testing/ |
D | sysfs-class-power-wilco | 16 level is above charge_control_end_threshold. 22 Used when charge_type="Custom", as described above. Measured in 29 Used when charge_type="Custom", as described above. Measured in
|
/Linux-v5.4/include/net/ |
D | nl802154.h | 9 * purpose with or without fee is hereby granted, provided that the above 26 /* currently we don't shipping this file via uapi, ignore the above one */ 59 /* add new commands above here */ 84 /* currently we don't shipping this file via uapi, ignore the above one */ 224 * @NL802154_CCA_ENERGY: Energy above threshold 226 * @NL802154_CCA_ENERGY_CARRIER: Carrier sense with energy above threshold
|
/Linux-v5.4/Documentation/devicetree/bindings/display/sunxi/ |
D | sun4i-drm.txt | 21 For a two pipeline system such as the one depicted above, the lines 54 - clock-names: the clock names mentioned above 60 - dma-names: the channel names mentioned above 93 - clock-names: the clock names mentioned above 97 - reset-names: reset names mentioned above 123 - clock-names: the clock names mentioned above 179 - clock-names: the clock names mentioned above 180 - reset-names: the reset names mentioned above 246 - clock-names: clock name mentioned above 263 have reg property with the id of the target TCON, as shown in above graph [all …]
|
/Linux-v5.4/Documentation/misc-devices/ |
D | bh1770glc.txt | 32 by using a delayed work. As long as there is proximity threshold above 69 RW - HI level threshold value. All results above the value 70 trigs an interrupt. 65535 (i.e. sensor_range) disables the above 101 RW - Measurement rate (in Hz) when the level is above threshold
|
/Linux-v5.4/tools/perf/pmu-events/arch/x86/broadwellx/ |
D | memory.json | 315 "BriefDescription": "Randomly selected loads with latency value being above 4", 322 "PublicDescription": "Counts randomly selected loads with latency value being above four.", 330 "BriefDescription": "Randomly selected loads with latency value being above 8", 337 "PublicDescription": "Counts randomly selected loads with latency value being above eight.", 345 "BriefDescription": "Randomly selected loads with latency value being above 16", 352 "PublicDescription": "Counts randomly selected loads with latency value being above 16.", 360 "BriefDescription": "Randomly selected loads with latency value being above 32", 367 "PublicDescription": "Counts randomly selected loads with latency value being above 32.", 375 "BriefDescription": "Randomly selected loads with latency value being above 64", 382 "PublicDescription": "Counts randomly selected loads with latency value being above 64.", [all …]
|
/Linux-v5.4/Documentation/arm/ |
D | booting.rst | 142 A safe location is just above the 128MiB boundary from start of RAM. 157 A safe location is just above the device tree blob which itself will 158 be loaded just above the 128MiB boundary from the start of RAM as 159 recommended above. 176 that it is loaded above 32MiB in order to avoid the need to relocate 193 - r1 = machine type number discovered in (3) above. 221 If the kernel is entered in HYP mode, the above requirements apply to
|