| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | ufs.rst | 18 3.3 UFS error handling
19 3.4 SCSI Error handling
77 layers. Device level configurations involve handling of query
129 Transfer request handling module of UFSHCD receives SCSI commands
135 3.3 UFS error handling
138 Error handling module handles Host controller fatal errors,
141 3.4 SCSI Error handling
144 This is done through UFSHCD SCSI error handling routines registered
145 with 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 20 handling
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
25 handling
|
| /kernel/linux/linux-5.10/net/rose/ |
| D | rose_in.c | 33 * The handling of the timer(s) is in file rose_timer.c.
34 * Handling of state 0 and connection release is in af_rose.c.
70 * The handling of the timer(s) is in file rose_timer.c
71 * Handling of state 0 and connection release is in af_rose.c.
98 * The handling of the timer(s) is in file rose_timer.c
99 * Handling of state 0 and connection release is in af_rose.c.
209 * The handling of the timer(s) is in file rose_timer.c
210 * Handling of state 0 and connection release is in af_rose.c.
247 * The handling of the timer(s) is in file rose_timer.c
248 * Handling of state 0 and connection release is in af_rose.c.
|
| /kernel/liteos_m/utils/ |
| D | los_error.h | 107 * @brief Define the pointer to the error handling function.
110 * This API is used to define the pointer to the error handling function.
135 * @brief Error handling function.
161 * Error handling function structure.
164 LOS_ERRORHANDLE_FUNC pfnHook; /**< Hook function for error handling. */
214 * @brief Error handling macro capable of returning error codes.
217 …* This API is used to call the error handling function by using an error code and return the same …
238 * @brief Error handling macro capable of returning error codes.
241 …* This API is used to call the error handling function by using an error code and the line number …
267 * This API is used to call the error handling function by using an error code.
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 20 handling
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
25 handling
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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 …]
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/crypto/asymmetric_keys/ |
| D | Makefile | 16 # X.509 Certificate handling
36 # PKCS#8 private key handling
49 # PKCS#7 message handling
69 # Signed PE binary-wrapped key handling
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/liteos_a/kernel/base/include/ |
| D | los_err_pri.h | 51 * @brief Error handling macro capable of returning error codes.
54 …* This API is used to call the error handling function by using an error code and return the same …
74 * @brief Error handling macro capable of returning error codes.
77 …* This API is used to call the error handling function by using an error code and the line number …
102 * This API is used to call the error handling function by using an error code.
|
| /kernel/liteos_a/arch/arm/include/ |
| D | los_exc.h | 33 * @defgroup los_exc Exception handling
138 * @brief Define an exception handling function hook.
141 * This API is used to define the exception handling function hook based on the type of
142 * the exception handling function and record exceptions.
157 * @brief Register an exception handling hook.
160 * This API is used to register an exception handling hook.
165 * @retval #LOS_OK The exception handling hook is successfully registered.
|
| /kernel/linux/linux-5.10/crypto/asymmetric_keys/ |
| D | Makefile | 17 # X.509 Certificate handling
34 # PKCS#8 private key handling
47 # PKCS#7 message handling
67 # Signed PE binary-wrapped key handling
|
| /kernel/liteos_a/kernel/include/ |
| D | los_err.h | 33 * @defgroup los_err Error handling
50 * @brief Define the pointer to the error handling function.
53 * This API is used to define the pointer to the error handling function.
78 * @brief Error handling function.
104 * @brief set Error handling function.
|
| /kernel/linux/linux-5.10/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
133 # image handling
142 # figure handling
151 # render handling
335 # image handling
372 # figure handling
[all …]
|