Home
last modified time | relevance | path

Searched refs:devres (Results 1 – 11 of 11) sorted by relevance

/linux-3.4.99/drivers/base/
Ddevres.c25 struct devres { struct
84 static __always_inline struct devres * alloc_dr(dr_release_t release, in alloc_dr()
87 size_t tot_size = sizeof(struct devres) + size; in alloc_dr()
88 struct devres *dr; in alloc_dr()
111 struct devres *dr; in __devres_alloc()
136 struct devres *dr; in devres_alloc()
155 struct devres *dr = container_of(res, struct devres, data); in devres_free()
174 struct devres *dr = container_of(res, struct devres, data); in devres_add()
183 static struct devres *find_dr(struct device *dev, dr_release_t release, in find_dr()
189 struct devres *dr = container_of(node, struct devres, node); in find_dr()
[all …]
DMakefile5 cpu.o firmware.o init.o map.o devres.o \
DKconfig163 This option enables kernel parameter devres.log. If set to
164 non-zero, devres debug messages are printed. Select this if
165 you are having a problem with devres or want to debug
166 resource management for a managed device. devres.log can be
/linux-3.4.99/Documentation/driver-model/
Ddevres.txt11 3. Devres Group : Group devres'es and release them together
20 devres came up while trying to convert libata to use iomap. Each
48 devres is basically linked list of arbitrarily sized memory areas
49 associated with a struct device. Each devres entry is associated with
50 a release function. A devres can be released in several ways. No
51 matter what, all devres entries are released on driver detach. On
53 devres entry is freed.
56 drivers using devres. For example, coherent DMA memory is acquired
131 devres. Complexity is shifted from less maintained low level drivers
139 Devres entries can be grouped using devres group. When a group is
[all …]
/linux-3.4.99/kernel/irq/
DMakefile2 obj-y := irqdesc.o handle.o manage.o spurious.o resend.o chip.o dummychip.o devres.o
/linux-3.4.99/arch/powerpc/lib/
DMakefile15 obj-$(CONFIG_HAS_IOMEM) += devres.o
/linux-3.4.99/scripts/coccinelle/free/
Ddevm_free.cocci5 /// See Documentation/driver-model/devres.txt for more information.
/linux-3.4.99/drivers/pci/
Dquirks.c388 u32 devres; in piix4_io_quirk() local
391 pci_read_config_dword(dev, port, &devres); in piix4_io_quirk()
392 if ((devres & enable) != enable) in piix4_io_quirk()
394 mask = (devres >> 16) & 15; in piix4_io_quirk()
395 base = devres & 0xffff; in piix4_io_quirk()
414 u32 devres; in piix4_mem_quirk() local
417 pci_read_config_dword(dev, port, &devres); in piix4_mem_quirk()
418 if ((devres & enable) != enable) in piix4_mem_quirk()
420 base = devres & 0xffff0000; in piix4_mem_quirk()
421 mask = (devres & 0x3f) << 16; in piix4_mem_quirk()
/linux-3.4.99/drivers/gpio/
DMakefile5 obj-$(CONFIG_GPIOLIB) += gpiolib.o devres.o
/linux-3.4.99/lib/
DMakefile37 obj-$(CONFIG_HAS_IOMEM) += iomap_copy.o devres.o
/linux-3.4.99/Documentation/
Dremoteproc.txt37 handle. There are several ways to achieve that cleanly (devres, pdata,