| /linux-4.4.14/Documentation/power/regulator/ |
| D | regulator.txt | 11 Drivers can register a regulator by calling :-
19 Regulators can be unregistered by calling :-
27 consumer drivers by calling :-
|
| 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 :-
158 calling :-
[all …]
|
| /linux-4.4.14/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 | DMA-attributes.txt | 61 by calling dma_mmap_attrs(). By using this API, you are guaranteeing
78 performed by calling dma_map_{single,page,sg} function more than once
|
| D | zorro.txt | 26 Zorro devices are found by calling `zorro_find_device()', which returns a
|
| D | dcdbas.txt | 39 3) Write "1" to smi_request to generate a calling interface SMI or
|
| D | adding-syscalls.txt | 88 - To cope with a later userspace program calling an older kernel, the kernel
91 - To cope with an older userspace program calling a newer kernel, the kernel
110 window between xyzzy() and calling fcntl(fd, F_SETFD, FD_CLOEXEC), where an
154 If your new xyzzy(2) system call manipulates a process other than the calling
156 only a calling process with the same permissions as the target process, or
|
| D | IRQ-domain.txt | 41 calling one of the irq_domain_add_*() functions (each mapping method
48 by calling irq_create_mapping() which accepts the irq_domain and a
|
| D | pwm.txt | 114 pwm_config(), so the calling context is currently driver specific. This
|
| D | futex-requeue-pi.txt | 117 nr_wake+nr_requeue tasks to the PI futex, calling
|
| D | men-chameleon-bus.txt | 94 is already requested from the kernel by calling request_mem_region().
|
| D | pi-futex.txt | 4 We are calling them lightweight for 3 reasons:
|
| D | kprobes.txt | 84 type) as the function being probed, and must always end by calling
124 stored in an object of type kretprobe_instance. Before calling
345 so, its handlers aren't hit until calling enable_kprobe(kp).
548 each other -- e.g., probing printk() and then calling printk() from a
|
| D | initrd.txt | 217 must exist before calling pivot_root. Example:
238 - before calling pivot_root, the current directory of the invoking
|
| D | vgaarbiter.txt | 42 explicitly tell it by calling vga_set_legacy_decoding().
|
| D | kref.txt | 298 by using kfree_rcu(entry, rhead) as done above, or by calling synchronize_rcu()
|
| D | kobject.txt | 122 must have an associated kobj_type. After calling kobject_init(), to
129 kobj->kset must be assigned before calling kobject_add(). If a kset is
|
| D | hwspinlock.txt | 47 be calling this function in order to reserve specific hwspinlock
|
| D | rbtree.txt | 179 node by calling rb_next() or rb_prev() on the current node. This will return
|
| D | remoteproc.txt | 134 last refcount should be decremented by calling rproc_put().
|
| D | vme_api.txt | 258 destination attributes need to be created before calling this function, this is
|
| D | svga.txt | 118 0x0900 to 0x09ff - Video7 special modes. Set by calling INT 0x10, AX=0x6f05.
|
| D | memory-hotplug.txt | 391 A callback routine can be registered by calling
|
| D | xillybus.txt | 177 the attached memory is done by seeking to the desired address, and calling
|
| D | dma-buf-sharing.txt | 380 up a mapping in userspace, calling do_mmap with dma_buf->file will equally
|
| D | atomic_ops.txt | 66 which simply reads the counter value currently visible to the calling thread.
|
| /linux-4.4.14/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-4.4.14/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.
|
| D | INTERFACE | 10 An HL-driver can register itself at LL by calling the function
47 supported prior to calling register_isdn(). Upon return of the call,
82 packets by calling this function. Upon calling, the HL-driver must
212 All commands will be performed by calling the function command() described
480 All status-changes are signaled via calling the previously described
|
| D | README.concap | 114 cprot may no longer be referenced after calling this */
|
| D | README | 268 octet 3 of calling party number IE (Numbering plan)
272 octet 3a of calling party number IE (Screening info)
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | entry-header.S | 323 load_user_sp_lr r2, r3, \offset + S_SP @ calling sp, lr
324 ldr r1, [sp, #\offset + S_PSR] @ get calling cpsr
333 ldmdb sp, {r1 - r12} @ get calling r1 - r12
335 ldmdb sp, {r0 - r12} @ get calling r0 - r12
|
| D | entry-common.S | 153 THUMB( store_user_sp_lr r8, r10, S_SP ) @ calling sp, lr
155 str lr, [sp, #S_PC] @ Save calling PC
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 65 /dev/watchdog miscdev. The id is set automatically when calling
70 * parent: set this to the parent device (or NULL) before calling
120 3) Call kref_init on this kref *before* calling watchdog_register_device()
121 4) Define a ref operation calling kref_get on this kref
122 5) Define a unref operation calling kref_put on this kref
125 * *After* calling watchdog_unregister_device() call kref_put on the kref
191 after calling watchdog_unregister_device, and then checked before calling
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | dax.txt | 60 - implementing the direct_IO address space operation, and calling
67 - calling dax_truncate_page() instead of block_truncate_page() for DAX files
68 - calling dax_zero_page_range() instead of zero_user() for DAX files
|
| D | porting | 38 typically between calling iget_locked() and unlocking the inode.
178 calling unlock_new_inode().
332 .d_compare() calling convention and locking rules are significantly
339 .d_hash() calling convention and locking rules are significantly
399 a matter of switching from calling get_sb_... to mount_... and changing the
492 calling conventions for ->follow_link() have changed. Instead of returning
499 calling conventions for ->put_link() have changed. It gets inode instead of
|
| D | fiemap.txt | 179 defining its set of supported fiemap flags, and calling a helper function on
224 automatically be set from specific flags on behalf of the calling file
|
| D | Locking | 155 doesn't hold it when calling ->statfs() - superblock is pinned down
265 currently, and VM should stop calling ->writepage() on this page for some
516 FS recursion means calling ->quota_read() and ->quota_write() from superblock
|
| D | vfs.txt | 81 file structure, and then calling the required file structure method to
621 calling ->writepage on that page.
716 be done by calling the ->releasepage function, but in this case the
734 calling invalidate_inode_pages2().
912 in the filesystem eventually ends up calling the device driver open()
998 It is a tricky calling convention because it needs to be called under
1050 calling process continue. -EISDIR can be returned to tell pathwalk to
|
| D | tmpfs.txt | 100 if any, modified by the calling task's cpuset constraints
|
| D | coda.txt | 245 the calling process and passes the information on to Venus. When
290 queue. The routine calling upcall is responsible for allocating the
299 the calling thread in P is blocked in upcall. A pointer in the
424 they are set for the calling process. The vuid_t and guid_t are 32 bit
1008 VFid in its cache and to note that the calling process wishes to open
1411 that the calling process received a signal after Venus read the
|
| D | relay.txt | 400 by calling the subbuf_start_reserve() helper function from within the
429 callback by calling the relay_buf_full() helper function.
|
| D | spufs.txt | 325 signal delivered to the calling process.
|
| /linux-4.4.14/net/x25/ |
| D | af_x25.c | 126 char *called, *calling; in x25_addr_ntoa() local
133 calling = calling_addr->x25_addr; in x25_addr_ntoa()
146 *calling++ = ((*p >> 0) & 0x0F) + '0'; in x25_addr_ntoa()
149 *calling++ = ((*p >> 4) & 0x0F) + '0'; in x25_addr_ntoa()
154 *called = *calling = '\0'; in x25_addr_ntoa()
163 char *called, *calling; in x25_addr_aton() local
167 calling = calling_addr->x25_addr; in x25_addr_aton()
170 calling_len = strlen(calling); in x25_addr_aton()
185 *p |= (*calling++ - '0') << 0; in x25_addr_aton()
189 *p |= (*calling++ - '0') << 4; in x25_addr_aton()
|
| /linux-4.4.14/security/tomoyo/ |
| D | Kconfig | 42 bool "Activate without calling userspace policy loader."
68 string "Trigger for calling userspace policy loader"
|
| /linux-4.4.14/Documentation/security/ |
| 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.
|
| D | keys.txt | 435 (*) Search the process's keyrings for a key, potentially calling out to
519 group ID to something other than the calling process's group ID or one of
567 This function clears the list of keys attached to a keyring. The calling
790 (*) Install the calling process's session keyring on its parent.
794 This functions attempts to install the calling process's session keyring
795 on to the calling process's parent, replacing the parent's current session
798 The calling process must have the same ownership as its parent, the
799 keyring must have the same ownership as the calling process, the calling
863 calling processes has a searchable link to the key from one of its
917 (*) A key can be requested asynchronously by calling one of:
[all …]
|
| D | Yama.txt | 64 with PTRACE_ATTACH, or through children calling PTRACE_TRACEME.
|
| D | credentials.txt | 316 Once a set of credentials has been made public (by calling commit_creds() for
462 new set of credentials by calling:
481 by calling:
574 the VFS, and that can be done by calling into such as vfs_mkdir() with a
|
| /linux-4.4.14/drivers/net/wireless/cw1200/ |
| D | Kconfig | 19 the default platform data by calling cw1200_sdio_set_platform_data()
|
| /linux-4.4.14/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-4.4.14/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
599 stw lr, [sp+], #S_PC @ Save calling PC
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci.txt | 231 decrement the reference count on these devices by calling pci_dev_put().
259 the PCI device by calling pci_enable_device(). This will:
268 pci_request_resources() before calling pci_enable_device().
305 calling pci_disable_device().
309 determine MMIO and IO Port resource availability _after_ calling
330 to "register" this capability by calling pci_set_dma_mask() with
339 address by calling pci_set_consistent_dma_mask().
363 While calling request_irq() is the last step described here,
386 MSI capability can be enabled by calling pci_enable_msi() or
387 pci_enable_msix() before calling request_irq(). This causes
[all …]
|
| D | MSI-HOWTO.txt | 207 Before calling this function, a device driver must always call free_irq()
443 Before calling this function, a device driver must always call free_irq()
477 it back to pin-interrupt mode, before calling pci_enable_msi_range()
|
| D | PCIEBUS-HOWTO.txt | 88 header file /include/linux/pcieport_if.h, before calling these APIs.
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 12 - ibm,opal-id: Refers to a specific bus and used to identify it when calling
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| 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:
|
| 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
317 obtained by calling object->cookie->def->get_aux()/get_attr().
374 cache can read these from the netfs by calling the cookie's get_attr()
415 as it can before calling, but most of the work belongs to the backend.
|
| D | object.txt | 122 Then when an event is raised (by calling fscache_raise_event()), if the event
123 is not masked, the object will be queued for processing (by calling
|
| D | netfs-api.txt | 342 filling in the index entry by calling the operations pointed to by def.
357 calling fscache_enable_cookie() (see below).
638 done by calling:
763 calling fscache_uncache_all_inode_pages() afterwards to make sure all page
|
| D | cachefiles.txt | 414 bypassing security and calling inode ops directly. Therefore the VFS and LSM
|
| /linux-4.4.14/Documentation/arm/ |
| D | 00-INDEX | 34 - Secure firmware registration and calling.
|
| D | firmware.txt | 1 Interface for registering and calling firmware-specific operations for ARM.
|
| D | kernel_user_helpers.txt | 145 optimization in the calling code.
239 optimization in the calling code.
|
| D | Booting | 155 There are two options for calling the kernel zImage. If the zImage
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | client.txt | 101 the DMA operation prior to calling dmaengine_prep_slave_sg(), and must
134 locks before calling the callback function which may cause a
156 The transactions in the pending queue can be activated by calling the
|
| D | pxa_dma.txt | 108 - calling all the transfer callbacks of finished transfers, based on
|
| /linux-4.4.14/Documentation/parisc/ |
| D | registers | 95 course, you need to save them if you care about them, before calling
108 that should not cause a problem for the calling routine.
|
| /linux-4.4.14/Documentation/x86/ |
| D | entry_64.txt | 39 have different calling conventions. The syscall and sysenter
40 instructions have their own peculiar calling conventions. Some of
|
| /linux-4.4.14/drivers/spi/ |
| D | spi-s3c24xx-fiq.S | 26 @ setup the calling registers.
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | callback_srm.S | 29 extwl $25,2,$25 # argument information (VMS calling std)
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | v4l2-controls.txt | 121 You add non-menu controls by calling v4l2_ctrl_new_std:
127 Menu and integer menu controls are added by calling v4l2_ctrl_new_std_menu:
133 Menu controls with a driver specific menu are added by calling
141 Integer menu controls with a driver specific menu can be added by calling
276 When a sub-device is registered with a V4L2 driver by calling
327 identical to the default value. After calling v4l2_ctrl_handler_setup() this
410 control, or by calling v4l2_ctrl_new_std_menu().
672 You can do that by calling v4l2_ctrl_find:
740 from a sub-device driver changes. You can set a notify callback by calling
|
| D | v4l2-framework.txt | 105 calling v4l2_device_register then it will be untouched. If dev is NULL, then
106 you *must* setup v4l2_dev->name before calling v4l2_device_register.
194 decrease the refcount manually as well by calling:
298 calling media_entity_init():
403 e.g. AUDIO_CONTROLLER and specify that as the group ID value when calling
454 for all registered sub-devices marked with V4L2_SUBDEV_FL_HAS_DEVNODE by calling
659 queuing ownership (i.e. is the filehandle calling it allowed to do the
684 your v4l2_ioctl_ops should be ignored. You can mark such ioctls by calling this
698 calling media_entity_init():
744 video_device before calling v4l2_device_disconnect. If you are also using
[all …]
|
| D | videobuf | 269 take care of calling get_user_pages() and filling in the scatterlist array.
272 the vidioc_reqbufs() function, *after* calling videobuf_reqbufs(). The
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | NOTES | 6 will point it out. The ARM calling conventions require floating point
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | introduction.txt | 21 refrain from calling the protocol engines directly, instead they should use
|
| /linux-4.4.14/Documentation/arm/OMAP/ |
| D | omap_pm | 96 The PM parameters can be overwritten by calling the function again
97 with the new value. The settings can be removed by calling the
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 42 by calling iio_channel_get(). The correct channel is identified by:
|
| /linux-4.4.14/drivers/cpuidle/ |
| D | Kconfig.arm | 11 initialized by calling the CPU operations init idle hook
|
| /linux-4.4.14/arch/mn10300/include/asm/ |
| D | frame.inc | 63 # peel back the stack to the calling frame
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | ilsp.doc | 58 This will allow calling routines to access the entry points
75 fixed so that a program calling the routines will not have to be
|
| D | fplsp.doc | 59 This will allow calling routines to access the entry points
76 fixed so that a program calling the routines will not have to be
|
| D | isp.doc | 63 This will allow calling routines to access the entry points
104 are listed in section "68060 ISP entry points" below. A calling routine
|
| D | fpsp.doc | 55 This will allow calling routines to access the entry points
96 are listed in section "68060 FPSP entry points" below. A calling routine
|
| D | TEST.DOC | 49 This will allow the calling routines to access the entry points
91 are listed in section "68060{ISP,FPSP}-TEST entry points" below. A calling
|
| /linux-4.4.14/drivers/staging/wilc1000/ |
| D | Kconfig | 22 by calling network device stop.
|
| /linux-4.4.14/Documentation/i2c/ |
| D | instantiating-devices | 18 i2c_board_info which is registered by calling i2c_register_board_info().
100 a struct i2c_board_info and calling i2c_new_device().
153 it on cleanup. This is done by calling i2c_unregister_device() on the
|
| D | functionality | 116 which you driver is calling.
|
| D | writing-clients | 167 structure with the device address and driver name, and calling
230 i2c_new_probed_device() can be unregistered by calling
|
| D | smbus-protocol | 26 Each transaction type corresponds to a functionality flag. Before calling a
|
| /linux-4.4.14/Documentation/networking/ |
| D | netdev-features.txt | 46 is calculated and filtered by calling ndo_fix_features callback
61 A driver that wants to trigger recalculation must do so by calling
|
| D | gen_stats.txt | 53 compatibility by calling the compat wrappers to keep providing the
|
| D | tproxy.txt | 27 option before calling bind:
|
| D | tuntap.txt | 161 calling it with IFF_DETACH_QUEUE flag, the queue were disabled. And when
162 calling it with IFF_ATTACH_QUEUE flag, the queue were enabled. The queue were
|
| D | dccp.txt | 76 can be set before calling bind().
93 must be registered on the socket before calling connect() or listen().
|
| D | timestamping.txt | 276 receives the timestamps by calling recvmsg() with flag MSG_ERRQUEUE
313 The calling application is often not interested in receiving the whole
355 calling ioctl(SIOCSHWTSTAMP) with a pointer to a struct ifreq whose
457 calling skb_hwtstamp_tx() with the original skb, the raw
|
| D | nfc.txt | 90 operation by calling STOP_POLL command. In this case, it will be checked if
|
| D | filter.txt | 616 Therefore, eBPF calling convention is defined as:
624 etc, and eBPF calling convention maps directly to ABIs used by the kernel on
665 place function arguments into R1 to R5 registers to satisfy calling
671 instruction. This calling convention was picked to cover common call
787 them across the calls as defined by calling convention.
1186 Program that uses invalid map_fd=0 while calling to map_lookup_elem() function:
|
| D | stmmac.txt | 178 o init/exit: callbacks used for calling a custom initialization;
256 MAC for fixed_link by calling:
|
| D | netlink_mmap.txt | 46 Conversion of the reception path involves calling poll() on the file
|
| D | altera_tse.txt | 67 transmit descriptor by calling the underlying DMA transmit routine (SGDMA or
|
| D | phy.txt | 86 manually calling functions to update status, and configure the PHY
|
| D | switchdev.txt | 253 entry by calling call_switchdev_notifiers(SWITCHDEV_FDB_ADD, ...). The
|
| D | rxrpc.txt | 400 extracted from the calling process's keyrings with request_key() and
656 aborted by calling sendmsg() with a dataless message with the following
|
| D | ppp_generic.txt | 126 `hdrlen' fields before calling ppp_register_channel() and not change
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | of_unittest.txt | 130 required to attach the root('/') node. All other nodes are attached by calling
183 properties are updated to the live tree's node by calling the function
|
| D | booting-without-of.txt | 159 of the kernel image. That entry point supports two calling
198 of the kernel image. That entry point supports two calling
278 supports one calling convention which is documented in
454 physical CPU ID is calling the kernel entry point. This is used,
457 the device-tree corresponding to the CPU calling the kernel entry
|
| /linux-4.4.14/Documentation/usb/ |
| D | URB.txt | 178 On the other hand, since usb_unlink_urb may end up calling the
184 count by calling
189 decrement the reference count by calling usb_free_urb. Of course,
|
| D | bulk-streams.txt | 51 without calling usb_free_streams(). This is a simplification for the xHCI host
|
| D | hotplug.txt | 23 actively (calling such a user mode helper program directly).
|
| D | power-management.txt | 352 driver does so by calling these six functions:
419 Drivers can enable autosuspend for their devices by calling
426 drivers can disable autosuspend by calling
458 long enough but not yet gotten around to calling the driver's suspend
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-calling.txt | 6 The preferred calling convention is known as the firmware mailbox. The
|
| D | fw-encoder-api.txt | 704 do any harm calling it regardless.
|
| /linux-4.4.14/Documentation/power/ |
| D | notifiers.txt | 9 resume/restore, but they cannot do it by calling request_firmware() from their
|
| D | runtime_pm.txt | 537 calling pm_runtime_set_active() for the device will affect the parent, unless
553 enabled earlier by calling pm_runtime_enable().
570 runtime PM functionality. It does so by calling pm_runtime_get_sync() before
576 calling pm_runtime_suspend() from their ->remove() routines, the driver core
639 The PM core always increments the runtime usage counter before calling the
640 ->suspend() callback and decrements it after calling the ->resume() callback.
778 Subsystems can tell the PM core about these devices by calling
812 typically just before calling pm_runtime_put_autosuspend(). The desired length
814 initially by calling pm_runtime_set_autosuspend_delay(), but after device
|
| D | freezing-of-tasks.txt | 25 All freezable tasks must react to that by calling try_to_freeze(), which
43 calling try_to_freeze(). The main loop of a freezable kernel thread may look
91 PF_NOFREEZE for itself by calling set_freezable() (the resetting of PF_NOFREEZE
|
| D | userland-swsusp.txt | 49 uploaded snapshot image; before calling it you should transfer
141 preferably using mlockall(), before calling SNAPSHOT_FREEZE.
|
| D | pm_qos_interface.txt | 48 and recompute the new aggregated target, calling the notification tree if the
119 and recompute the new aggregated target, calling the notification trees if the
|
| /linux-4.4.14/drivers/isdn/capi/ |
| D | capidrv.c | 1799 u8 calling[ISDN_MSNLEN + 3]; in capidrv_command() local
1835 calling[0] = 0; in capidrv_command()
1840 calling[0] = strlen(bchan->mynum) + 2; in capidrv_command()
1841 calling[1] = 0; in capidrv_command()
1842 calling[2] = 0x80; in capidrv_command()
1843 strncpy(calling + 3, bchan->mynum, ISDN_MSNLEN); in capidrv_command()
1855 calling, /* CallingPartyNumber */ in capidrv_command()
|
| /linux-4.4.14/Documentation/scsi/ |
| D | osd.txt | 68 (OSD LUN). The osd_dev structure is needed for calling osd_start_request().
93 asynchronously by calling the block layer API directly.
|
| D | osst.txt | 35 devices. If those are not present, you may create them by calling
59 the device nodes by calling the Makedevs.sh script (see below) manually.
|
| D | scsi_eh.txt | 44 command by calling scsi_done callback passed from midlayer when
64 the completed request by calling blk_end_request and
179 calling scsi_restart_operations(), which
|
| D | ChangeLog.lpfc | 303 * Lock before calling lpfc_sli_hba_down().
306 * Fix issue where we are calling lpfc_disc_done() recursively from
338 by calling lpfc_disc_done() even if it is called from
343 * Release host lock and enable interrupts when calling
608 * Set nlp_state before calling lpfc_nlp_list() since this will
617 * Grab lock before calling lpfc_sli_issue_mbox(phba, pmb,
809 remove checking of list emptiness before calling lpfc_disc_done,
833 corresponding to the pid of the calling process.
1150 calling list_del on an object that was never put on a list.
1320 * In some of the els completion routines, after calling
|
| D | in2000.txt | 116 reselect. The driver defaults to what I'm calling
|
| D | scsi_mid_low_api.txt | 428 * scan the bus; this can be done by calling scsi_scan_host() or
430 * the transport template before calling this function and may only
484 * get unblocked other than the LLD calling scsi_unblock_requests().
1279 result - should be set by LLD prior to calling 'done'. A value
|
| D | ChangeLog.1992-1997 | 439 - Change all interrupt handlers to accept new calling convention.
1065 calling sequence for request_irq.
1265 request_queueable to use new calling sequence.
1409 disable_irq/enable_irq before calling queuecommand if we
|
| D | libsas.txt | 37 start OOB (at which point your driver will start calling the
|
| D | scsi_fc_transport.txt | 435 FC drivers are required to call fc_remove_host() prior to calling
|
| D | ChangeLog.megaraid_sas | 155 3. Enable MSI-X before calling megasas_init_fw().
|
| /linux-4.4.14/fs/jffs2/ |
| D | README.Locking | 50 before calling a function which may need to allocate space. The
56 before calling the space allocation functions.
|
| /linux-4.4.14/Documentation/input/ |
| D | multi-touch-protocol.txt | 31 Drivers for type A devices separate contact packets by calling
36 Drivers for type B devices separate contact packets by calling
41 All drivers mark the end of a multi-touch transfer by calling the usual
77 use_count to false when calling input_mt_report_pointer_emulation().
|
| D | input-programming.txt | 96 Then the example driver registers the input device structure by calling
197 However EV_ABS requires a little special care. Before calling
|
| /linux-4.4.14/Documentation/vm/ |
| D | numa_memory_policy.txt | 366 always affect only the calling task, the calling task's address space, or
367 some shared object mapped into the calling task's address space.
380 Set's the calling task's "task/process memory policy" to mode
396 Queries the "task/process memory policy" of the calling task, or
410 a VMA policy for the range of the calling task's address space
|
| D | page_migration | 66 calling isolate_lru_page().
|
| D | frontswap.txt | 19 links itself to frontswap by calling frontswap_register_ops to set the
42 cache" by calling frontswap_writethrough(). In this mode, the reduction
|
| D | numa | 147 or cpu_to_mem() function to locate the "local memory node" for the calling or
|
| D | transhuge.txt | 325 calling split_huge_page(page). This is what the Linux VM does before
344 We want as much code as possible hugepage aware, as calling
|
| D | unevictable-lru.txt | 348 back the page - by calling putback_lru_page() - which will notice that the page
406 For munlock(), populate_vma_page_range() unlocks individual pages by calling
|
| D | cleancache.txt | 29 to the kernel's cleancache "frontend" by calling cleancache_register_ops,
|
| /linux-4.4.14/arch/c6x/lib/ |
| D | remu.S | 41 ;; The ABI seems designed to prevent these functions calling each other,
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | psci.txt | 38 - method : The method of calling the PSCI firmware. Permitted
|
| /linux-4.4.14/Documentation/ia64/ |
| D | fsys.txt | 82 routine takes care of entering (full) kernel mode and calling the
116 doing a full system call (by calling fsys_fallback_syscall).
121 must be preserved, in accordance to the normal calling conventions.
|
| /linux-4.4.14/Documentation/metag/ |
| D | kernel-ABI.txt | 139 arguments, even if this is contrary to the normal calling conventions (where the
165 These calling conventions apply to both user and kernel code. The stack grows
|
| /linux-4.4.14/Documentation/crypto/ |
| D | async-tx-api.txt | 88 3/ calling async_tx_ack() on the descriptor.
96 event by calling async_tx_issue_pending_all(). This operates on all
|
| /linux-4.4.14/Documentation/gpio/ |
| D | driver.txt | 97 holding the IRQs disabled. The GPIO irqchip will then end up calling
129 The GPIO irqchip will then end up calling something like this sequence in
268 calling driver.
|
| D | consumer.txt | 129 It is strictly forbidden to use a descriptor after calling these functions.
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 49 A board can do its own setup before calling s3c_pm_init, if it
|
| /linux-4.4.14/Documentation/acpi/ |
| D | gpio-properties.txt | 95 calling acpi_dev_remove_driver_gpios() on the ACPI device object where that
|
| D | enumeration.txt | 204 Then the at25 SPI driver can get this configuration by calling _DSM on its
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | bus.txt | 82 lock is not held when calling the callback.
|
| D | devres.txt | 12 4. Details : Life time rules, calling context, ...
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | completion.txt | 123 Note that wait_for_completion() is calling spin_lock_irq()/spin_unlock_irq(),
222 There only can be one thread calling complete() or complete_all() on a
|
| /linux-4.4.14/Documentation/s390/ |
| D | cds.txt | 54 * Instead of calling read_dev_chars()/read_conf_data(), the driver issues
130 device drivers should use the new calling interface via the ccw_device only.
187 with the associated I/O request when calling ccw_device_start().
342 must not try to obtain it again when calling ccw_device_start() or we end in a
|
| D | CommonIO | 118 Logs the calling of functions in the common I/O-layer and, if applicable,
|
| D | s390dbf.txt | 49 - Cpu-Number of calling task
526 - Cpu-Number of calling task
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | arm-vgic.txt | 115 -ENXIO: VGIC not properly configured as required prior to calling
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | hwmon-kernel-api.txt | 45 the parent device prior to calling hwmon_device_register. A name attribute must
|
| D | pmbus-core | 100 handled more efficiently and thus preferred. Either case, the calling PMBus
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | user_mad.txt | 13 and then calling the IB_USER_MAD_REGISTER_AGENT ioctl on a file
|
| /linux-4.4.14/Documentation/block/ |
| D | data-integrity.txt | 139 calling bio_integrity_alloc(bio). This will allocate and attach the
200 Prior to calling this function, the bio data direction and start
|
| /linux-4.4.14/Documentation/frv/ |
| D | mmu-layout.txt | 117 furthermore, a driver using kmap() may sleep before calling kunmap(), but may not sleep before
118 calling kunmap_atomic() if it had previously called kmap_atomic().
|
| /linux-4.4.14/Documentation/serial/ |
| D | tty.txt | 118 The driver is forbidden from calling this directly
253 code calling its own functions must be careful in this case.
|
| /linux-4.4.14/Documentation/locking/ |
| D | ww-mutex-design.txt | 64 required, since simply calling the normal ww_mutex_lock functions on the
80 semantics as a normal mutex. This is done by calling ww_mutex_lock with a NULL
|
| /linux-4.4.14/Documentation/power/powercap/ |
| D | powercap.txt | 232 to be defined prior to calling powercap_register_zone() to register that zone.
|
| /linux-4.4.14/arch/arc/kernel/ |
| D | entry-compact.S | 250 ; icause1 needs to be read early, before calling tracing, which
|
| /linux-4.4.14/Documentation/RCU/ |
| D | UP.txt | 101 Because the calling function is scanning an RCU-protected linked
|
| D | checklist.txt | 208 by calling rcu_read_lock_sched() and rcu_read_unlock_sched().
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.txt | 125 drivers/pci/hotplug/pSeries_pci.c calling in to the eeh.c code.
183 events (for example, calling "ifup eth0" for ethernet cards).
|
| /linux-4.4.14/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 80 arrives and departs, by calling the function driver's probe() and remove()
316 Linux environment by calling input_report_key() and input_report_abs().
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | Exporting | 78 It returns NULL when the passed-in dentry is used, following the calling
|
| /linux-4.4.14/arch/frv/kernel/ |
| D | head.S | 562 # - GR8 and GR9 should be rounded up/down to the nearest megabyte before calling
|
| /linux-4.4.14/Documentation/fb/ |
| D | viafb.txt | 175 instead of calling common ioctl function FBIOPUT_VSCREENINFO since
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-single.txt | 51 it by calling pulldown, pullup disabled.
|
| /linux-4.4.14/Documentation/trace/ |
| D | mmiotrace.txt | 102 calling one of the ioremap_*() functions. Mmiotrace is hooked into the
|
| D | tracepoint-analysis.txt | 30 calling
|
| D | coresight.txt | 172 The next field, "struct coresight_platform_data *pdata" is acquired by calling
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | ppc-pv.txt | 138 also act on the shared page. So calling privileged instructions still works as
|
| D | api.txt | 1649 TLB, prior to calling KVM_RUN on the associated vcpu.
1685 physical device command register by calling this ioctl to inform the kernel of
1851 prior to calling the KVM_RUN ioctl.
2654 must be called after calling KVM_CREATE_IRQCHIP, but before calling
3037 execution by changing fields in kvm_run prior to calling the KVM_RUN
3451 to tell KVM which entries have been changed, prior to calling KVM_RUN again
|
| /linux-4.4.14/Documentation/thermal/ |
| D | power_allocator.txt | 242 `thermal_zone_device_update()` (or anything that ends up calling the
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-cxl | 77 all: all segments process calling START_WORK maps.
|
| /linux-4.4.14/Documentation/pps/ |
| D | pps.txt | 100 and then calling the function pps_register_source() in your
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei.txt | 54 /dev/mei is open. The binding to a specific feature is performed by calling
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | cpu-drivers.txt | 234 By calling cpufreq_frequency_table_cpuinfo(struct cpufreq_policy *policy,
|
| /linux-4.4.14/Documentation/filesystems/configfs/ |
| D | configfs.txt | 297 this group is usually defined statically. Before calling
412 probably shouldn't calling them of its own gumption. Rather it should
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 345 histogram of the callers, but actually places the calling
546 goes into an infinite loop (calling cond_sched() to let other tasks
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | cdrom-standard.tex | 356 done by the calling routine in \cdromc, so the low-level routine
463 addressing mode), whatever the calling software requested. But
512 possible to return the error code to the calling program. (We may decide
671 subsequent calls to the device don't cause the calling process to
821 calling device-operations in $cdrom_device_ops$, if implemented and
|
| /linux-4.4.14/arch/x86/crypto/sha-mb/ |
| D | sha1_x8_avx2.S | 59 ## outer calling routine takes care of save and restore of XMM registers
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 159 the numbers in the different calling conventions overlap, then checks in
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 111 - packet is prepared to be processed by the Ethernet layer by calling
420 builtin Ethernet PHYs, per port. This function is responsible for calling
|
| /linux-4.4.14/arch/xtensa/ |
| D | Kconfig | 260 register windows of a calling userspace task onto its stack.
|
| /linux-4.4.14/Documentation/nfc/ |
| D | nfc-hci.txt | 170 calling nfc_llc_register(const char *name, struct nfc_llc_ops *ops);
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 180 will need to reprogram the FPGA by calling this function. If the
|
| /linux-4.4.14/Documentation/hid/ |
| D | hid-transport.txt | 277 Used by HID core before calling ->request() again. A transport driver can use
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | rapidio.txt | 278 into the routing table. The algorithm recurs by calling itself with hopcount + 1
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | modules.txt | 410 calling "make." This has effect when installing both in-tree
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 3294 # register must get updated by calling _calc_ea_fout(). If the <ea> #
3585 # correct register before calling _real_inex(). #
4315 # we're also passing "size" and "strg" back to the calling routine
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-script-python.txt | 270 calling the print_syscall_totals() function from the trace_end()
|