Searched full:whenever (Results 1 – 25 of 1939) sorted by relevance
12345678910>>...78
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | debug-objects.rst | 70 This function is called whenever the initialization function of a real
93 This function is called whenever the initialization function of a real
117 This function is called whenever the activation function of a real
142 This function is called whenever the deactivation function of a real
213 This function is called from the debug code whenever a problem in
231 This function is called from the debug code whenever a problem in
259 This function is called from the debug code whenever a problem in
272 This function is called from the debug code whenever a problem in
288 This function is called from the debug code whenever a problem in
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| D | debug-objects.rst | 70 This function is called whenever the initialization function of a real
93 This function is called whenever the initialization function of a real
117 This function is called whenever the activation function of a real
142 This function is called whenever the deactivation function of a real
213 This function is called from the debug code whenever a problem in
231 This function is called from the debug code whenever a problem in
259 This function is called from the debug code whenever a problem in
272 This function is called from the debug code whenever a problem in
288 This function is called from the debug code whenever a problem in
|
| /kernel/linux/linux-5.10/sound/oss/dmasound/ |
| D | Kconfig | 12 inserted in and removed from the running kernel whenever you
26 inserted in and removed from the running kernel whenever you
40 inserted in and removed from the running kernel whenever you
|
| /kernel/linux/linux-6.6/sound/oss/dmasound/ |
| D | Kconfig | 12 inserted in and removed from the running kernel whenever you
26 inserted in and removed from the running kernel whenever you
40 inserted in and removed from the running kernel whenever you
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-pinctrl.txt | 47 Whenever an access is made to a device on a child bus, the relevant pinctrl
50 If an idle state is defined, whenever an access is not being made to a device
54 left programmed into hardware whenever no access is being made of a device on
|
| D | i2c-mux-gpio.txt | 35 Whenever an access is made to a device on a child bus, the value set
40 whenever an access is not being made to a device on a child bus, the
44 left programmed into hardware whenever no access is being made to a
|
| D | i2c-mux-reg.txt | 26 Whenever an access is made to a device on a child bus, the value set
30 whenever an access is not being made to a device on a child bus, the
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-pinctrl.yaml | 41 Whenever an access is made to a device on a child bus, the relevant pinctrl state will be
44 If an idle state is defined, whenever an access is not being made to a device on a child bus,
48 into hardware whenever no access is being made of a device on a child bus.
|
| D | i2c-mux-gpio.yaml | 32 Whenever an access is made to a device on a child bus, the value set in the relevant node's reg
36 If an idle state is defined, using the idle-state (optional) property, whenever an access is not
40 hardware whenever no access is being made to a device on a child bus.
|
| D | i2c-mux-reg.txt | 26 Whenever an access is made to a device on a child bus, the value set
30 whenever an access is not being made to a device on a child bus, the
|
| /kernel/linux/linux-6.6/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 20 DMA-eligible devices to the controller itself. Whenever the device
38 Moreover, some DMA controllers, whenever the RAM is used as a source
59 transfer, and whenever the transfer is started, the controller will go
65 and whenever a DRQ will be asserted, it will go through the collection
77 whenever you're willing to use DMA.
377 - These functions will be called whenever a driver will call
439 and starts the transfer. Whenever that transfer is done, it
626 most work to a tasklet, including the start of a new transfer whenever
|
| /kernel/linux/linux-5.10/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 20 DMA-eligible devices to the controller itself. Whenever the device
38 Moreover, some DMA controllers, whenever the RAM is used as a source
59 transfer, and whenever the transfer is started, the controller will go
65 and whenever a DRQ will be asserted, it will go through the collection
77 whenever you're willing to use DMA.
358 - These functions will be called whenever a driver will call
420 and starts the transfer. Whenever that transfer is done, it
607 most work to a tasklet, including the start of a new transfer whenever
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 85 the MoCA interface whenever the MoCA coaxial cable gets disconnected or the
97 Whenever possible, the SF2 driver tries to minimize the overall switch power
111 MAC controller wake-on logic. Whenever Wake-on-LAN is requested, an intersection
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| D | bcm_sf2.rst | 85 the MoCA interface whenever the MoCA coaxial cable gets disconnected or the
97 Whenever possible, the SF2 driver tries to minimize the overall switch power
111 MAC controller wake-on logic. Whenever Wake-on-LAN is requested, an intersection
|
| /kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/ |
| D | ia_css_irq.h | 96 /* CSS receiver error types. Whenever the CSS receiver has encountered
100 * fact common (whenever an error occurs, it usually results in multiple
164 * This function should be used whenever a CSI receiver error interrupt is
183 * This function should be used whenever a CSI receiver error interrupt is
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_irq.h | 95 /* CSS receiver error types. Whenever the CSS receiver has encountered
99 * fact common (whenever an error occurs, it usually results in multiple
163 * This function should be used whenever a CSI receiver error interrupt is
182 * This function should be used whenever a CSI receiver error interrupt is
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlegacy/ |
| D | Kconfig | 34 inserted in and removed from the running kernel whenever you want),
60 inserted in and removed from the running kernel whenever you want),
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlegacy/ |
| D | Kconfig | 33 inserted in and removed from the running kernel whenever you want),
60 inserted in and removed from the running kernel whenever you want),
|
| /kernel/linux/linux-6.6/Documentation/mm/damon/ |
| D | maintainer-profile.rst | 11 whenever possible and posted to the mailing lists.
24 tree[1] whenever possible. damon/next is only for preview of others' works in
|
| /kernel/linux/linux-5.10/drivers/visorbus/ |
| D | vbuschannel.h | 28 * Must increment this whenever you insert or delete fields within this channel
29 * struct. Also increment whenever you change the meaning of fields within this
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | uaccess-asm.h | 45 * Whenever we re-enter userspace, the domains should always be
59 * Whenever we re-enter userspace, the domains should always be
|
| /kernel/linux/linux-6.6/arch/arm/include/asm/ |
| D | uaccess-asm.h | 45 * Whenever we re-enter userspace, the domains should always be
59 * Whenever we re-enter userspace, the domains should always be
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | remote-controller.rst | 52 whenever the input device is really present, which of the devices it
53 is, check whenever pressing keys on the remote actually generates
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/media/ |
| D | remote-controller.rst | 52 whenever the input device is really present, which of the devices it
53 is, check whenever pressing keys on the remote actually generates
|
| /kernel/linux/linux-6.6/rust/kernel/ |
| D | build_assert.rs | 39 /// [`static_assert!`] should be preferred to `build_assert!` whenever possible.
45 /// possible, so [`static_assert!`] should be used whenever possible.
|
12345678910>>...78