Searched refs:wants (Results 1 – 25 of 119) sorted by relevance
12345
| /linux-3.4.99/drivers/gpu/vga/ |
| D | vgaarb.c | 165 unsigned int wants, legacy_wants, match; in __vga_tryget() local
184 wants = rsrc & ~vgadev->owns; in __vga_tryget()
187 if (wants == 0) in __vga_tryget()
193 legacy_wants = wants & VGA_RSRC_LEGACY_MASK; in __vga_tryget()
278 if (wants & (VGA_RSRC_LEGACY_MEM|VGA_RSRC_NORMAL_MEM)) in __vga_tryget()
280 if (wants & (VGA_RSRC_LEGACY_IO|VGA_RSRC_NORMAL_IO)) in __vga_tryget()
283 if (!!(wants & VGA_RSRC_LEGACY_MASK)) in __vga_tryget()
291 vgadev->owns |= (wants & vgadev->decodes); in __vga_tryget()
|
| /linux-3.4.99/drivers/rpmsg/ |
| D | Kconfig | 3 # RPMSG always gets selected by whoever wants it
|
| /linux-3.4.99/Documentation/arm/Samsung-S3C24XX/ |
| D | CPUfreq.txt | 27 and anything else associated with it. Any board that wants to use this
60 Each board that wants to use the cpufreq code must register some basic
|
| /linux-3.4.99/drivers/hwspinlock/ |
| D | Kconfig | 5 # HWSPINLOCK always gets selected by whoever wants it.
|
| /linux-3.4.99/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /linux-3.4.99/Documentation/acpi/ |
| D | method-tracing.txt | 4 The AML method name that the user wants to trace
|
| /linux-3.4.99/drivers/remoteproc/ |
| D | Kconfig | 3 # REMOTEPROC gets selected by whoever wants it
|
| /linux-3.4.99/arch/x86/boot/ |
| D | pmjump.S | 59 # a valid stack if some debugging hack wants to use it.
|
| /linux-3.4.99/Documentation/ |
| D | rpmsg.txt | 65 The caller should specify the channel, the data it wants to send,
81 The caller should specify the channel, the data it wants to send,
99 The caller should specify the channel, the data it wants to send,
115 The caller should specify the channel, the data it wants to send,
128 The user should specify the channel, the data it wants to send,
143 The user should specify the channel, the data it wants to send,
|
| /linux-3.4.99/drivers/virtio/ |
| D | Kconfig | 1 # Virtio always gets selected by whoever wants it.
|
| /linux-3.4.99/Documentation/x86/x86_64/ |
| D | cpu-hotplug-spec | 4 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
|
| /linux-3.4.99/Documentation/fb/ |
| D | cmap_xfbdev.txt | 50 that the app wants to match to. The above code is doing what looks like a least
|
| /linux-3.4.99/Documentation/usb/ |
| D | wusb-cbaf | 45 (connection key). Device saves them for the next time it wants to
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-platform-kim | 40 When one of the protocols Bluetooth, FM or GPS wants to make
|
| /linux-3.4.99/Documentation/blockdev/ |
| D | nbd.txt | 5 the client computer wants to read, e.g., /dev/nb0, it sends a
|
| /linux-3.4.99/Documentation/sound/oss/ |
| D | VIBRA16 | 18 So, the big problem still remains, because the sb module wants a
|
| /linux-3.4.99/Documentation/i2c/ |
| D | i2c-stub | 51 If you spam it hard enough, printk can be lossy. This module really wants
|
| /linux-3.4.99/Documentation/vm/ |
| D | highmem.txt | 29 the pieces of physical memory that it wants to access.
92 wants to access the contents of a page that might be allocated from high memory
|
| /linux-3.4.99/lib/raid6/ |
| D | int.uc | 45 * IA-64 wants insane amounts of unrolling. On other architectures that
|
| /linux-3.4.99/Documentation/filesystems/caching/ |
| D | operations.txt | 79 may decide it wants to handle an operation itself without deferring it to
171 (3) If the submitting thread wants to do the work itself, and has marked the
|
| D | object.txt | 260 The object transits to this state if the cache decides it wants to
306 This is signalled when the cache backend wants to withdraw an object.
313 which one it wants to honour, and that effects the other.
|
| /linux-3.4.99/Documentation/power/ |
| D | charger-manager.txt | 7 wants to look at the aggregated information of the multiple chargers.
84 function to know whether Charger Manager wants to suspend again or not.
|
| /linux-3.4.99/arch/arm/vfp/ |
| D | vfphw.S | 91 @ thread wants ownership of the VFP hardware, save the old
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | dnotify.txt | 12 The application decides which "events" it wants to be notified about.
|
| /linux-3.4.99/Documentation/filesystems/configfs/ |
| D | configfs.txt | 156 Usually a subsystem wants the item to display and/or store attributes,
198 When a config_item wants an attribute to appear as a file in the item's
253 If the subsystem wants the child to be a group itself, the subsystem
341 protect modifications. Whenever a subsystem wants to navigate the
370 reject a link if it only wants links to a certain type of object (say,
|
12345