Home
last modified time | relevance | path

Searched refs:conflict (Results 1 – 25 of 67) sorted by relevance

123

/linux-3.4.99/Documentation/ioctl/
Dioctl-number.txt65 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!
86 '3' 00-0F drivers/s390/char/raw3270.h conflict!
87 '3' 00-1F linux/suspend_ioctls.h conflict!
91 '@' 00-0F linux/radeonfb.h conflict!
92 '@' 00-0F drivers/video/aty/aty128fb.c conflict!
93 'A' 00-1F linux/apm_bios.h conflict!
94 'A' 00-0F linux/agpgart.h conflict!
[all …]
/linux-3.4.99/kernel/
Dresource.c239 struct resource *conflict; in request_resource_conflict() local
242 conflict = __request_resource(root, new); in request_resource_conflict()
244 return conflict; in request_resource_conflict()
256 struct resource *conflict; in request_resource() local
258 conflict = request_resource_conflict(root, new); in request_resource()
259 return conflict ? -EBUSY : 0; in request_resource()
479 struct resource *conflict; in reallocate_resource() local
503 conflict = __request_resource(root, old); in reallocate_resource()
504 BUG_ON(conflict); in reallocate_resource()
650 struct resource *conflict; in insert_resource_conflict() local
[all …]
/linux-3.4.99/drivers/pci/
Dsetup-res.c96 struct resource *root, *conflict; in pci_claim_resource() local
105 conflict = request_resource_conflict(root, res); in pci_claim_resource()
106 if (conflict) { in pci_claim_resource()
109 res, conflict->name, conflict); in pci_claim_resource()
174 struct resource *root, *conflict; in pci_revert_fw_address() local
197 conflict = request_resource_conflict(root, res); in pci_revert_fw_address()
198 if (conflict) { in pci_revert_fw_address()
201 res, conflict->name, conflict); in pci_revert_fw_address()
/linux-3.4.99/drivers/gpu/vga/
Dvgaarb.c166 struct vga_device *conflict; in __vga_tryget() local
198 list_for_each_entry(conflict, &vga_list, list) { in __vga_tryget()
203 if (vgadev == conflict) in __vga_tryget()
209 if (!vga_conflicts(vgadev->pdev, conflict->pdev)) in __vga_tryget()
218 if (vgadev->pdev->bus != conflict->pdev->bus) { in __vga_tryget()
226 if (conflict->locks & lwants) in __vga_tryget()
227 return conflict; in __vga_tryget()
234 WARN_ON(conflict->owns & ~conflict->decodes); in __vga_tryget()
235 match = lwants & conflict->owns; in __vga_tryget()
246 if (!conflict->bridge_has_one_vga) { in __vga_tryget()
[all …]
/linux-3.4.99/arch/x86/pci/
Dacpi.c293 struct resource *res, *root, *conflict; in add_resources() local
308 conflict = insert_resource_conflict(root, res); in add_resources()
309 if (conflict) in add_resources()
312 res, conflict->name, conflict); in add_resources()
/linux-3.4.99/Documentation/blackfin/
Dbfin-gpio-notes.txt30 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-3.4.99/net/sctp/
Dbind_addr.c358 int conflict = 0; in sctp_bind_addr_conflict() local
377 conflict = sp->pf->cmp_addr(&laddr->a, addr, sp); in sctp_bind_addr_conflict()
378 if (conflict) in sctp_bind_addr_conflict()
383 return conflict; in sctp_bind_addr_conflict()
/linux-3.4.99/arch/m68k/fpsp040/
Dbugfix.S185 | 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-3.4.99/arch/arm/plat-omap/include/plat/
Dkeypad.h47 #error Group bits in conflict with keynum bits
/linux-3.4.99/drivers/gpu/drm/radeon/
Dradeon_connectors.c196 struct drm_connector *conflict; in radeon_connector_analog_encoder_conflict_solve() local
200 list_for_each_entry(conflict, &dev->mode_config.connector_list, head) { in radeon_connector_analog_encoder_conflict_solve()
201 if (conflict == connector) in radeon_connector_analog_encoder_conflict_solve()
204 radeon_conflict = to_radeon_connector(conflict); in radeon_connector_analog_encoder_conflict_solve()
206 if (conflict->encoder_ids[i] == 0) in radeon_connector_analog_encoder_conflict_solve()
210 if (conflict->encoder_ids[i] == encoder->base.id) { in radeon_connector_analog_encoder_conflict_solve()
211 if (conflict->status != connector_status_connected) in radeon_connector_analog_encoder_conflict_solve()
218 DRM_DEBUG_KMS("1: conflicting encoders switching off %s\n", drm_get_connector_name(conflict)); in radeon_connector_analog_encoder_conflict_solve()
220 conflict->status = connector_status_disconnected; in radeon_connector_analog_encoder_conflict_solve()
221 radeon_connector_update_scratch_regs(conflict, connector_status_disconnected); in radeon_connector_analog_encoder_conflict_solve()
[all …]
/linux-3.4.99/Documentation/networking/
Dcs89x0.txt495 mode and that the range of memory addresses assigned does not conflict
522 Failure of a test item indicates a possible system resource conflict with
581 An IO conflict occurs when two or more adapter use the same ISA resource (IO
582 address, memory address or IRQ). You can usually detect an IO conflict in one
594 memory address conflict.
596 If an IO conflict occurs, run the CS8900/20 Setup Utility and perform a
597 diagnostic self-test. Normally, the ISA resource in conflict will fail the
599 resource in conflict. Run the diagnostics again to check for further IO
D3c509.txt144 increasing you likely have a physical conflict with two devices trying to
145 use the same ISA IRQ line. The common conflict is with a sound card on IRQ10
DREADME.sb100070 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
Dltpc.txt69 board. Set the switches so as not to conflict with other hardware.
/linux-3.4.99/arch/um/
DKconfig.net48 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-3.4.99/Documentation/filesystems/
Dcifs.txt11 modules can coexist and do not conflict. The CIFS VFS filesystem
Dbefs.txt42 the kernel. Because of this naming conflict, on Linux the BeOS
/linux-3.4.99/Documentation/
Dinit.txt22 C) Possibly a conflict in console= setup --> initial console unavailable.
Dvgaarbiter.txt16 (e.g. two server in parallel). Their address assignments conflict. Moreover,
128 might conflict and disable their IOs and/or Memory access, including VGA
/linux-3.4.99/Documentation/serial/
Dmoxa-smartio123 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
/linux-3.4.99/Documentation/fb/
Dintelfb.txt46 for the least amount). Note, an arbitrary setting may conflict
/linux-3.4.99/Documentation/devicetree/bindings/powerpc/fsl/
Dssi.txt72 drivers (fsldma) will attempt to use them, and it will conflict with the
/linux-3.4.99/arch/powerpc/boot/dts/
Dvirtex440-ml507.dts132 xlnx,ppc440mc-bank-conflict-mask = <0xc00000>;
140 xlnx,ppc440mc-row-conflict-mask = <0x3ffe00>;
/linux-3.4.99/Documentation/trace/
Dtracepoints.txt88 tracepoint name over all the kernel to make sure no type conflict will
/linux-3.4.99/Documentation/sound/oss/
DIntroduction295 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.

123