| /linux/tools/perf/pmu-events/arch/powerpc/power8/ |
| H A D | memory.json | 5 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for all data …
6 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
11 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for a demand …
12 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
47 …"BriefDescription": "Initial and Final Pump Scope was group pump (prediction=correct) for a demand…
48 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was group pu…
53 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump …
54 …Initial Pump Scope OR Final Pump Scope(Group) got data from source that was at smaller scope(Chip)…
59 …"BriefDescription": "Final Pump Scope (Group) ended up larger than Initial Pump Scope (Chip) for a…
60 …p) to get data sourced, ended up larger than Initial Pump Scope (Chip) Final pump was group pump a…
[all …]
|
| H A D | frontend.json | 71 …"BriefDescription": "Initial and Final Pump Scope was chip pump (prediction=correct) for an instru…
72 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was chip pum…
239 …"BriefDescription": "Initial and Final Pump Scope was group pump (prediction=correct) for an instr…
240 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was group pu…
245 …"BriefDescription": "Final Pump Scope (Group) ended up either larger or smaller than Initial Pump …
246 …Initial Pump Scope OR Final Pump Scope(Group) got data from source that was at smaller scope(Chip)…
251 …"BriefDescription": "Final Pump Scope (Group) ended up larger than Initial Pump Scope (Chip) for a…
252 …p) to get data sourced, ended up larger than Initial Pump Scope (Chip) Final pump was group pump a…
275 …"BriefDescription": "Initial and Final Pump Scope was system pump (prediction=correct) for an inst…
276 …"PublicDescription": "Initial and Final Pump Scope and data sourced across this scope was system p…
[all …]
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | sm7125-xiaomi-common.dtsi | 136 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
142 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
148 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
154 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
163 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
169 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
175 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
181 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
187 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
193 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
[all …]
|
| H A D | sdx75-idp.dts | 134 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
141 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
148 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
155 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
162 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
169 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
176 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
183 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
190 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
197 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
[all …]
|
| H A D | sm8250-samsung-common.dtsi | 86 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
96 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
103 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
110 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
120 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
127 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
134 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
|
| H A D | sc8280xp-huawei-gaokun3.dts | 329 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
337 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
344 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
351 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
361 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
368 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
379 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
389 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
396 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
407 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
[all …]
|
| H A D | sdm850-lenovo-yoga-c630.dts | 152 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
158 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
164 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
191 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
198 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
211 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
218 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
224 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
249 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
259 regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
[all …]
|
| /linux/tools/testing/selftests/uevent/ |
| H A D | uevent_filtering.c | 382 * - Open uevent listening socket in initial network namespace owned by in TEST()
383 * initial user namespace. in TEST()
384 * - Trigger uevent in initial network namespace owned by initial user in TEST()
396 * - Open uevent listening socket in non-initial network namespace in TEST()
397 * owned by initial user namespace. in TEST()
398 * - Trigger uevent in initial network namespace owned by initial user in TEST()
411 * - Open uevent listening socket in initial network namespace in TEST()
412 * owned by initial use in TEST()
[all...] |
| /linux/arch/arm/boot/dts/qcom/ |
| H A D | qcom-sdx55-mtp.dts | 117 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
123 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
129 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
135 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
141 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
147 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
153 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
159 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
165 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
171 regulator-initial-mode = <RPMH_REGULATOR_MODE_LPM>;
[all …]
|
| /linux/usr/ |
| H A D | Kconfig | 56 bool "Support initial ramdisk/ramfs compressed using gzip"
60 Support loading of a gzip encoded initial ramdisk or cpio buffer.
64 bool "Support initial ramdisk/ramfs compressed using bzip2"
68 Support loading of a bzip2 encoded initial ramdisk or cpio buffer
72 bool "Support initial ramdisk/ramfs compressed using LZMA"
76 Support loading of a LZMA encoded initial ramdisk or cpio buffer
80 bool "Support initial ramdisk/ramfs compressed using XZ"
84 Support loading of a XZ encoded initial ramdisk or cpio buffer.
88 bool "Support initial ramdisk/ramfs compressed using LZO"
92 Support loading of a LZO encoded initial ramdisk or cpio buffer
[all …]
|
| /linux/LICENSES/dual/ |
| H A D | CDDL-1.0 | 35 1.5. "Initial Developer" means the individual or entity that first
45 extent possible, whether at the time of the initial grant or
86 2.1. The Initial Developer Grant.
89 to third party intellectual property claims, the Initial Developer
94 trademark) Licensable by Initial Developer, to use,
106 effective on the date Initial Developer first distributes
186 the Initial Developer.
196 on behalf of the Initial Developer or any Contributor. You must
199 agree to indemnify the Initial Developer and every Contributor for
200 any liability incurred by the Initial Developer or such Contributor
[all …]
|
| H A D | MPL-1.1 | 42 1.6. "Initial Developer" means the individual or entity identified
43 as the Initial Developer in the Source Code notice required by Exhibit
52 extent possible, whether at the time of the initial grant or
97 2.1. The Initial Developer Grant.
98 The Initial Developer hereby grants You a world-wide, royalty-free,
102 trademark) Licensable by Initial Developer to use, reproduce,
113 effective on the date Initial Developer first distributes
189 Code provided by the Initial Developer and including the name of the
190 Initial Developer in (a) the Source Code, and (b) in any notice in an
235 may do so only on Your own behalf, and not on behalf of the Initial
[all …]
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | acpi-lid.rst | 35 initial returning value. When the AML tables implement this control method
36 with cached value, the initial returning value is likely not reliable.
37 There are platforms always return "closed" as initial lid state.
71 events and the unreliable initial state notification, Linux users can use
76 initial lid state using the returning value of the _LID control method
81 of the _LID control method is reliable but the initial lid state
89 initial lid state as "opened" and whether the "opened"/"closed" events
93 control method is not reliable and the initial lid state notification is
97 and the unreliable initial state notification, Linux users should always
102 initial lid state and there is a compensation mechanism implemented to
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | smsc,usb3503.yaml | 54 initial-mode:
57 Specifies initial mode. 1 for Hub mode, 2 for standby mode and 3 for bypass mode.
98 initial-mode:
102 initial-mode:
120 initial-mode = <1>;
139 initial-mode = <3>;
151 initial-mode = <1>; /* initialize in HUB mode */
|
| H A D | usb4604.txt | 10 - initial-mode: Should specify initial mode.
18 initial-mode = <1>;
|
| /linux/include/uapi/linux/hdlc/ |
| H A D | ioctl.h | 25 #define PARITY_CRC16_PR0 2 /* CRC16, initial value 0x0000 */
26 #define PARITY_CRC16_PR1 3 /* CRC16, initial value 0xFFFF */
27 #define PARITY_CRC16_PR0_CCITT 4 /* CRC16, initial 0x0000, ITU-T version */
28 #define PARITY_CRC16_PR1_CCITT 5 /* CRC16, initial 0xFFFF, ITU-T version */
29 #define PARITY_CRC32_PR0_CCITT 6 /* CRC32, initial value 0x00000000 */
30 #define PARITY_CRC32_PR1_CCITT 7 /* CRC32, initial value 0xFFFFFFFF */
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| H A D | rohm,bd96801-pmic.yaml | 97 /* 0.5V min INITIAL - 150 mV tune */
103 rohm,initial-voltage-microvolt = <500000>;
114 rohm,initial-voltage-microvolt = <3000000>;
125 rohm,initial-voltage-microvolt = <600000>;
136 rohm,initial-voltage-microvolt = <600000>;
147 rohm,initial-voltage-microvolt = <500000>;
158 rohm,initial-voltage-microvolt = <300000>;
169 rohm,initial-voltage-microvolt = <500000>;
|
| /linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 95 initial contact, which oversees the process of handling such issues under
99 will form the initial response team for a particular issue. The initial
128 the Contact section above. This initial contact should contain a
136 mailing list which will be used for initial discussion with the reporter,
143 form the initial response team and will be responsible for handling the
144 issue after initial contact. The hardware security team is supporting the
171 The disclosing party provides detailed information to the initial response
181 The initial response team sets up an encrypted mailing-list or repurposes
195 The initial response team will identify further experts from the Linux
275 Neither the hardware security team nor the initial response team assign
[all …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | rohm,bd96801-regulator.yaml | 31 rohm,initial-voltage-microvolt:
33 Initial voltage for regulator. Voltage can be tuned +/-150 mV from
48 rohm,initial-voltage-microvolt:
50 Initial voltage for regulator. Voltage can be tuned +/-150 mV from
|
| H A D | microchip,mcp16502.yaml | 58 regulator-initial-mode:
61 description: Initial operating mode
97 regulator-initial-mode = <2>;
116 regulator-initial-mode = <2>;
135 regulator-initial-mode = <2>;
154 regulator-initial-mode = <2>;
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-dqevent.rst | 145 called an initial event will be generated for that filehandle with
174 if the HPD is low, then an initial event will be generated for that
183 if the HPD is high, then an initial event will be generated for that
192 if the 5V is low, then an initial event will be generated for that
201 if the 5V is high, then an initial event will be generated for that
213 * .. _`CEC-EVENT-FL-INITIAL-STATE`:
217 - Set for the initial events that are generated when the device is
219 applications to learn the initial state of the CEC adapter at
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | nxp,pcf8575.yaml | 55 lines-initial-states:
58 Bitmask that specifies the initial state of each line.
103 # lines-initial-states XOR reset-gpios
105 # may not match passed lines-initial-states
108 - lines-initial-states
|
| /linux/drivers/crypto/ccree/ |
| H A D | cc_hash.h | 84 * cc_digest_len_addr() - Gets the initial digest length
90 * Returns the address of the initial digest length in SRAM
95 * cc_larval_digest_addr() - Gets the address of the initial digest in SRAM
102 * The address of the initial digest in SRAM
|
| /linux/arch/s390/mm/ |
| H A D | pfault.c | 125 * Get the external interruption subcode & pfault initial/completion in pfault_interrupt()
147 * Initial interrupt was faster than the completion in pfault_interrupt()
159 * Completion interrupt was faster than initial in pfault_interrupt()
160 * interrupt. Set pfault_wait to -1 so the initial in pfault_interrupt()
179 * Completion interrupt was faster than the initial in pfault_interrupt()
186 * Initial interrupt arrived before completion in pfault_interrupt()
|
| /linux/include/linux/ |
| H A D | percpu-refcount.h | 11 * refcounts; you have to keep track of your initial refcount, and then when you
12 * start shutting down you call percpu_ref_kill() _before_ dropping the initial
24 * it's safe to drop the initial ref.
35 * and it's then safe to drop the initial ref with percpu_ref_put().
43 * explicit synchronization to ensure the initial refcount can only be dropped
136 * percpu_ref_kill - drop the initial ref
139 * Must be used to drop the initial ref on a percpu refcount; must be called
143 * and dropping the initial ref.
|