| /linux/drivers/gpio/ |
| H A D | gpio-winbond.c | 212 * @testbit: index of a bit to check whether an actual conflict exists
213 * @warnonly: if set then a conflict isn't fatal (just warn about it),
214 * otherwise disable the particular GPIO port if a conflict
236 * @conflict: description of a device that possibly conflicts with
248 struct winbond_gpio_port_conflict conflict; member
261 .conflict = {
278 /* special conflict handling so doesn't use conflict data */
289 .conflict = {
306 .conflict = {
323 .conflict = {
[all …]
|
| /linux/tools/perf/pmu-events/arch/powerpc/power8/ |
| H A D | cache.json | 41 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to a demand l…
42 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to either onl…
47 … processor's data cache was reloaded from local core's L2 with dispatch conflict due to a demand l…
48 … processor's data cache was reloaded from local core's L2 with dispatch conflict due to either onl…
59 …: "The processor's data cache was reloaded from local core's L2 without conflict due to a demand l…
60 …: "The processor's data cache was reloaded from local core's L2 without conflict due to either onl…
83 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to a demand l…
84 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to either onl…
95 …: "The processor's data cache was reloaded from local core's L3 without conflict due to a demand l…
96 …: "The processor's data cache was reloaded from local core's L3 without conflict due to either onl…
|
| H A D | marked.json | 107 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to a marked l…
113 … "Duration in cycles to reload from local core's L2 with load hit store conflict due to a marked l…
119 … processor's data cache was reloaded from local core's L2 with dispatch conflict due to a marked l…
125 …"BriefDescription": "Duration in cycles to reload from local core's L2 with dispatch conflict due …
143 …: "The processor's data cache was reloaded from local core's L2 without conflict due to a marked l…
149 …"BriefDescription": "Duration in cycles to reload from local core's L2 without conflict due to a m…
179 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to a marked l…
185 …"BriefDescription": "Duration in cycles to reload from local core's L3 with dispatch conflict due …
203 …: "The processor's data cache was reloaded from local core's L3 without conflict due to a marked l…
209 …"BriefDescription": "Duration in cycles to reload from local core's L3 without conflict due to a m…
[all …]
|
| H A D | frontend.json | 125 …Instruction cache was reloaded from local core's L2 with load hit store conflict due to an instruc…
126 …Instruction cache was reloaded from local core's L2 with load hit store conflict due to either an …
131 …sor's Instruction cache was reloaded from local core's L2 with dispatch conflict due to an instruc…
132 …sor's Instruction cache was reloaded from local core's L2 with dispatch conflict due to either an …
143 …processor's Instruction cache was reloaded from local core's L2 without conflict due to an instruc…
144 …processor's Instruction cache was reloaded from local core's L2 without conflict due to either an …
167 …sor's Instruction cache was reloaded from local core's L3 with dispatch conflict due to an instruc…
168 …sor's Instruction cache was reloaded from local core's L3 with dispatch conflict due to either an …
179 …processor's Instruction cache was reloaded from local core's L3 without conflict due to an instruc…
180 …processor's Instruction cache was reloaded from local core's L3 without conflict due to either an …
[all …]
|
| H A D | pipeline.json | 53 …efDescription": "Completion stall due to cache miss that resolves in the L2 or L3 with a conflict",
54 …"PublicDescription": "Completion stall due to cache miss resolving in core's L2/L3 with a conflict"
131 …"BriefDescription": "Completion Stalled due to thread conflict. Group ready to complete but it was…
132 "PublicDescription": "Completion stall due to thread conflict"
|
| H A D | translation.json | 59 …A Page Table Entry was loaded into the TLB from local core's L2 without conflict due to a data sid…
71 … Table Entry was loaded into the TLB from local core's L3 with dispatch conflict due to a data sid…
83 …A Page Table Entry was loaded into the TLB from local core's L3 without conflict due to a data sid…
|
| H A D | other.json | 77 …fDescription": "Read blocked due to interleave conflict. The ifar logic will detect an interleave …
419 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to either dem…
420 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to either onl…
425 … processor's data cache was reloaded from local core's L2 with dispatch conflict due to either dem…
426 … processor's data cache was reloaded from local core's L2 with dispatch conflict due to either onl…
437 …: "The processor's data cache was reloaded from local core's L2 without conflict due to either dem…
438 …: "The processor's data cache was reloaded from local core's L2 without conflict due to either onl…
479 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to either dem…
480 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to either onl…
491 …: "The processor's data cache was reloaded from local core's L3 without conflict due to either dem…
[all …]
|
| /linux/drivers/pci/ |
| H A D | setup-res.c | 80 * disabled ROM can conflict with other BARs. in pci_std_update_resource()
94 * disable decoding so that a half-updated BAR won't conflict in pci_std_update_resource()
140 struct resource *root, *conflict; in pci_claim_resource() local
164 conflict = request_resource_conflict(root, res); in pci_claim_resource()
165 if (conflict) { in pci_claim_resource()
166 pci_info(dev, "%s %pR: can't claim; address conflict with %s %pR\n", in pci_claim_resource()
167 res_name, res, conflict->name, conflict); in pci_claim_resource()
204 struct resource *root, *conflict; in pci_revert_fw_address() local
237 conflict = request_resource_conflict(root, res); in pci_revert_fw_address()
238 if (conflict) { in pci_revert_fw_address()
[all …]
|
| H A D | ecam.c | 34 struct resource *conflict; in pci_ecam_create() local
69 conflict = request_resource_conflict(&iomem_resource, &cfg->res); in pci_ecam_create()
70 if (conflict) { in pci_ecam_create()
72 dev_err(dev, "can't claim ECAM area %pR: address conflict with %s %pR\n", in pci_ecam_create()
73 &cfg->res, conflict->name, conflict); in pci_ecam_create()
|
| /linux/drivers/input/keyboard/ |
| H A D | hpps2atkbd.h | 19 # define CONFLICT(x,y) x macro
21 # define CONFLICT(x,y) y macro
28 #define C_07 CONFLICT( KEY_F12, KEY_F1 )
29 #define C_11 CONFLICT( KEY_LEFTALT, KEY_LEFTCTRL )
30 #define C_14 CONFLICT( KEY_LEFTCTRL, KEY_CAPSLOCK )
31 #define C_58 CONFLICT( KEY_CAPSLOCK, KEY_RIGHTCTRL )
32 #define C_61 CONFLICT( KEY_102ND, KEY_LEFT )
104 #undef CONFLICT
|
| /linux/arch/m68k/fpsp040/ |
| H A D | bugfix.S | 51 | (cmdreg1b[ 9: 7] != cmdreg3b[9:7])) { /* xu conflict only */
53 | xu conflict and NOT an nu conflict */
98 | (cmdreg1b[9:7] != cmdreg3b[9:7])) { /* xu conflict only */
100 | xu conflict and NOT an nu conflict */
185 | Test the register conflict aspect. If opclass0, check for
197 | Check for cu and nu register conflict. If one exists, this takes
198 | priority over a cu and xu conflict.
212 | Check for cu and xu register conflict.
246 | We have the case in which a conflict exists between the cu src or
357 | a cu and nu conflict taking priority an nu conflict. If either,
[all …]
|
| /linux/arch/arm/boot/dts/gemini/ |
| H A D | gemini-wbd111.dts | 36 /* Conflict with ICE */
46 /* Conflict with TVC and extended parallel flash */
52 /* Conflict with TVC and extended parallel flash */
58 /* Conflict with TVC and extended parallel flash */
64 /* Conflict with TVC and extended parallel flash */
|
| H A D | gemini-wbd222.dts | 35 /* Conflict with ICE */
45 /* Conflict with TVC and extended parallel flash */
51 /* Conflict with TVC and extended parallel flash */
57 /* Conflict with TVC and extended parallel flash */
63 /* Conflict with TVC and extended parallel flash */
|
| H A D | gemini-nas4220b.dts | 35 /* Conflict with TVC */
43 /* Conflict with TVC */
52 /* Conflict with TVC */
58 /* Conflict with TVC */
|
| H A D | gemini-rut1xx.dts | 35 /* Conflict with TVC */
45 /* Conflict with ICE */
52 /* Conflict with NAND CE0 */
|
| /linux/arch/arm/boot/dts/microchip/ |
| H A D | at91-sama5d27_som1_ek.dts | 120 status = "disabled"; /* Conflict with leds. */
159 status = "disabled"; /* Conflict with isc. */
178 status = "disabled"; /* Conflict with isc. */
185 status = "disabled"; /* Conflict with isc. */
197 status = "disabled"; /* Conflict with spi6 and i2c6. */
204 status = "okay"; /* Conflict with uart5 and i2c6. */
211 status = "disabled"; /* Conflict with uart5 and spi6. */
498 status = "okay"; /* Conflict with pwm0. */
|
| H A D | at91-sama5d2_xplained.dts | 77 status = "okay"; /* conflict with qspi0 */
86 status = "disabled"; /* conflict with sdmmc1 */
322 status = "disabled"; /* conflict with leds */
327 status = "disabled"; /* conflict with ISC_D2 & ISC_D3 data pins */
347 status = "disabled"; /* conflict with ISC_D2 & ISC_D3 data pins */
367 status = "disabled"; /* conflict with can0 */
697 status = "disabled"; /* conflict with spi0, sdmmc1 */
726 status = "okay"; /* conflict with pwm0 */
|
| H A D | at91-sam9x60ek.dts | 54 status = "okay"; /* Conflict with pwm0. */
117 status = "disabled"; /* Conflict with dbgu. */
137 status = "okay"; /* Conflict with can0. */
309 status = "disabled"; /* Conflict with QSPI. */
580 status = "disabled"; /* Conflict with leds. */
598 status = "disabled"; /* Conflict with flx4. */
604 status = "okay"; /* Conflict with i2s. */
|
| /linux/arch/loongarch/pci/ |
| H A D | acpi.c | 103 struct resource *conflict; in arch_pci_ecam_create() local
127 conflict = request_resource_conflict(&iomem_resource, &cfg->res); in arch_pci_ecam_create()
128 if (conflict) { in arch_pci_ecam_create()
130 dev_err(dev, "can't claim ECAM area %pR: address conflict with %s %pR\n", in arch_pci_ecam_create()
131 &cfg->res, conflict->name, conflict); in arch_pci_ecam_create()
|
| /linux/tools/testing/selftests/net/ |
| H A D | netns-name.sh | 41 # Test move with a conflict
46 fail "Performed a netns move with a name conflict"
52 # Test move with a conflict and rename
87 # Test no conflict of the same name/ifindex in different netns
|
| /linux/arch/s390/tools/ |
| H A D | gcc-thunk-extern.sh | 3 # Borrowed from gcc: gcc/testsuite/gcc.target/s390/nobp-section-type-conflict.c
4 # Checks that we don't get error: section type conflict with ‘put_page’.
|
| /linux/tools/perf/pmu-events/arch/powerpc/power9/ |
| H A D | other.json | 145 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to a demand l…
255 …ssor's data cache was reloaded from local core's L2 with load hit store conflict due to a marked l…
430 "BriefDescription": "TM Load (fav or non-fav) ran into conflict (failed)"
435 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to a marked l…
500 "BriefDescription": "TM Store (fav or non-fav) ran into conflict (failed)"
630 … processor's data cache was reloaded from local core's L3 with dispatch conflict due to a demand l…
640 …"BriefDescription": "Duration in cycles to reload from local core's L2 with dispatch conflict due …
905 …"BriefDescription": "Duration in cycles to reload from local core's L2 without conflict due to a m…
965 …Description": "Read blocked due to interleave conflict. The ifar logic will detect an interleave …
1160 …spatch attempts for this thread that failed due to an address collision conflict with an L2 machin…
[all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | style.rst | 10 they may break some tooling, may conflict with other tests, and may not be run
134 As tests are themselves functions, their names cannot conflict with
145 name conflict with the macro itself.
198 subdirectory to not conflict with other source files (e.g. for
|
| /linux/net/mctp/test/ |
| H A D | sock-test.c | 259 /* Pairs of binds and whether they will conflict */
261 /* Both ADDR_ANY, conflict */
264 /* Same specific EID, conflict */
275 * vs specific EID, explicit default net 1, conflict
287 /* specific remote peer doesn't conflict with any-peer bind */
|
| /linux/Documentation/networking/device_drivers/ethernet/cirrus/ |
| H A D | cs89x0.rst | 425 mode and that the range of memory addresses assigned does not conflict
457 Failure of a test item indicates a possible system resource conflict with
519 An IO conflict occurs when two or more adapter use the same ISA resource (IO
520 address, memory address or IRQ). You can usually detect an IO conflict in one
532 memory address conflict.
534 If an IO conflict occurs, run the CS8900/20 Setup Utility and perform a
535 diagnostic self-test. Normally, the ISA resource in conflict will fail the
537 resource in conflict. Run the diagnostics again to check for further IO
|