| /linux/net/rose/ |
| H A 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.
211 * The handling of the timer(s) is in file rose_timer.c
212 * Handling of state 0 and connection release is in af_rose.c.
249 * The handling of the timer(s) is in file rose_timer.c
250 * Handling of state 0 and connection release is in af_rose.c.
|
| /linux/include/media/ |
| H A D | dvb_vb2.h | 177 * buffer handling.
193 * buffer handling.
202 * buffer handling.
212 * buffer handling.
225 * buffer handling.
237 * buffer handling.
248 * dvb_vb2_qbuf() - Wrapper to vb2_core_qbuf() for Digital TV buffer handling.
260 * buffer handling.
271 * dvb_vb2_mmap() - Wrapper to vb2_mmap() for Digital TV buffer handling.
|
| /linux/Documentation/scsi/ |
| H A 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
|
| /linux/Documentation/devicetree/bindings/clock/ti/ |
| H A D | ti,interface-clock.yaml | 26 - ti,omap3-hsotgusb-interface-clock # interface clock with USB specific HW handling
27 - ti,omap3-dss-interface-clock # interface clock with DSS specific HW handling
28 - ti,omap3-ssi-interface-clock # interface clock with SSI specific HW handling
29 - ti,am35xx-interface-clock # interface clock with AM35xx specific HW handling
30 - ti,omap2430-interface-clock # interface clock with OMAP2430 specific HW handling
|
| /linux/Documentation/core-api/ |
| H A 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/net/x25/ |
| H A 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/drivers/mtd/ubi/ |
| H A 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/crypto/asymmetric_keys/ |
| H A 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/sound/pci/lx6464es/ |
| H A 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/drivers/uio/ |
| H A 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/kernel/time/ |
| H A 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/net/ax25/ |
| H A 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.
|
| H A 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/Documentation/power/ |
| H A 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/Documentation/driver-api/serial/ |
| H A 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/net/netrom/ |
| H A 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/Documentation/gpu/ |
| H A D | nouveau.rst | 16 NVKM provides a unified interface for handling various GPU architectures.
18 It enables resource management, power control, memory handling, and command
32 :doc: GSP message handling policy
|
| /linux/arch/x86/lib/ |
| H A 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/tools/perf/pmu-events/arch/x86/knightslanding/ |
| H A 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/Documentation/driver-api/80211/ |
| H A D | mac80211-advanced.rst | 108 Station handling
184 Key handling
187 Key handling basics
191 :doc: Key handling basics
208 Station info handling
|
| /linux/Documentation/driver-api/ |
| H A D | libata.rst | 184 Some controllers need special handling and have custom tuning rules,
192 tuning logic in that case would bypass handling for drive and bridge
256 Exception and probe handling (EH)
288 :c:func:`ata_std_error_handler` will perform a standard error handling sequence
315 Hardware interrupt handling
324 ``->irq_handler`` is the interrupt handling routine registered with the
382 Error handling
401 handling. All normal blk requests and commands for SCSI emulation are
500 code path is taken and very little error handling takes place. A qc is
504 However, failed ATAPI commands require more handling as REQUEST SENSE is
[all …]
|
| /linux/drivers/media/platform/allegro-dvt/ |
| H A 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/Documentation/networking/ |
| H A D | bareudp.rst | 14 Special Handling
17 The bareudp device supports special handling for MPLS & IP as they can have
21 This special handling can be enabled only for ethertypes ETH_P_IP & ETH_P_MPLS_UC
|
| /linux/Documentation/mm/ |
| H A D | overcommit-accounting.rst | 5 The Linux kernel supports the following overcommit handling modes
8 Heuristic overcommit handling. Obvious overcommits of address
79 * Review stack handling/building on exec
|
| /linux/Documentation/timers/ |
| H A D | hrtimers.rst | 18 - the forced handling of low-resolution and high-resolution timers in
30 necessitate a more complex handling of high resolution timers, which
37 the timer wheel has already introduced a quite complex handling of
104 high-resolution clocks though, it also simplifies the handling of
113 be set without having to touch the rbtree. This also makes the handling
|