| /linux-2.6.39/Documentation/power/regulator/ |
| D | consumer.txt | 11 A consumer driver can get access to its supply regulator by calling :-
37 A consumer can enable its power supply by calling:-
45 A consumer can determine if a regulator is enabled by calling :-
52 A consumer can disable its supply when no longer needed by calling :-
75 Consumers can control their supply voltage by calling :-
87 The regulators configured voltage output can be found by calling :-
105 Consumers can control their supply current limit by calling :-
117 A regulators current limit can be found by calling :-
138 by calling :-
157 calling :-
[all …]
|
| D | regulator.txt | 11 Drivers can register a regulator by calling :-
20 Regulators can be unregistered by calling :-
28 drivers by calling :-
|
| /linux-2.6.39/arch/arm/kernel/ |
| D | entry-header.S | 92 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
101 ldmdb sp, {r1 - lr}^ @ get calling r1 - lr
103 ldmdb sp, {r0 - lr}^ @ get calling r0 - lr
139 load_user_sp_lr r2, r3, \offset + S_SP @ calling sp, lr
140 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
145 ldmdb sp, {r1 - r12} @ get calling r1 - r12
147 ldmdb sp, {r0 - r12} @ get calling r0 - r12
|
| D | entry-common.S | 333 ldmia sp, {r0 - lr}^ @ Get calling r0 - lr
348 THUMB( store_user_sp_lr r8, r10, S_SP ) @ calling sp, lr
350 str lr, [sp, #S_PC] @ Save calling PC
|
| /linux-2.6.39/Documentation/ |
| D | media-framework.txt | 48 Drivers register media device instances by calling
87 Drivers unregister media device instances by calling
104 Drivers initialize entities by calling
110 initialized before or after calling media_entity_init. Entities embedded in
118 Drivers must set the direction of every pad in the pads array before calling
127 Drivers register entities with a media device by calling
138 Drivers unregister entities by calling
148 Drivers free resources associated with an entity by calling
201 Drivers create links by calling
245 Drivers initiate a graph traversal by calling
[all …]
|
| D | keys-request-key.txt | 9 The process starts by either the kernel requesting a service by calling
185 (a) If extant, the calling process's thread keyring is searched.
187 (b) If extant, the calling process's process keyring is searched.
189 (c) The calling process's session keyring is searched.
|
| /linux-2.6.39/Documentation/pcmcia/ |
| D | driver-changes.txt | 31 are reserved, after calling pcmcia_request_configuration(), they may
45 - calling request_irq/free_irq directly. Use the IRQ from *p_dev->irq.
66 By calling pcmcia_loop_config(), a driver can iterate over all available
72 Instead of calling pcmcia_release_{configuration,io,irq,win}, all that's
73 necessary now is calling pcmcia_disable_device. As there is no valid
|
| /linux-2.6.39/Documentation/isdn/ |
| D | README.avmb1 | 55 and add the card by calling
57 and load the firmware by calling
61 and add the card by calling
63 and load the firmware by calling
|
| D | INTERFACE.CAPI | 26 CAPI drivers optionally register themselves with Kernel CAPI by calling the
30 registration can be revoked by calling the function unregister_capi_driver()
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
38 driver. The registration can be revoked by calling the function
43 structure of the device, and signal its readiness by calling capi_ctr_ready().
55 operation CAPI_REGISTER) to an appropriate hardware driver by calling its
79 the following non-private fields, all to be set by the driver before calling
99 - to be set by the driver before calling attach_capi_ctr():
165 - to be filled in before calling capi_ctr_ready():
|
| D | README.diversion | 34 Tracing calling and diversion information
36 4. Tracing calling and diversion information
92 Tracing calling and diversion information
110 4. Tracing calling and diversion information
|
| D | README.audio | 88 with ATA, depending on the calling service, the emulator
123 <DLE>c FAX calling tone received.
|
| /linux-2.6.39/arch/frv/kernel/ |
| D | kernel_execve.S | 17 # Do a system call from kernel instead of calling sys_execve so we end up with
|
| /linux-2.6.39/arch/mn10300/kernel/ |
| D | kernel_execve.S | 16 # Do a system call from kernel instead of calling sys_execve so we end up with
|
| /linux-2.6.39/Documentation/s390/ |
| D | kvm.txt | 21 * KVM_CREATE_VM may fail on s390, if the calling process has multiple
30 calling process to be single-threaded. Note that the first call to KVM_CREATE_VM
34 observe an error calling KVM_CREATE_VM. Switching on PGSTE is a one-time
36 the calling process. It does not have any user-visible effect other than a small
|
| /linux-2.6.39/net/x25/ |
| D | af_x25.c | 124 char *called, *calling; in x25_addr_ntoa() local
131 calling = calling_addr->x25_addr; in x25_addr_ntoa()
144 *calling++ = ((*p >> 0) & 0x0F) + '0'; in x25_addr_ntoa()
147 *calling++ = ((*p >> 4) & 0x0F) + '0'; in x25_addr_ntoa()
152 *called = *calling = '\0'; in x25_addr_ntoa()
161 char *called, *calling; in x25_addr_aton() local
165 calling = calling_addr->x25_addr; in x25_addr_aton()
168 calling_len = strlen(calling); in x25_addr_aton()
183 *p |= (*calling++ - '0') << 0; in x25_addr_aton()
187 *p |= (*calling++ - '0') << 4; in x25_addr_aton()
|
| /linux-2.6.39/Documentation/sound/alsa/soc/ |
| D | jack.txt | 35 Jacks are created by the machine driver calling snd_soc_jack_new().
52 input to the system and update a jack by calling snd_soc_jack_report(),
|
| /linux-2.6.39/arch/unicore32/kernel/ |
| D | entry.S | 71 ldw r1, [sp+], #\offset + S_PSR @ get calling asr
76 ldm.w (r1 - r15), [sp]+ @ get calling r1 - r15
77 ldur (r16 - lr), [sp]+ @ get calling r16 - lr
79 ldm.w (r0 - r15), [sp]+ @ get calling r0 - r15
80 ldur (r16 - lr), [sp]+ @ get calling r16 - lr
602 stw lr, [sp+], #S_PC @ Save calling PC
|
| /linux-2.6.39/Documentation/filesystems/caching/ |
| D | backend-api.txt | 20 The cache definition (struct fscache_cache) should be initialised by calling:
65 A cache can be withdrawn from the system by calling this function with a
87 The calling process's fsuid, fsgid and SELinux security identities may need to
150 initialised by calling fscache_object_init(object).
188 calling fscache_get_retrieval() and refs may be discarded by calling
308 obtained by calling object->cookie->def->get_aux()/get_attr().
353 cache can read these from the netfs by calling the cookie's get_attr()
394 as it can before calling, but most of the work belongs to the backend.
|
| D | operations.txt | 53 struct embedded in it. They should initialise it by calling:
82 This is, for example, used in read operations for calling readpages() on
187 and calling:
|
| /linux-2.6.39/Documentation/PCI/ |
| D | pci.txt | 249 decrement the reference count on these devices by calling pci_dev_put().
277 the PCI device by calling pci_enable_device(). This will:
286 pci_request_resources() before calling pci_enable_device().
323 calling pci_disable_device().
327 determine MMIO and IO Port resource availability _after_ calling
348 to "register" this capability by calling pci_set_dma_mask() with
357 address by calling pci_set_consistent_dma_mask().
381 While calling request_irq() is the last step described here,
404 MSI capability can be enabled by calling pci_enable_msi() or
405 pci_enable_msix() before calling request_irq(). This causes
[all …]
|
| /linux-2.6.39/Documentation/parisc/ |
| D | registers | 87 course, you need to save them if you care about them, before calling
100 that should not cause a problem for the calling routine.
|
| /linux-2.6.39/drivers/spi/ |
| D | spi_s3c24xx_fiq.S | 26 @ setup the calling registers.
|
| /linux-2.6.39/arch/alpha/lib/ |
| D | callback_srm.S | 29 extwl $25,2,$25 # argument information (VMS calling std)
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | porting | 38 typically between calling iget_locked() and unlocking the inode.
179 calling unlock_new_inode().
335 .d_compare() calling convention and locking rules are significantly
342 .d_hash() calling convention and locking rules are significantly
407 a matter of switching from calling get_sb_... to mount_... and changing the
|
| /linux-2.6.39/Documentation/arm/nwfpe/ |
| D | NOTES | 6 will point it out. The ARM calling conventions require floating point
|