Searched full:routine (Results 1 – 25 of 134) sorted by relevance
123456
/Documentation/watchdog/ |
D | watchdog-kernel-api.rst | 33 The watchdog_register_device routine registers a watchdog timer device. 34 The parameter of this routine is a pointer to a watchdog_device structure. 35 This routine returns zero on success and a negative errno code for failure. 37 The watchdog_unregister_device routine deregisters a registered watchdog timer 38 device. The parameter of this routine is the pointer to the registered 145 * start: this is a pointer to the routine that starts the watchdog timer 147 The routine needs a pointer to the watchdog timer device structure as a 154 * stop: with this routine the watchdog timer device is being stopped. 156 The routine needs a pointer to the watchdog timer device structure as a 159 driver supporting such hardware does not have to implement the stop routine. [all …]
|
/Documentation/driver-api/memory-devices/ |
D | ti-gpmc.rst | 29 generic timing routine was developed to achieve above requirements. 31 Generic routine provides a generic method to calculate gpmc timings 40 field as required by peripheral, educate generic timing routine to 45 Generic timing routine has been verified to work properly on 48 A word of caution: generic timing routine has been developed based 52 in mainline having custom timing routine) and by simulation. 176 mentioned above, refer timing routine for more details. To know what
|
/Documentation/mm/ |
D | hugetlbfs_reserv.rst | 103 These operations result in a call to the routine hugetlb_reserve_pages():: 112 was specified, then this routine returns immediately as no reservations 150 reservations is known. The routine hugetlb_acct_memory() is called to check 182 is performed within the routine alloc_hugetlb_folio():: 195 The helper routine vma_needs_reservation() is called to determine if a 198 information on what this routine does. 206 exists and can be used for the allocation, the routine dequeue_huge_page_vma() 207 is called. This routine takes two arguments related to reservations: 239 The routine vma_commit_reservation() is then called to adjust the reserve 287 The routine first calls hugepage_subpool_put_pages() for the page. If this [all …]
|
/Documentation/scsi/ |
D | 53c700.rst | 73 In the detect routine, you need to allocate a struct 77 routine into the interrupt line and call NCR_700_detect with the host 82 In the release routine, you must free the NCR_700_Host_Parameters that 93 where host is the return from the relevant NCR_700_detect() routine. 95 You may also write your own interrupt handling routine which calls
|
D | ChangeLog.ips | 74 4.00.05 - Remove wish_block from init routine 93 3.60.01 - Remove bogus error check in passthru routine. 109 0.99.03 - Make interrupt routine handle all completed request on the
|
D | ChangeLog.megaraid_sas | 214 c). In driver's timeout routine, driver will report to 215 OS as reset. Also driver's queue routine will block the 218 d). in Driver's ISR routine, if driver get the FW state as 222 e). In driver's IOCTL routine, the application cmds will wait for the 232 3. In driver's timeout routine, driver will do three time reset if fw is in 264 2. Takeoff the debug print-out in aen_polling routine. 337 1. Add shutdown DCMD cmd to the shutdown routine to make FW shutdown proper. 416 1. Added the megasas_reset_timer routine to intercept cmd timeout and throttle io. 435 routine for max 3 minutes for all pending command completion. Now driver will 436 call completion routine every 5 seconds from the reset routine instead of [all …]
|
D | dpti.rst | 63 - Fixed pointer bug in bus reset routine 79 - Add code to rescan routine that notifies scsi-core about new devices
|
/Documentation/admin-guide/device-mapper/ |
D | kcopyd.rst | 30 completion callback routine, and a pointer to some context data for the copy:: 39 When the copy completes, kcopyd will call the user's completion routine,
|
/Documentation/leds/ |
D | ledtrig-transient.rst | 26 routine for the default trigger gets called. During registration of an led 29 When the driver unregisters, deactivation routine for the currently active 46 as its default trigger, trigger activation routine will get called. During 52 Transient trigger activation routine doesn't change the LED state. It 54 deactivation routine, will cancel any timer that is active before it cleans
|
/Documentation/driver-api/ |
D | vme.rst | 8 with the VME subsystem, typically called from the devices init routine. This is 35 The '.probe' element should contain a pointer to the probe routine. The 36 probe routine is passed a :c:type:`struct vme_dev <vme_dev>` pointer as an 45 driver's exit routine. 51 Once a driver has registered with the VME core the provided match routine will 54 failure. For all successful matches, the probe routine of the corresponding 55 driver is called. The probe routine is passed a pointer to the devices
|
/Documentation/driver-api/rapidio/ |
D | rapidio.rst | 107 an enumeration and/or discovery routine may be called automatically or 156 initialization routine. In this case an enumerating module shall be loaded 160 routine depending on the configured role of a master port: host or agent. 217 initialization routine calls rio_init_mports() to perform enumeration or 249 process from module initialization routine. 267 table entry contains a pointer to a switch-specific initialization routine that 316 method's module initialization routine calls rio_register_scan() to attach
|
/Documentation/power/ |
D | pci.rst | 450 The pci_pm_prepare() routine first puts the device into the "fully functional" 455 The pci_pm_suspend() routine first checks if the device's driver implements 462 bridges are ignored by this routine). Next, the device driver's pm->suspend() 472 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has 474 invoked while this routine is running. It first checks if the device's driver 476 late suspend routine is called and its result is returned (the standard 479 present, the device's standard configuration registers are saved and the routine 520 The pci_pm_resume_noirq() routine first puts the device into the full-power 534 The pci_pm_resume() routine first checks if the device's standard configuration 546 on each other in a known way, the pci_pm_resume() routine may be executed for [all …]
|
/Documentation/sound/designs/ |
D | compress-offload.rst | 104 This routine returns the list of audio formats supported. Querying the 109 For each codec, this routine returns a list of 119 settings, this routine returns the minimum buffer size handled by the 126 This routine sets the configuration chosen for a specific codec. The 224 This routine sets the encoder delay and encoder padding. This can be used by 229 This routine tells DSP that metadata and write operation sent after this would
|
/Documentation/spi/ |
D | spi-lm70llp.rst | 57 The bitbanger routine in this driver (lm70_txrx) is called back from 75 So: the getmiso inline routine in this driver takes this fact into account,
|
/Documentation/core-api/ |
D | cachetlb.rst | 95 At the end of every page fault, this routine is invoked to tell 100 This routine is also invoked in various other places which pass 202 This routine need only be implemented if the platform utilizes 290 This routine need only be called for page cache pages 306 If D-cache aliasing is not an issue, this routine may simply be defined 365 If the icache does not snoop stores then this routine will need
|
D | memory-hotplug.rst | 39 A callback routine can be registered by calling:: 74 The callback routine shall return one of the values
|
/Documentation/pcmcia/ |
D | driver.rst | 20 Once added, the driver probe routine will be invoked for any unclaimed
|
/Documentation/networking/ |
D | driver.rst | 23 After the ndo_stop routine has been called, the hardware must 31 The ndo_stop routine will be called by unregister_netdevice
|
/Documentation/networking/device_drivers/ethernet/toshiba/ |
D | spider_net.rst | 78 The show_rx_chain() routine will print out the locations of the 172 routine. When the driver receives RX interrupts, but an examination 194 so its not appropriate to wait for the poll routine to refill, since 195 the poll routine runs only once per jiffy. The low-watermark mechanism
|
/Documentation/crypto/ |
D | async-tx-api.rst | 130 2. Specify a completion callback. The callback routine runs in tasklet 135 unknown length it can use the async_trigger_callback() routine to set a 231 specifying the necessary channel, the filter_fn routine can be used to 232 disposition the available channels in the system. The filter_fn routine
|
D | descore-readme.rst | 71 the key setting routine. also, i have no interest in re-implementing 122 the des routine here is buried inside a loop to do the 145 as in crypt above, the des routine is buried in a loop. it's 342 call this before using any other routine with ``Quick`` in its name. 354 is called with m, the routine will act like standard des 365 provide a routine that converts 128 6-bit bytes (specified in 383 Small|Quick determines whether you use the normal routine
|
/Documentation/driver-api/mei/ |
D | mei-client-bus.rst | 123 And the driver's simplified probe routine would look like that: 137 In the probe routine the driver first enable the MEI device and then registers
|
/Documentation/ABI/testing/ |
D | sysfs-block-aoe | 30 kicked by the periodic timer handler routine.
|
/Documentation/timers/ |
D | hpet.rst | 23 of the HPET before the driver module_init routine is called. This enables
|
/Documentation/arch/s390/ |
D | cds.rst | 76 generic interrupt routine. This function is called by the interrupt entry 77 routine whenever an I/O interrupt is presented to the system. The do_IRQ() 78 routine determines the interrupt status and calls the device specific 152 ccw to retrieve device characteristics in its online routine. 158 ccw_device_start() routine allows to specify whether it expects the CDS layer 196 device driver I/O requests must be issued using this routine. A device driver 198 routine provides all interfaces required to drive arbitrary devices. 423 provides the ccw_device_resume() routine.
|
123456