| /openbmc/openpower-hw-diags/ |
| H A D | main.cpp | 20 * --all <on|off>: All attention handling
21 * --vital <on|off>: Vital attention handling
22 * --checkstop <on|off>: Checkstop attention handling
23 * --terminate <on|off>: Terminate Immiediately attention handling
24 * --breakpoints <on|off>: Breakpoint attention handling
43 printf(" --all <on|off>: All attention handling\n"); in main()
44 printf(" --vital <on|off>: Vital attention handling\n"); in main()
45 printf(" --checkstop <on|off>: Checkstop attention handling\n"); in main()
47 "handling\n"); in main()
48 printf(" --breakpoints <on|off>: Breakpoint attention handling\n"); in main()
|
| /openbmc/openbmc/poky/bitbake/ |
| H A D | ChangeLog | 12 - Fix invalid regexp in BBMASK error handling (missing import) (#1124)
38 - Fix handling of variables with expansion in the name using _append/_prepend
52 - runqueue.py: Fix idepends handling to avoid dependency errors
73 - Fix unexport handling (#3135)
80 - SRCREV handling updates, improvements and fixes from Poky
93 - Change the wget fetcher failure handling to avoid lockfile problems
103 - Optmise cache handling by more quickly detecting an invalid cache, only
119 - When handling build target failures make sure idepends are checked and
122 - Fix problems with recrdeptask handling where some idepends weren't handled
148 - Fix hg fetcher username/password handling and fix crash
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-control-zone-config/witherspoon/ |
| H A D | zones.yaml | 30 Custom thermal control mode for handling the use of
36 Heavy IO thermal control mode for handling the use
41 Maximum base fan floor mode is for handling the
78 Custom thermal control mode for handling the use of
84 Heavy IO thermal control mode for handling the use
89 Maximum base fan floor mode is for handling the
|
| /openbmc/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.
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.
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ti/ |
| H A 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
|
| /openbmc/linux/include/media/ |
| H A 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.
|
| /openbmc/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
|
| H A 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 …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A 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
|
| 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 …]
|
| /openbmc/u-boot/drivers/mtd/ubi/ |
| H A D | misc.c | 85 * ubi_update_reserved - update bad eraseblock handling accounting data.
89 * bad eraseblock handling and the required level of PEBs that must be
104 ubi_msg(ubi, "reserved more %d PEBs for bad PEB handling", need); in ubi_update_reserved()
109 * eraseblock handling.
116 * for future bad eraseblock handling. in ubi_calculate_reserved()
121 …d) is above the expected limit (%d), not reserving any PEBs for bad PEB handling, will use availab… in ubi_calculate_reserved()
|
| /openbmc/openpower-hw-diags/attn/ |
| H A D | Attention_Handler.md | 21 handling attention requests. The attention handler is loaded into memory when
34 The general handling of attentions is as follows:
48 the handling of attentions. Among these are systemd, dbus, phosphor-logging and
82 handling attentions. Using the PDBG interface the attention handler will query
168 - vital handling enable/disable, default enable
169 - TI handling enable/disable, default enable
170 - BP handling enable/disable, default enable
171 - checkstop handling enable/disable, default enable
|
| /openbmc/ipmitool/control/ |
| H A D | ipmitool.spec.in | 75 erroneous handling of raw Send Message
82 - Change bridge message handling to reuse command ipmi_lan_poll_recv
191 - Fix bug generating garbage on the screen when handling GetDeviceId
210 - Fixed lan interface accessibility timeout handling
215 - Fix SOLv2 NACK and retry handling for Intel ESB2 BMC
239 - Fix improper LUN handling with Tyan SOL
247 - Fix handling of LUNs for LAN interfaces
333 - Improve lan interface retry handling
336 - Fix reservation ID handling when two sessions open to BMC
355 - better handling of SDR printing
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-ipy_1.01.bb | 1 SUMMARY = "IPy - class and tools for handling of IPv4 and IPv6 addresses and networks"
2 DESCRIPTION = "IPy is a Python module for handling IPv4 and IPv6 Addresses and Networks \
4 a comfortable parsing and handling for most notations in use for IPv4 \
|
| /openbmc/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()
|
| /openbmc/linux/crypto/asymmetric_keys/ |
| H A 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
|
| /openbmc/linux/Documentation/block/ |
| H A 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
|
| /openbmc/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.
|
| /openbmc/qemu/include/qapi/ |
| H A D | compat-policy.h | 2 * Policy for handling "funny" management interfaces
31 * policy for handling deprecated management interfaces set with
40 * policy for handling deprecated management interfaces set with
|
| /openbmc/u-boot/Documentation/sphinx/ |
| H A 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
131 # image handling
140 # figure handling
149 # render handling
329 # image handling
366 # figure handling
[all …]
|
| /openbmc/linux/kernel/time/ |
| H A D | tick-sched.h | 29 * it is reset during irq handling phases.
65 /* Tick handling: jiffies stall check */
69 /* Tick handling */
96 /* Full dynticks handling */
|
| /openbmc/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 …
10 …ont end resteers for conditional branches as a result of another branch handling mechanism in the …
17 …s the front end resteers for RET branches as a result of another branch handling mechanism in the …
|
| /openbmc/phosphor-buttons/src/ |
| H A D | debugHostSelector_button.cpp | 23 * callbackHandler if platform specific event handling is needed then a
24 * derived class instance with its specific event handling logic along with
25 * init() function can be created to override the default event handling
|
| /openbmc/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. */
|
| /openbmc/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
|