| /linux-4.1.27/Documentation/ioctl/ |
| D | ioctl-number.txt | 65 0x00 00-1F linux/fs.h conflict!
66 0x00 00-1F scsi/scsi_ioctl.h conflict!
67 0x00 00-1F linux/fb.h conflict!
68 0x00 00-1F linux/wavefront.h conflict!
88 '3' 00-0F drivers/s390/char/raw3270.h conflict!
89 '3' 00-1F linux/suspend_ioctls.h conflict!
94 '@' 00-0F linux/radeonfb.h conflict!
95 '@' 00-0F drivers/video/aty/aty128fb.c conflict!
96 'A' 00-1F linux/apm_bios.h conflict!
97 'A' 00-0F linux/agpgart.h conflict!
[all …]
|
| /linux-4.1.27/kernel/ |
| D | resource.c | 294 struct resource *conflict; in request_resource_conflict() local
297 conflict = __request_resource(root, new); in request_resource_conflict()
299 return conflict; in request_resource_conflict()
311 struct resource *conflict; in request_resource() local
313 conflict = request_resource_conflict(root, new); in request_resource()
314 return conflict ? -EBUSY : 0; in request_resource()
637 struct resource *conflict; in reallocate_resource() local
661 conflict = __request_resource(root, old); in reallocate_resource()
662 BUG_ON(conflict); in reallocate_resource()
808 struct resource *conflict; in insert_resource_conflict() local
[all …]
|
| /linux-4.1.27/drivers/pci/ |
| D | setup-res.c | 111 struct resource *root, *conflict; in pci_claim_resource() local
127 conflict = request_resource_conflict(root, res); in pci_claim_resource()
128 if (conflict) { in pci_claim_resource()
130 resource, res, conflict->name, conflict); in pci_claim_resource()
169 struct resource *root, *conflict; in pci_revert_fw_address() local
191 conflict = request_resource_conflict(root, res); in pci_revert_fw_address()
192 if (conflict) { in pci_revert_fw_address()
194 resno, res, conflict->name, conflict); in pci_revert_fw_address()
|
| D | probe.c | 2035 struct resource *parent_res, *conflict; in pci_bus_insert_busn_res() local
2048 conflict = request_resource_conflict(parent_res, res); in pci_bus_insert_busn_res()
2050 if (conflict) in pci_bus_insert_busn_res()
2054 parent_res, conflict->name, conflict); in pci_bus_insert_busn_res()
2056 return conflict == NULL; in pci_bus_insert_busn_res()
|
| /linux-4.1.27/drivers/gpu/vga/ |
| D | vgaarb.c | 174 struct vga_device *conflict; in __vga_tryget() local
206 list_for_each_entry(conflict, &vga_list, list) { in __vga_tryget()
211 if (vgadev == conflict) in __vga_tryget()
217 if (!vga_conflicts(vgadev->pdev, conflict->pdev)) in __vga_tryget()
226 if (vgadev->pdev->bus != conflict->pdev->bus) { in __vga_tryget()
234 if (conflict->locks & lwants) in __vga_tryget()
235 return conflict; in __vga_tryget()
241 match = lwants & conflict->owns; in __vga_tryget()
255 if (!conflict->bridge_has_one_vga) { in __vga_tryget()
256 if ((match & conflict->decodes) & VGA_RSRC_LEGACY_MEM) in __vga_tryget()
[all …]
|
| /linux-4.1.27/arch/x86/pci/ |
| D | acpi.c | 298 struct resource *res, *conflict, *root = NULL; in add_resources() local
312 conflict = insert_resource_conflict(root, res); in add_resources()
313 if (conflict) { in add_resources()
316 res, conflict->name, conflict); in add_resources()
|
| /linux-4.1.27/Documentation/blackfin/ |
| D | bfin-gpio-notes.txt | 30 2. Avoiding resource conflict
32 Followed function groups are used to avoiding resource conflict,
64 GPIO interrupt. This will really cause resource conflict. So if
|
| /linux-4.1.27/arch/m68k/fpsp040/ |
| D | bugfix.S | 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,
368 | We have the case in which a conflict exists between the cu src or
|
| /linux-4.1.27/net/sctp/ |
| D | bind_addr.c | 344 int conflict = 0; in sctp_bind_addr_conflict() local
363 conflict = sp->pf->cmp_addr(&laddr->a, addr, sp); in sctp_bind_addr_conflict()
364 if (conflict) in sctp_bind_addr_conflict()
369 return conflict; in sctp_bind_addr_conflict()
|
| /linux-4.1.27/include/linux/platform_data/ |
| D | keypad-omap.h | 45 #error Group bits in conflict with keynum bits
|
| /linux-4.1.27/drivers/staging/lustre/lustre/osc/ |
| D | osc_lock.c | 1013 struct cl_lock *conflict = NULL; in osc_lock_enqueue_wait() local
1059 conflict = scan; in osc_lock_enqueue_wait()
1064 if (conflict) { in osc_lock_enqueue_wait()
1071 lock, conflict); in osc_lock_enqueue_wait()
1072 cl_lock_put(env, conflict); in osc_lock_enqueue_wait()
1076 lock, conflict); in osc_lock_enqueue_wait()
1078 lu_ref_add(&conflict->cll_reference, "cancel-wait", in osc_lock_enqueue_wait()
1080 lock->cll_conflict = conflict; in osc_lock_enqueue_wait()
|
| D | osc_cache.c | 630 struct osc_extent *conflict = NULL; in osc_extent_find() local
719 conflict = osc_extent_get(ext); in osc_extent_find()
785 LASSERT(conflict == NULL); in osc_extent_find()
791 } else if (conflict == NULL) { in osc_extent_find()
806 if (conflict != NULL) { in osc_extent_find()
811 rc = osc_extent_wait(env, conflict, OES_INV); in osc_extent_find()
812 osc_extent_put(env, conflict); in osc_extent_find()
813 conflict = NULL; in osc_extent_find()
|
| /linux-4.1.27/drivers/staging/lustre/lustre/obdclass/ |
| D | cl_lock.c | 1213 struct cl_lock *conflict; in cl_lock_enqueue_wait() local
1220 conflict = lock->cll_conflict; in cl_lock_enqueue_wait()
1226 cl_lock_mutex_get(env, conflict); in cl_lock_enqueue_wait()
1227 cl_lock_trace(D_DLMTRACE, env, "enqueue wait", conflict); in cl_lock_enqueue_wait()
1228 cl_lock_cancel(env, conflict); in cl_lock_enqueue_wait()
1229 cl_lock_delete(env, conflict); in cl_lock_enqueue_wait()
1231 while (conflict->cll_state != CLS_FREEING) { in cl_lock_enqueue_wait()
1232 rc = cl_lock_state_wait(env, conflict); in cl_lock_enqueue_wait()
1236 cl_lock_mutex_put(env, conflict); in cl_lock_enqueue_wait()
1237 lu_ref_del(&conflict->cll_reference, "cancel-wait", lock); in cl_lock_enqueue_wait()
[all …]
|
| /linux-4.1.27/drivers/gpu/drm/radeon/ |
| D | radeon_connectors.c | 439 struct drm_connector *conflict; in radeon_connector_analog_encoder_conflict_solve() local
443 list_for_each_entry(conflict, &dev->mode_config.connector_list, head) { in radeon_connector_analog_encoder_conflict_solve()
444 if (conflict == connector) in radeon_connector_analog_encoder_conflict_solve()
447 radeon_conflict = to_radeon_connector(conflict); in radeon_connector_analog_encoder_conflict_solve()
449 if (conflict->encoder_ids[i] == 0) in radeon_connector_analog_encoder_conflict_solve()
453 if (conflict->encoder_ids[i] == encoder->base.id) { in radeon_connector_analog_encoder_conflict_solve()
454 if (conflict->status != connector_status_connected) in radeon_connector_analog_encoder_conflict_solve()
462 conflict->name); in radeon_connector_analog_encoder_conflict_solve()
465 conflict->status = connector_status_disconnected; in radeon_connector_analog_encoder_conflict_solve()
466 radeon_connector_update_scratch_regs(conflict, connector_status_disconnected); in radeon_connector_analog_encoder_conflict_solve()
[all …]
|
| /linux-4.1.27/Documentation/networking/ |
| D | cs89x0.txt | 416 mode and that the range of memory addresses assigned does not conflict
443 Failure of a test item indicates a possible system resource conflict with
502 An IO conflict occurs when two or more adapter use the same ISA resource (IO
503 address, memory address or IRQ). You can usually detect an IO conflict in one
515 memory address conflict.
517 If an IO conflict occurs, run the CS8900/20 Setup Utility and perform a
518 diagnostic self-test. Normally, the ISA resource in conflict will fail the
520 resource in conflict. Run the diagnostics again to check for further IO
|
| D | 3c509.txt | 143 increasing you likely have a physical conflict with two devices trying to
144 use the same ISA IRQ line. The common conflict is with a sound card on IRQ10
|
| D | README.sb1000 | 70 conflict with one another. Then test this configuration by running the
155 Make sure they don't conflict with any other pieces of hardware first! Then
|
| D | ltpc.txt | 69 board. Set the switches so as not to conflict with other hardware.
|
| D | arcnet-hardware.txt | 309 copying buffers around. Make SURE it doesn't conflict with any other
1643 Note: - Do not use JP11=IRQ6, it may conflict with your Floppy Disk
1646 Hard Disk, it may conflict with their controllers
1709 some others that I didn't write here the card seems to conflict with the
|
| D | ip-sysctl.txt | 1225 privacy stable address generation if a DAD conflict is
1231 address if a DAD conflict is detected.
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | imx6dl-tx6u-811x.dts | 95 status = "disabled"; /* pad conflict with backlight1 PWM */
|
| D | imx6q-tx6q-1110.dts | 95 status = "disabled"; /* pad conflict with backlight1 PWM */
|
| D | sama5d4.dtsi | 1083 /* external trigger is conflict with USBA_VBUS */
1373 AT91_PIOB 1 AT91_PERIPH_C AT91_PINCTRL_NONE /* ISI_PCK, conflict with G0_RXCK */
1531 <AT91_PIOC 4 AT91_PERIPH_B AT91_PINCTRL_NONE /* MCI0_CK, conflict with PCK1(ISI_MCK) */
1532 AT91_PIOC 5 AT91_PERIPH_B AT91_PINCTRL_PULL_UP /* MCI0_CDB, conflict with NAND_D0 */
1533 AT91_PIOC 6 AT91_PERIPH_B AT91_PINCTRL_PULL_UP /* MCI0_DB0, conflict with NAND_D1 */
1538 <AT91_PIOC 7 AT91_PERIPH_B AT91_PINCTRL_PULL_UP /* MCI0_DB1, conflict with NAND_D2 */
1539 AT91_PIOC 8 AT91_PERIPH_B AT91_PINCTRL_PULL_UP /* MCI0_DB2, conflict with NAND_D3 */
1540 AT91_PIOC 9 AT91_PERIPH_B AT91_PINCTRL_PULL_UP /* MCI0_DB3, conflict with NAND_D4 */
|
| D | imx6qdl-sabreauto.dtsi | 53 status = "disabled"; /* pin conflict with WEIM NOR */
481 status = "disabled"; /* pin conflict with SPI NOR */
|
| D | ste-href-family-pinctrl.dtsi | 195 * Activating I2C4 will conflict with UART1 about the same pins so do not
|
| /linux-4.1.27/arch/x86/kernel/cpu/ |
| D | perf_event_intel_cqm.c | 832 bool conflict = false; in intel_cqm_setup_event() local
849 conflict = true; in intel_cqm_setup_event()
852 if (conflict) in intel_cqm_setup_event()
|
| D | perf_event_intel.c | 2958 EVENT_ATTR_STR(tx-conflict, tx_conflict, "event=0x54,umask=0x1");
2963 EVENT_ATTR_STR(el-conflict, el_conflict, "event=0x54,umask=0x1");
|
| /linux-4.1.27/arch/um/ |
| D | Kconfig.net | 48 more than one without conflict. If you don't need UML networking,
85 conflict. If you don't need UML networking, say N.
108 more than one without conflict. If you don't need UML networking,
|
| /linux-4.1.27/Documentation/ |
| D | init.txt | 22 C) Possibly a conflict in console= setup --> initial console unavailable.
|
| D | vgaarbiter.txt | 16 (e.g. two server in parallel). Their address assignments conflict. Moreover,
128 might conflict and disable their IOs and/or Memory access, including VGA
|
| D | devices.txt | 1913 There is currently a device-naming conflict between
2247 relocated to major 183 due to an unfortunate conflict.
2594 It had to be moved due to an unfortunate conflict.
|
| D | memory-barriers.txt | 2108 conflict on any particular lock.
2674 cacheline over to the accessing CPU and propagate the effects upon conflict.
|
| /linux-4.1.27/Documentation/serial/ |
| D | moxa-smartio | 123 You may need to adjust IRQ usage in BIOS to avoid from IRQ conflict
493 Error msg: Request_irq fail, IRQ(?) may be conflict with another device.
511 Load Moxa driver fail, the major number may conflict with other devices.
518 conflict with other devices. Please refer to previous section 3.7 to
|
| D | rocket.txt | 119 conflict with any other cards in the system, including other
|
| /linux-4.1.27/Documentation/fb/ |
| D | intelfb.txt | 46 for the least amount). Note, an arbitrary setting may conflict
|
| D | udlfb.txt | 114 (e.g. X with --shared-vt) are in conflict.
|
| D | intel810.txt | 124 arbitrary setting may conflict with XFree86.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | befs.txt | 42 the kernel. Because of this naming conflict, on Linux the BeOS
|
| /linux-4.1.27/arch/powerpc/boot/dts/ |
| D | virtex440-ml507.dts | 132 xlnx,ppc440mc-bank-conflict-mask = <0xc00000>;
140 xlnx,ppc440mc-row-conflict-mask = <0x3ffe00>;
|
| D | virtex440-ml510.dts | 127 xlnx,ppc440mc-bank-conflict-mask = <0x1800000>;
135 xlnx,ppc440mc-row-conflict-mask = <0x7ffe00>;
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | fsl,ssi.txt | 86 drivers (fsldma) will attempt to use them, and it will conflict with the
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | Introduction | 295 example, if you get device conflict errors) try the
321 or DMA conflict. Move the card to another IRQ or DMA
323 when I had an IRQ conflict.
|
| D | SoundPro | 69 in your isapnp configuration file, and that there is no conflict with
|
| D | README.OSS | 162 - "I/O error". Almost certainly (99%) it's an IRQ or DMA conflict.
463 will cause a conflict with these cards. So check if your card is
481 cause a conflict. So check if your card is listed in this file before
736 some drivers (like MPU401) may conflict with your SCSI controller and
787 these cards will cause a conflict. Also enabling MPU401 on a system
825 conflict.
|
| /linux-4.1.27/Documentation/trace/ |
| D | tracepoints.txt | 102 tracepoint name over all the kernel to make sure no type conflict will
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-i801 | 147 that the unhidden SMBus doesn't conflict with e.g. ACPI.
|
| /linux-4.1.27/drivers/target/ |
| D | target_core_pr.c | 136 int conflict = 0; in target_check_scsi2_reservation_conflict() local
174 conflict = 1; in target_check_scsi2_reservation_conflict()
187 conflict = (list_empty(&pr_tmpl->registration_list)) ? 0 : 1; in target_check_scsi2_reservation_conflict()
191 if (conflict) { in target_check_scsi2_reservation_conflict()
|
| /linux-4.1.27/Documentation/devicetree/bindings/bus/ |
| D | mvebu-mbus.txt | 206 The operating system may insert additional mbus windows that do not conflict
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | transactional_memory.txt | 56 If, in the meantime, there is a conflict with the locations accessed by the
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | hdspm.txt | 124 !!!! This is a hardware-function but is in conflict with the
|
| D | CMIPCI.txt | 215 0x330. Choose a value that doesn't conflict with other cards.
|
| D | ALSA-Configuration.txt | 2213 the same time as long as they don't conflict).
2216 hot-plugging and the resultant slot conflict. For example, in the
|
| D | HD-Audio.txt | 29 driver might not work properly because of conflict of mixer elements.
|
| /linux-4.1.27/mm/ |
| D | swapfile.c | 418 bool conflict; in scan_swap_map_ssd_cluster_conflict() local
421 conflict = !cluster_is_null(&si->free_cluster_head) && in scan_swap_map_ssd_cluster_conflict()
425 if (!conflict) in scan_swap_map_ssd_cluster_conflict()
|
| /linux-4.1.27/sound/oss/ |
| D | Kconfig | 329 will cause a conflict.
341 will cause a conflict. Also, enabling MPU401 on a system that
|
| D | CHANGELOG | 147 SB DMA of MAD16 so that it doesn't conflict with codec's DMA channels.
|
| /linux-4.1.27/Documentation/arm/pxa/ |
| D | mfp.txt | 86 because pin configuration definitions may conflict in these file (i.e.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.megaraid | 172 conflict.
286 1. Bump up the version of scsi module due to its conflict.
|
| /linux-4.1.27/arch/m68k/ |
| D | Kconfig.cpu | 351 workaround of disabling interrupts, it can conflict with DMA
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 35 Occasionally, the kernel's coding style will run into conflict with an
387 likely to conflict with work being done by other developers. Needless to
|
| D | 6.Followthrough | 126 Other times, conflict resolution will involve working with the other
|
| D | 2.Process | 252 core kernel function prototype, for example, will conflict with any other
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pcieaer-howto.txt | 54 behavior. To avoid this conflict, a successful load of the AER Root driver
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | kconfig-language.txt | 43 type must not conflict.
|
| /linux-4.1.27/tools/perf/ |
| D | design.txt | 209 a conflict with some other event), then the counter goes into an
|
| /linux-4.1.27/drivers/input/keyboard/ |
| D | Kconfig | 106 The PrecisionBook has five keys that conflict with those used by most
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 427 they will conflict. They can block and allocate. A client driver
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.HiSax | 79 You can combine any card, if there is no conflict between the resources
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 602 creation and file open to such servers. Fix semaphore conflict which causes
1040 show range as locked when there is a conflict with an existing lock.
|
| /linux-4.1.27/sound/pci/ |
| D | Kconfig | 798 depends on SND_OXYGEN=n && SND_VIRTUOSO=n # PCI ID conflict
|
| /linux-4.1.27/drivers/input/touchscreen/ |
| D | Kconfig | 717 streaming data, this must not conflict with other AC97C drivers.
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 682 conflict with the cache trying to write pages to the cache (which may itself
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 113 13.11 UML build conflict between ptrace.h and ucontext.h
1028 may conflict with the UML IP address-based scheme
3990 13.11. UML build conflict between ptrace.h and ucontext.h
|
| /linux-4.1.27/Documentation/x86/ |
| D | boot.txt | 925 conflict with actual kernel options now or in the future.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 950 guest physical address space and must not conflict with any memory slot
1069 guest physical address space and must not conflict with any memory slot
|
| /linux-4.1.27/Documentation/block/ |
| D | biodoc.txt | 926 results in some sort of conflict internally,
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1406 or to conflict in title with any Invariant Section.
|