Home
last modified time | relevance | path

Searched refs:handling (Results 1 – 25 of 805) sorted by relevance

12345678910>>...33

/openbmc/openbmc-test-automation/openpower/ras/
H A Dtest_host_ras.robot30 [Documentation] Verify recoverable callout handling for MCACALIFIR with
40 [Documentation] Verify recoverable callout handling for MCACALIFIR with
50 [Documentation] Verify unrecoverable callout handling for MCACALIFIR.
61 [Documentation] Verify recoverable callout handling for mci with
71 [Documentation] Verify unrecoverable callout handling for mci.
82 [Documentation] Verify recoverable callout handling for CXA with
92 [Documentation] Verify recoverable callout handling for CXA with
102 [Documentation] Verify unrecoverable callout handling for CXAFIR.
114 [Documentation] Verify recoverable callout handling for OBUS with
126 [Documentation] Verify recoverable callout handling for NPU0 with
[all …]
H A Dtest_bmc_ras.robot33 [Documentation] Verify recoverable callout handling for MCACALIFIR
43 [Documentation] Verify recoverable callout handling for MCACALIFIR
53 [Documentation] Verify unrecoverable callout handling for MCACALIFIR
65 [Documentation] Verify recoverable callout handling for MCI
75 [Documentation] Verify unrecoverable callout handling for mci
88 [Documentation] Verify recoverable callout handling for CXA
98 [Documentation] Verify recoverable callout handling for CXA
108 [Documentation] Verify unrecoverable callout handling for CXAFIR
120 [Documentation] Verify recoverable callout handling for OBUS
132 [Documentation] Verify recoverable callout handling for NPU0
[all …]
H A Dtest_host_boot_ras.robot31 [Documentation] Verify recoverable callout handling for MCACALIFIR
44 [Documentation] Verify recoverable callout handling for MCI
56 [Documentation] Verify recoverable callout handling for NXDMAENG
70 [Documentation] Verify recoverable callout handling for L2FIR
85 [Documentation] Verify recoverable callout handling for OCCFIR
99 [Documentation] Verify recoverable callout handling for NCUFIR
111 [Documentation] Verify unrecoverable callout handling for NCUFIR
122 [Documentation] Verify unrecoverable callout handling for L3FIR
133 [Documentation] Verify unrecoverable callout handling for L2FIR
144 [Documentation] Verify unrecoverable callout handling for CXAFIR
[all …]
H A Dtest_reboot_ras.robot2 Documentation This suite tests error log callout handling when checkstop
21 [Documentation] Verify host unrecoverable callout handling at reboot.
31 [Documentation] Verify unrecoverable callout handling
/openbmc/linux/Documentation/devicetree/bindings/clock/ti/
H A Dinterface.txt20 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/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-ipy_1.01.bb1 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/openbmc/poky/bitbake/
H A DChangeLog12 - 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/linux/Documentation/driver-api/serial/
H A Dserial-iso7816.rst15 handling communication with a smart card.
49 /* Error handling. See errno. */
77 /* Error handling. See errno. */
84 /* Error handling. See errno. */
/openbmc/qemu/qapi/
H A Dcompat.json11 # Policy for handling "funny" input.
27 # Policy for handling "funny" output.
41 # Policy for handling deprecated management interfaces.
/openbmc/linux/Documentation/scsi/
H A Dufs.rst18 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
/openbmc/linux/Documentation/driver-api/80211/
H A Dmac80211-advanced.rst108 Station handling
184 Key handling
187 Key handling basics
191 :doc: Key handling basics
208 Station info handling
/openbmc/linux/Documentation/devicetree/bindings/mips/
H A Dmscc.txt14 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:
/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-meh/
H A Dpython3-meh_0.52.bb1 SUMMARY = "A python library for handling exceptions"
2 DESCRIPTION = "The python-meh package is a python library for handling, saving, and reporting \
/openbmc/linux/Documentation/core-api/
H A Dentry.rst1 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 Dgenericirq.rst4 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/linux/drivers/staging/media/imx/
H A DTODO11 - Similarly to the legacy control handling, legacy format handling where
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/libbpf/
H A Dlibbpf_1.4.6.bb
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/tipcutils/tipcutils/
H A D0001-test-ptts-Set-recv-buffer-size-too-max-to-receive-as.patch10 "Ignoring premature msg 16, currently handling 12"
34 - dbg1("Ignoring premature msg %u, currently handling %u\n",
36 + dbg1("Ignoring premature msg %u, currently handling %u\n"
/openbmc/openbmc/poky/meta/recipes-extended/unzip/unzip/
H A DCVE-2019-13232_p1.patch24 - * (single exception: see read_byte()'s "G.csize <= 0" handling) !!
25 + * (single exception: see readbyte()'s "G.csize <= 0" handling) !!
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-crypto/pkcs11-helper/
H A Dpkcs11-helper_1.30.0.bb5 certificates, or selecting a certificate directly by serialized id, handling \
6 card removal and card insert events, handling card ie-insert to a different \
/openbmc/linux/arch/mips/sgi-ip22/
H A DPlatform6 # 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.
/openbmc/openpower-hw-diags/attn/
H A DAttention_Handler.md21 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/openbmc/meta-openembedded/meta-perl/recipes-perl/liberror/
H A Dliberror-perl_0.17029.bb1 SUMMARY = "Error - Error/exception handling in an OO-ish way"
3 Error provides a procedural interface to exception handling. \
/openbmc/ipmitool/control/
H A Dipmitool.spec.in75 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/linux/Documentation/arch/arm/vfp/
H A Drelease-notes.rst35 - fadd/fsub shows some differences in the handling of +0 / -0 results
37 - the handling of underflow exceptions is slightly different. If a

12345678910>>...33