Searched refs:handling (Results 1 – 25 of 533) sorted by relevance
12345678910>>...22
| /linux-6.6.21/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
|
| D | gate.txt | 21 "ti,dss-gate-clock" - gate clock with DSS specific hardware handling
22 "ti,am35xx-gate-clock" - gate clock with AM35xx specific hardware handling
26 "ti,hsdiv-gate-clock" - gate clock with OMAP36xx specific hardware handling,
|
| /linux-6.6.21/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. */
|
| D | serial-rs485.rst | 69 /* Error handling. See errno. */
97 /* Error handling. See errno. */
104 /* Error handling. See errno. */
|
| /linux-6.6.21/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.
329 - Large rewrite of the SCSI MESSAGE handling.
[all …]
|
| /linux-6.6.21/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
|
| D | mac80211.rst | 13 Basic hardware handling
49 This chapter should describe PHY handling including start/stop callbacks
86 drivers as well as transmit status handling.
|
| D | cfg80211.rst | 96 Scanning and BSS list handling
100 :doc: Scanning and BSS list handling
|
| /linux-6.6.21/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-6.6.21/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.6.21/drivers/staging/media/imx/ |
| D | TODO | 11 - Similarly to the legacy control handling, legacy format handling where
|
| /linux-6.6.21/arch/mips/sgi-ip22/ |
| D | Platform | 6 # be aligned to a multiple of the kernel stack size or the handling of the
23 # be 16kb aligned or the handling of the current variable will break.
|
| /linux-6.6.21/Documentation/arch/arm/vfp/ |
| D | release-notes.rst | 35 - fadd/fsub shows some differences in the handling of +0 / -0 results
37 - the handling of underflow exceptions is slightly different. If a
|
| /linux-6.6.21/Documentation/mm/ |
| D | overcommit-accounting.rst | 5 The Linux kernel supports the following overcommit handling modes
8 Heuristic overcommit handling. Obvious overcommits of address
80 * Review stack handling/building on exec
|
| /linux-6.6.21/tools/testing/selftests/tc-testing/ |
| D | TODO.txt | 23 - Proper exception handling - make an exception class and use it
25 - a TestCase class, for easier testcase handling, searching, comparison
|
| /linux-6.6.21/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.6.21/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.6.21/scripts/coccinelle/null/ |
| D | kmerr.cocci | 4 /// error handling code later in the function, which may be helpful
5 /// in determining what the error handling code for the call to kmalloc etc
|
| /linux-6.6.21/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.6.21/Documentation/virt/acrn/ |
| D | io-request.rst | 3 I/O request handling
9 handling are described in the following sections.
26 An I/O client is responsible for handling User VM I/O requests whose accessed
|
| /linux-6.6.21/tools/testing/selftests/riscv/hwprobe/ |
| D | sys_hwprobe.S | 9 # handling, the caller can deal with it.
|
| /linux-6.6.21/drivers/staging/nvec/ |
| D | TODO | 4 - move event handling to nvec_events
|
| /linux-6.6.21/Documentation/networking/ |
| D | bareudp.rst | 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>>...22