Searched full:handling (Results 1 – 25 of 3163) sorted by relevance
12345678910>>...127
| /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 …]
|
| /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
|
| /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.
|
| /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.
|
| /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 …]
|
| /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()
|
| /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.
|
| /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
|
| /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 …]
|
| /linux-5.10/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-5.10/Documentation/devicetree/bindings/mips/ |
| D | mscc.txt | 14 The SoC has a few registers (DEVCPU_GCB:CHIP_REGS) handling miscellaneous
31 The SoC has a few registers (ICPU_CFG:CPU_SYSTEM_CTRL) handling configuration of
47 The SoC has a few registers (HSIO) handling miscellaneous functionalities:
|
| /linux-5.10/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-5.10/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-5.10/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-5.10/sound/pci/lx6464es/ |
| D | lx_core.h | 104 /* low-level pipe handling */
118 /* low-level stream handling */
150 /* low-level buffer handling */
161 /* low-level gain/peak handling */
167 /* interrupt handling */
|
| /linux-5.10/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-5.10/arch/x86/lib/ |
| D | copy_mc_64.S | 96 * there is no "tail" handling since the source buffer is 8-byte
108 * For write fault handling, given the destination is unaligned,
129 * copy_mc_enhanced_fast_string - memory copy with exception handling
131 * Fast string copy + fault / exception handling. If the CPU does
|
| /linux-5.10/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-5.10/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
|
| D | tls-offload.rst | 31 with its own TCP handling, it is not usable in production environments
166 TLS handling and confirms the sequence number matches its expectation.
179 number is the expected one and proceeds to TLS handling (record delineation,
182 Device indicates successful handling of TLS offload in the per-packet context
191 Resync handling
221 data (to be able to insert the authentication tag) and move onto handling
286 handling. ``ktls`` software fallback handles the decryption of record
353 Error handling
367 Any device TLS offload handling error on the transmission side must result
520 system errors and should never be used as an error handling mechanism
|
| /linux-5.10/Documentation/vm/ |
| D | overcommit-accounting.rst | 7 The Linux kernel supports the following overcommit handling modes
10 Heuristic overcommit handling. Obvious overcommits of address
81 * Review stack handling/building on exec
|
| /linux-5.10/Documentation/driver-api/ |
| D | libata.rst | 200 Some controllers need special handling and have custom tuning rules,
208 tuning logic in that case would bypass handling for drive and bridge
272 Exception and probe handling (EH)
332 Hardware interrupt handling
341 ``->irq_handler`` is the interrupt handling routine registered with the
400 Error handling
419 handling. All normal blk requests and commands for SCSI emulation are
529 code path is taken and very little error handling takes place. A qc is
533 However, failed ATAPI commands require more handling as REQUEST SENSE is
553 :c:func:`ata_qc_timeout` on the qc if so. Actual error handling occurs in
[all …]
|
| /linux-5.10/arch/mips/math-emu/ |
| D | sp_fmax.c | 48 * Quiet NaN handling in ieee754sp_fmax()
74 * Infinity and zero handling in ieee754sp_fmax()
174 * Quiet NaN handling in ieee754sp_fmaxa()
200 * Infinity and zero handling in ieee754sp_fmaxa()
|
12345678910>>...127