Lines Matching +full:power +full:- +full:managed

2 Devres - Managed Device Resource
16    6. List of managed interfaces: Currently implemented managed interfaces
20 --------
29 sufficient bugs in ->remove and ->probe failure path.  Well, yes,
42 and having half broken failure path implementation in ->probe() which
48 ---------
57 Managed interface is created for resources commonly used by device
59 using dma_alloc_coherent().  The managed version is called
61 for the DMA memory allocated using it is managed and will be
75 	dma_free_coherent(dev, this->size, this->vaddr, this->dma_handle);
91 	dr->vaddr = vaddr;
100 freed whether initialization fails half-way or the device gets
101 detached.  If most resources are acquired using managed interface, a
111 		return -ENOMEM;
113 	d->ring = dmam_alloc_coherent(...);
114 	if (!d->ring)
115 		return -ENOMEM;
118 		return -EINVAL;
138 managed devm_* versions it is up to you to check if internal operations
139 like allocating memory, have failed. Managed resources pertains to the
140 freeing of these resources *only* - all other checks needed are still
142 necessary before moving to the managed devm_* calls.
146 ---------------
154 	return -ENOMEM;
190 		return -ENOMEM;
205 ----------
208 when it is released or destroyed (removed and freed) - no reference
212 has support for single-instance devres types (atomic
213 lookup-and-add-if-not-found).  Other than that, synchronizing
215 responsibility.  This is usually non-issue because bus ops and
218 For an example of single-instance devres type, read pcim_iomap_table()
226 -----------
242 6. List of managed interfaces
243 -----------------------------
385 PER-CPU MEM
390   devm_pci_alloc_host_bridge()  : managed PCI host bridge allocation
394   pcim_enable_device()		: after success, some PCI ops become managed
402   pcim_set_mwi()		: enable Memory-Write-Invalidate PCI transaction
418 POWER