| /openbmc/u-boot/include/ |
| H A D | reset.h | 16 * or in response to some error condition. Reset signals are often controlled
19 * reset controllers set or clear reset signals.
22 * controller will often implement multiple separate reset signals, since the
26 * Reset consumers/clients are the HW modules affected by reset signals. This
66 * signals.
72 * the API to all the reset signals in the bulk struct.
87 * client device; each device is assumed to have n reset signals associated
89 * mapping of client device reset signal indices to provider reset signals may
95 * list of reset signals.
103 * reset_get_bulk - Get/request all reset signals of a device.
[all …]
|
| /openbmc/linux/arch/arm/mach-spear/ |
| H A D | pl080.c | 26 } signals[16] = {{0, 0}, }; variable
36 if (signals[signal].busy && in pl080_get_signal()
37 (signals[signal].val != cd->muxval)) { in pl080_get_signal()
43 if (!signals[signal].busy) { in pl080_get_signal()
56 signals[signal].busy++; in pl080_get_signal()
57 signals[signal].val = cd->muxval; in pl080_get_signal()
70 if (!signals[signal].busy) in pl080_put_signal()
73 signals[signal].busy--; in pl080_put_signal()
|
| /openbmc/linux/tools/testing/selftests/arm64/fp/ |
| H A D | README | 30 Terminated by signal 15, no error, iterations=9467, signals=1014
33 Terminated by signal 15, no error, iterations=9448, signals=1028
36 Terminated by signal 15, no error, iterations=9436, signals=1039
39 Terminated by signal 15, no error, iterations=9421, signals=1039
42 Terminated by signal 15, no error, iterations=9403, signals=1039
45 Terminated by signal 15, no error, iterations=9385, signals=1036
48 Terminated by signal 15, no error, iterations=9376, signals=1039
51 Terminated by signal 15, no error, iterations=9361, signals=1039
54 Terminated by signal 15, no error, iterations=9350, signals=1039
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Chassis/ |
| H A D | README.md | 10 following methods, signals.
17 #### signals subsubsection
26 methods, signals.
32 #### signals subsubsection
40 following methods, signals.
46 #### signals subsubsection
|
| /openbmc/linux/drivers/net/wireless/rsi/ |
| H A D | Kconfig | 3 bool "Redpine Signals Inc devices"
16 tristate "Redpine Signals Inc 91x WLAN driver support"
24 bool "Redpine Signals Inc debug support"
32 tristate "Redpine Signals SDIO bus support"
40 tristate "Redpine Signals USB bus support"
48 bool "Redpine Signals WLAN BT Coexistence support"
|
| /openbmc/u-boot/arch/arm/mach-socfpga/ |
| H A D | freeze_controller.c | 42 * and niotri signals in sys_mgr_frzctrl_freeze_req()
67 * niotri signals in sys_mgr_frzctrl_freeze_req()
76 * assert active low bhniotri & nfrzdrv signals, in sys_mgr_frzctrl_freeze_req()
78 * active high frzreg and nfrzdrv signals in sys_mgr_frzctrl_freeze_req()
92 * active high pllbiasen signals in sys_mgr_frzctrl_freeze_req()
133 * de-assert active low plniotri and niotri signals in sys_mgr_frzctrl_thaw_req()
158 * assert active high pllbiasen signals in sys_mgr_frzctrl_thaw_req()
168 * de-assert active low bhniotri signals, in sys_mgr_frzctrl_thaw_req()
185 /* de-assert active low plniotri and niotri signals */ in sys_mgr_frzctrl_thaw_req()
|
| /openbmc/phosphor-fan-presence/control/json/triggers/ |
| H A D | signal.cpp | 98 // will do nothing since signals require a group in propertiesChanged()
123 // will do nothing since signals require a group in interfacesAdded()
147 // will do nothing since signals require a group in interfacesRemoved()
172 // will do nothing since signals require a group in nameOwnerChanged()
209 "signals from service of path {}, interface {}", in nameOwnerChanged()
226 // will do nothing since signals require a group in member()
242 auto subscriber = signals.end(); in triggerSignal()
247 subscriber = signals.find(signal); in triggerSignal()
249 if (subscriber == signals.end()) in triggerSignal()
251 // Construct list of available signals in triggerSignal()
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gdb/gdb/ |
| H A D | 0006-Fix-invalid-sigprocmask-call.patch | 24 * common/signals-state-save-restore.c (save_original_signals_state):
31 gdbsupport/signals-state-save-restore.cc | 2 +-
34 diff --git a/gdbsupport/signals-state-save-restore.cc b/gdbsupport/signals-state-save-restore.cc
36 --- a/gdbsupport/signals-state-save-restore.cc
37 +++ b/gdbsupport/signals-state-save-restore.cc
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/chassis/ |
| H A D | obmc-phosphor-buttons_git.bb | 13 PACKAGECONFIG ??= "signals handler"
14 PACKAGECONFIG[signals] = ",,gpioplus nlohmann-json,"
24 SYSTEMD_SERVICE:${PN}-signals = "xyz.openbmc_project.Chassis.Buttons.service"
29 FILES:${PN}-signals = "${bindir}/buttons"
34 BUTTON_PACKAGES = "${PN}-signals ${PN}-handler"
|
| /openbmc/u-boot/drivers/reset/ |
| H A D | Kconfig | 10 controller drivers allow control over these reset signals. In some
28 Say Y if you want to control reset signals provided by system config
42 Enable support for manipulating Tegra's on-SoC reset signals via
49 Enable support for manipulating Tegra's on-SoC reset signals via IPC
72 Say Y if you want to control reset signals provided by System Control
83 though is that some reset signals, like I2C or MISC reset multiple
|
| /openbmc/linux/Documentation/trace/coresight/ |
| H A D | coresight-ect.rst | 14 individual input and output hardware signals known as triggers to and from
50 The hardware trigger signals can also be connected to non-CoreSight devices
72 capable of generating or using trigger signals.::
100 Individual trigger connection information. This describes trigger signals for
108 * ``in_types`` : functional types for in signals.
109 * ``out_signals`` : output trigger signals for this connection.
110 * ``out_types`` : functional types for out signals.
127 If a connection has zero signals in either the 'in' or 'out' triggers then
177 * ``chan_free``: Show channels with no attached signals.
185 dangerous output signals to be set.
[all …]
|
| /openbmc/linux/drivers/staging/vc04_services/vchiq-mmal/ |
| H A D | mmal-msg.h | 220 /* Signals that the current payload is the end of the stream of data */
222 /* Signals that the start of the current payload starts a frame */
224 /* Signals that the end of the current payload ends a frame */
226 /* Signals that the current payload contains only complete frames (>1) */
230 /* Signals that the current payload is a keyframe (i.e. self decodable) */
233 * Signals a discontinuity in the stream of data (e.g. after a seek).
238 * Signals a buffer containing some kind of config data for the component
242 /* Signals an encrypted payload */
244 /* Signals a buffer containing side information */
247 * Signals a buffer which is the snapshot/postview image from a stills
[all …]
|
| /openbmc/linux/Documentation/gpu/amdgpu/display/ |
| H A D | dcn-overview.rst | 67 2. Global sync signals (green): It is a set of synchronization signals composed
70 4. Sideband signals: All other signals that do not fit the previous one.
72 These signals are essential and play an important role in DCN. Nevertheless,
197 These atomic register updates are driven by global sync signals in DCN. In
199 signals page flip and vblank events it is helpful to understand how global sync
202 Global sync consists of three signals, VSTARTUP, VUPDATE, and VREADY. These are
206 The global sync signals always happen during VBlank, are independent from the
210 or userspace clients as it signals the point at which hardware latches to
218 The below picture illustrates the global sync signals:
222 These signals affect core DCN behavior. Programming them incorrectly will lead
|
| /openbmc/phosphor-host-ipmid/libipmid/ |
| H A D | signals.cpp | 82 std::vector<std::unique_ptr<SignalHandler>> signals; variable
94 if (signals.empty()) in registerSignalHandler()
96 signals.resize(SIGRTMAX); in registerSignalHandler()
99 if (!signals[signalNumber]) in registerSignalHandler()
102 signals[signalNumber] = in registerSignalHandler()
105 signals[signalNumber]->registerHandler(priority, handler); in registerSignalHandler()
|
| /openbmc/qemu/tests/tcg/s390x/ |
| H A D | Makefile.target | 27 TESTS+=signals-s390x
98 run-gdbstub-signals-s390x: signals-s390x
102 --bin $< --test $(S390X_SRC)/gdbstub/test-signals-s390x.py, \
103 mixing signals and debugging)
114 EXTRA_RUNS += run-gdbstub-signals-s390x run-gdbstub-svc
|
| /openbmc/linux/arch/mips/include/asm/mach-rc32434/ |
| H A D | gpio.h | 39 /* UART GPIO signals */
45 /* M & P bus GPIO signals */
51 /* CPU GPIO signals */
54 /* Reserved GPIO signals */
63 /* NAND GPIO signals */
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 10 read/write the value of, numerous GPIO signals. Routing of GPIO signals to
24 b) GPIO registers, which allow manipulation of the GPIO signals. In some GPIO
48 Each GPIO controller can generate a number of interrupt signals. Each signal
50 number of interrupt signals generated by a controller varies as a rough function
54 Each GPIO controller in fact generates multiple interrupts signals for each set
56 interrupt signals generated by a set-of-ports. The intent is for each generated
59 per-port-set signals is reported via a separate register. Thus, a driver needs
|
| /openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | panel-common.yaml | 96 # and timing of those control signals are device-specific and left for panel
98 # used for panels that implement compatible control signals.
107 signals (or active high power down signals) can be supported by inverting
118 while active. Active high reset signals can be supported by inverting the
125 The tearing effect signal is active high. Active low signals can be
143 # backlight control through GPIO, PWM or other signals connected to an external
|
| /openbmc/sdeventplus/example/ |
| H A D | follow.cpp | 76 // Block all signals before changing system state so we guarantee our clean in main()
78 sigset_t signals; in main() local
79 if (sigfillset(&signals)) in main()
81 fprintf(stderr, "Failed to populate signals: %s\n", strerror(errno)); in main()
84 if (sigprocmask(SIG_BLOCK, &signals, nullptr)) in main()
86 fprintf(stderr, "Failed to mask signals: %s\n", strerror(errno)); in main()
|
| /openbmc/sdbusplus/tools/sdbusplus/templates/ |
| H A D | interface.md.mako | 25 ${"##"} Signals
26 % if len(interface.signals):
27 % for s in interface.signals:
31 No signals.
|
| /openbmc/linux/Documentation/devicetree/bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.yaml | 21 and read/write the value of, numerous GPIO signals. Routing of GPIO signals
35 b) GPIO registers, which allow manipulation of the GPIO signals. In some
60 Each GPIO controller can generate a number of interrupt signals. Each
62 ports. Thus, the number of interrupt signals generated by a controller
67 Each GPIO controller in fact generates multiple interrupts signals for
69 one of the interrupt signals generated by a set-of-ports. The intent is
72 The status of each of these per-port-set signals is reported via a
|
| /openbmc/linux/arch/um/os-Linux/ |
| H A D | signal.c | 46 /* enable signals if sig isn't IRQ signal */ in sig_handler_common()
56 * These are the asynchronous signals. SIGPROF is excluded because we want to
94 * Note we won't get here if signals are hard-blocked in sig_handler()
222 * Again, pending comes back with a mask of signals in hard_handler()
284 * This must return with signals disabled, so this barrier in block_signals()
311 * Save and reset save_pending after enabling signals. This in unblock_signals()
326 * We have pending interrupts, so disable signals, as the in unblock_signals()
331 * pending signals will mess up the tracing state. in unblock_signals()
357 /* Re-enable signals and trace that we're doing so. */ in unblock_signals()
421 panic("unblocking signals while not blocked"); in unblock_signals_hard()
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/reset/ |
| H A D | reset.txt | 3 This binding is intended to represent the hardware reset signals present
4 internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole
24 may be reset. Instead, reset signals should be represented in the DT node
27 block node for dedicated reset signals. The intent of this binding is to give
28 appropriate software access to the reset signals in order to manage the HW,
|
| /openbmc/linux/Documentation/devicetree/bindings/reset/ |
| H A D | reset.txt | 3 This binding is intended to represent the hardware reset signals present
4 internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole
24 may be reset. Instead, reset signals should be represented in the DT node
27 block node for dedicated reset signals. The intent of this binding is to give
28 appropriate software access to the reset signals in order to manage the HW,
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ |
| H A D | arm,coresight-cti.yaml | 19 output hardware trigger signals. CTIs can have a maximum number of input and
20 output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
30 In general the connections between CTI and components via the trigger signals
40 binding can be declared with no explicit trigger signals. This will result
57 signals to GEN_IO.
59 Note that some hardware trigger signals can be connected to non-CoreSight
134 A trigger connections child node which describes the trigger signals
157 signals. Types in this array match to the corresponding signal in the
174 signals. Types in this array match to the corresponding signal
183 List of CTI trigger out signals that will be blocked from becoming
|