Lines Matching refs:device
13 PCI device drivers.
33 a new device, the driver with a matching "description" will be notified.
42 Once the driver knows about a PCI device and takes ownership, the
45 Enable the device
49 Access device configuration space (if needed)
54 When done using the device, and perhaps the module needs to be unloaded,
56 Disable the device from generating IRQs
62 Disable the device
77 PCI device drivers call pci_register_driver() during their
83 id_table Pointer to table of device ID's the driver is
89 devices or later if a new device gets inserted) for
92 passed a "struct pci_dev *" for each device whose
93 entry in the ID table matches the device. The probe
95 take "ownership" of the device or an error code
100 remove The remove() function gets called whenever a device
107 suspend Put device into low power state.
108 suspend_late Put device into low power state.
110 resume_early Wake device from low power state.
111 resume Wake device from low power state.
119 the power state of a device before reboot.
129 vendor,device Vendor and device ID to match (or PCI_ANY_ID)
131 subvendor, Subsystem vendor and device ID to match (or PCI_ANY_ID)
138 as vendor/device is normally sufficient.
146 into a static list of equivalent device types,
153 New PCI IDs may be added to a device driver pci_ids table at runtime
156 echo "vendor device subvendor subdevice class class_mask driver_data" > \
160 The vendor and device fields are mandatory, the others are optional. Users
224 is because one PCI device implements several different HW services.
229 Searching by vendor and device ID:
239 Searching by both vendor/device and subsystem vendor/device ID:
244 VENDOR_ID or DEVICE_ID. This allows searching for any device from a
257 for device initialization:
259 Enable the device
263 Access device configuration space (if needed)
274 3.1 Enable the PCI device
276 Before touching any device registers, the driver needs to enable
277 the PCI device by calling pci_enable_device(). This will:
278 o wake up the device if it was in suspended state,
279 o allocate I/O and memory regions of the device (if BIOS did not),
287 Currently, the device drivers can't detect the bug when when two
300 If the PCI device can use the PCI Memory-Write-Invalidate transaction,
313 from the PCI device config space. Use the values in the pci_dev structure
317 See Documentation/IO-mapping.txt for how to access device registers
318 or device memory.
320 The device driver needs to call pci_request_region() to verify
321 no other device is already using the same address resource.
342 drivers need to indicate DMA capabilities of the device and is not
355 Similarly, drivers must also "register" this capability if the device
369 before enabling DMA on the device.
372 3.5 Initialize device registers
382 this is often just another intermediate step to initialize a device.
383 This step can often be deferred until the device is opened for use.
389 request_irq() will associate an interrupt handler and device handle
391 IRQ lines which run from the PCI device to the Interrupt controller.
394 request_irq() also enables the interrupt. Make sure the device is
406 the PCI support to program CPU vector data into the PCI device
409 If your PCI device supports both, try to enable MSI-X first.
420 its device caused the interrupt.
433 4. PCI device shutdown
436 When a PCI device driver is being unloaded, most of the following
439 Disable the device from generating IRQs
444 Disable device from responding to MMIO/IO Port addresses
448 4.1 Stop IRQs on the device
450 How to do this is chip/device specific. If it's not done, it opens
452 the IRQ is shared with another device.
456 "unhooked" device asserts IRQ line, the system will respond assuming
470 Once the device is quiesced (no more IRQs), one can call free_irq().
502 Most low level PCI device drivers support some other subsystem
513 Do not access device registers after calling pci_disable_device().
527 space of a device represented by struct pci_dev *. All these functions return 0
533 pci_bus_(read|write)_config_(byte|word|dword) to access a given device
551 pci_find_capability() Find specified capability in device's capability
566 When displaying PCI device names to the user (for example when a driver wants
581 8. Vendor and device identifications
584 One is not not required to add new device ids to include/linux/pci_ids.h.
585 Please add PCI_VENDOR_ID_xxx for vendors and a hex constant for device ids.
587 PCI_VENDOR_ID_xxx constants are re-used. The device ids are arbitrary
591 Please DO submit new vendor/device ids to pciids.sourceforge.net project.
608 The alternative is the traditional PCI device driver that walks PCI
609 device lists. This is still possible but discouraged.
620 device before the CPU can continue. Writes to MMIO space allow the CPU
621 to continue before the transaction reaches the PCI device. HW weenies
643 interferes with the correct operation of the device.
645 Another case to watch out for is when resetting a PCI device. Use PCI
647 handle the PCI master abort on all platforms if the PCI device is