Searched full:handling (Results 1 – 25 of 3611) sorted by relevance
12345678910>>...145
| /linux-6.12.1/net/rose/ |
| D | rose_in.c | 34 * The handling of the timer(s) is in file rose_timer.c.
35 * Handling of state 0 and connection release is in af_rose.c.
71 * The handling of the timer(s) is in file rose_timer.c
72 * Handling of state 0 and connection release is in af_rose.c.
99 * The handling of the timer(s) is in file rose_timer.c
100 * Handling of state 0 and connection release is in af_rose.c.
210 * The handling of the timer(s) is in file rose_timer.c
211 * Handling of state 0 and connection release is in af_rose.c.
248 * The handling of the timer(s) is in file rose_timer.c
249 * Handling of state 0 and connection release is in af_rose.c.
|
| /linux-6.12.1/Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 18 handling
19 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
20 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
21 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
23 handling
|
| /linux-6.12.1/Documentation/scsi/ |
| D | ufs.rst | 18 3.3 UFS error handling
19 3.4 SCSI Error handling
79 layers. Device level configurations involve handling of query
131 Transfer request handling module of UFSHCD receives SCSI commands
137 3.3 UFS error handling
140 Error handling module handles Host controller fatal errors,
143 3.4 SCSI Error handling
146 This is done through UFSHCD SCSI error handling routines registered
147 with the SCSI Midlayer. Examples of some of the error handling commands
|
| D | ChangeLog.sym53c8xx | 25 handling. If the DSA didn't match a CCB, a bad write to
97 * Simpler handling of illegal phases and data overrun from
100 * Sync the residual handling code with sym-1.6.2 and now
157 - Updated the SCRIPTS error handling of the SWIDE
249 - Cleanup of the extended error status handling:
254 - Remove the quirk handling that has been useless since day one.
270 - Fix some bug in the fully untested MDP handling:) and share
271 some code between MDP handling and residual calculation.
275 - Add support of some 'resource handling' for linux-2.3.13.
317 - Handling of the SWIDE (low byte residue at the end of a CHMOV
[all …]
|
| /linux-6.12.1/include/media/ |
| D | dvb_vb2.h | 176 * buffer handling.
192 * buffer handling.
201 * buffer handling.
211 * buffer handling.
224 * buffer handling.
236 * buffer handling.
247 * dvb_vb2_qbuf() - Wrapper to vb2_core_qbuf() for Digital TV buffer handling.
259 * buffer handling.
270 * dvb_vb2_mmap() - Wrapper to vb2_mmap() for Digital TV buffer handling.
|
| /linux-6.12.1/Documentation/core-api/ |
| D | entry.rst | 1 Entry/exit handling for exceptions, interrupts, syscalls and KVM
63 low-level C code must not be instrumented. A typical syscall handling function
122 Task work handling is done separately for guest at the boundary of the
131 Interrupts entry and exit handling is slightly more complex than syscalls
135 and exit handling is exactly the same as for syscalls.
138 exit handling is slightly different. RCU state is only updated when the
144 The architecture-specific part looks similar to syscall handling:
189 example, softirq handling happens within an irqentry_{enter,exit}() block with
278 while handling an NMI. So NMI entry code has to be reentrant and state updates
|
| D | genericirq.rst | 4 Linux generic IRQ handling
13 The generic interrupt handling layer is designed to provide a complete
14 abstraction of interrupt handling for device drivers. It is able to
23 generic IRQ handling layer.
28 The original implementation of interrupt handling in Linux uses the
52 optimize the flow of the interrupt handling for each specific interrupt
54 the optimized handling of a given type.
62 have different flow handling.
80 The separation makes the generic interrupt handling layer more flexible
120 high-level IRQ handling function only uses desc->irq_data.chip
[all …]
|
| /linux-6.12.1/Documentation/block/ |
| D | ublk.rst | 38 driver, thus completing the request cycle. This way, any specific IO handling
39 logic is totally done by userspace, such as loop's IO handling, NBD's IO
46 Both the IO request forward and IO handling result committing are done via
51 done by io_uring, but also the preferred IO handling in ublk server is io_uring
119 pthread & io_uring for handling ublk IO), this command is sent to the
156 1) if kernel is capable of handling ``UBLK_F_UNPRIVILEGED_DEV``
171 2) if kernel isn't capable of handling ``UBLK_F_UNPRIVILEGED_DEV``
215 re-issued to the new process after handling ``UBLK_CMD_END_USER_RECOVERY``.
232 ublk server needs to create per-queue IO pthread & io_uring for handling IO
234 focuses on IO handling and shouldn't handle any control & management
|
| /linux-6.12.1/net/x25/ |
| D | x25_in.c | 84 * The handling of the timer(s) is in file x25_timer.c.
85 * Handling of state 0 and connection release is in af_x25.c.
172 * The handling of the timer(s) is in file x25_timer.c
173 * Handling of state 0 and connection release is in af_x25.c.
205 * The handling of the timer(s) is in file x25_timer.c
206 * Handling of state 0 and connection release is in af_x25.c.
341 * The handling of the timer(s) is in file x25_timer.c
342 * Handling of state 0 and connection release is in af_x25.c.
387 * The handling of the timer(s) is in file x25_timer.c
388 * Handling of state 0 and connection release is in af_x25.c.
|
| /linux-6.12.1/drivers/mtd/ubi/ |
| D | misc.c | 84 * ubi_update_reserved - update bad eraseblock handling accounting data.
88 * bad eraseblock handling and the required level of PEBs that must be
103 ubi_msg(ubi, "reserved more %d PEBs for bad PEB handling", need); in ubi_update_reserved()
108 * eraseblock handling.
115 * for future bad eraseblock handling. in ubi_calculate_reserved()
120 …d) is above the expected limit (%d), not reserving any PEBs for bad PEB handling, will use availab… in ubi_calculate_reserved()
|
| /linux-6.12.1/crypto/asymmetric_keys/ |
| D | Makefile | 16 # X.509 Certificate handling
38 # PKCS#8 private key handling
51 # PKCS#7 message handling
71 # Signed PE binary-wrapped key handling
|
| /linux-6.12.1/sound/pci/lx6464es/ |
| D | lx_core.h | 104 /* low-level pipe handling */
118 /* low-level stream handling */
147 /* low-level buffer handling */
158 /* low-level gain/peak handling */
164 /* interrupt handling */
|
| /linux-6.12.1/drivers/uio/ |
| D | Kconfig | 10 is also required for interrupt handling to work properly.
29 tristate "Userspace I/O platform driver with generic IRQ handling"
32 interrupt handling code. Shared interrupts are not supported.
46 interrupt handling code. Shared interrupts are not supported.
122 In particular, it implements interrupt handling. This can be used
|
| /linux-6.12.1/kernel/time/ |
| D | tick-sched.h | 23 * it is reset during irq handling phases.
68 /* Tick handling: jiffies stall check */
72 /* Tick handling */
98 /* Full dynticks handling */
|
| /linux-6.12.1/Documentation/power/ |
| D | suspend-and-interrupts.rst | 65 That may involve turning on a special signal handling logic within the platform
69 handling system wakeup events. Then, if a given interrupt line is supposed to
77 handling the given IRQ as a system wakeup interrupt line and disable_irq_wake()
111 any special interrupt handling logic for it to work.
121 First of all, if the IRQ is not shared, the rules for handling IRQF_NO_SUSPEND
123 directly at odds with the rules for handling system wakeup interrupts (interrupt
|
| /linux-6.12.1/net/ax25/ |
| D | ax25_ds_in.c | 29 * The handling of the timer(s) is in file ax25_ds_timer.c.
30 * Handling of state 0 and connection release is in ax25.c.
97 * The handling of the timer(s) is in file ax25_ds_timer.c
98 * Handling of state 0 and connection release is in ax25.c.
142 * The handling of the timer(s) is in file ax25_timer.c
143 * Handling of state 0 and connection release is in ax25.c.
|
| D | ax25_std_in.c | 36 * The handling of the timer(s) is in file ax25_std_timer.c.
37 * Handling of state 0 and connection release is in ax25.c.
100 * The handling of the timer(s) is in file ax25_std_timer.c
101 * Handling of state 0 and connection release is in ax25.c.
138 * The handling of the timer(s) is in file ax25_std_timer.c
139 * Handling of state 0 and connection release is in ax25.c.
263 * The handling of the timer(s) is in file ax25_std_timer.c
264 * Handling of state 0 and connection release is in ax25.c.
|
| /linux-6.12.1/Documentation/driver-api/serial/ |
| D | serial-iso7816.rst | 15 handling communication with a smart card.
49 /* Error handling. See errno. */
77 /* Error handling. See errno. */
84 /* Error handling. See errno. */
|
| /linux-6.12.1/Documentation/sphinx/ |
| D | kfigure.py | 4 scalable figure and image handling
7 Sphinx extension which implements scalable image handling.
14 handling from the author's POV. Directives like ``kernel-figure`` implement
19 * ``.. kernel-image``: for image handling / a ``.. image::`` replacement
21 * ``.. kernel-figure``: for figure handling / a ``.. figure::`` replacement
129 # image handling
138 # figure handling
147 # render handling
427 # image handling
464 # figure handling
[all …]
|
| /linux-6.12.1/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | frontend.json | 3 …mes the front end resteers for any branch as a result of another branch handling mechanism in the …
11 …ont end resteers for conditional branches as a result of another branch handling mechanism in the …
19 …s the front end resteers for RET branches as a result of another branch handling mechanism in the …
|
| /linux-6.12.1/arch/x86/lib/ |
| D | copy_mc_64.S | 84 * there is no "tail" handling since the source buffer is 8-byte
96 * For write fault handling, given the destination is unaligned,
117 * copy_mc_enhanced_fast_string - memory copy with exception handling
119 * Fast string copy + fault / exception handling. If the CPU does
|
| /linux-6.12.1/net/netrom/ |
| D | nr_in.c | 68 * The handling of the timer(s) is in file nr_timer.c.
69 * Handling of state 0 and connection release is in netrom.c.
112 * The handling of the timer(s) is in file nr_timer.c
113 * Handling of state 0 and connection release is in netrom.c.
143 * The handling of the timer(s) is in file nr_timer.c
144 * Handling of state 0 and connection release is in netrom.c.
|
| /linux-6.12.1/Documentation/driver-api/80211/ |
| D | mac80211-advanced.rst | 108 Station handling
184 Key handling
187 Key handling basics
191 :doc: Key handling basics
208 Station info handling
|
| /linux-6.12.1/drivers/media/platform/allegro-dvt/ |
| D | nal-rbsp.h | 22 * struct rbsp - State object for handling a raw byte sequence payload
28 * @error: an error occurred while handling the rbsp
36 * pointers for handling each type in the rbsp.
|
| /linux-6.12.1/Documentation/networking/ |
| D | bareudp.rst | 14 Special Handling
16 The bareudp device supports special handling for MPLS & IP as they can have
20 This special handling can be enabled only for ethertypes ETH_P_IP & ETH_P_MPLS_UC
|
12345678910>>...145