Searched full:signals (Results 1 – 25 of 1204) sorted by relevance
12345678910>>...49
16 * or in response to some error condition. Reset signals are often controlled19 * reset controllers set or clear reset signals.22 * controller will often implement multiple separate reset signals, since the26 * Reset consumers/clients are the HW modules affected by reset signals. This66 * 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 associated89 * mapping of client device reset signal indices to provider reset signals may95 * list of reset signals.103 * reset_get_bulk - Get/request all reset signals of a device.[all …]
10 following methods, signals.17 #### signals subsubsection26 methods, signals.32 #### signals subsubsection40 following methods, signals.46 #### signals subsubsection
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.cc36 --- a/gdbsupport/signals-state-save-restore.cc37 +++ b/gdbsupport/signals-state-save-restore.cc
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()
15 signals.c: In function ‘_rl_handle_signal’:16 signals.c:62:36: error: ‘return’ with a value, in function returning void [-Wreturn-mismatch]19 signals.c:290:3: note: in expansion of macro ‘SIGHANDLER_RETURN’22 signals.c:178:1: note: declared here25 signals.c: In function ‘rl_sigwinch_handler’:26 …signals.c:306:32: error: passing argument 2 of ‘rl_set_sighandler’ from incompatible pointer type …32 from signals.c:37:33 signals.c:81:51: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’54 +--- gdb-10.2/readline/readline/signals.c.orig55 ++++ gdb-10.2/readline/readline/signals.c
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"
96 // will do nothing since signals require a group in propertiesChanged()121 // will do nothing since signals require a group in interfacesAdded()145 // will do nothing since signals require a group in interfacesRemoved()170 // will do nothing since signals require a group in nameOwnerChanged()207 "signals from service of path {MEMBER}, interface {GROUP_INTERFACE}", in nameOwnerChanged()223 // will do nothing since signals require a group in member()239 auto subscriber = signals.end(); in triggerSignal()244 subscriber = signals.find(signal); in triggerSignal()246 if (subscriber == signals.end()) in triggerSignal()248 // Construct list of available signals in triggerSignal()[all …]
10 controller drivers allow control over these reset signals. In some28 Say Y if you want to control reset signals provided by system config42 Enable support for manipulating Tegra's on-SoC reset signals via49 Enable support for manipulating Tegra's on-SoC reset signals via IPC72 Say Y if you want to control reset signals provided by System Control83 though is that some reset signals, like I2C or MISC reset multiple
82 std::vector<std::unique_ptr<SignalHandler>> signals; variable94 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()
27 TESTS+=signals-s390x98 run-gdbstub-signals-s390x: signals-s390x102 --bin $< --test $(S390X_SRC)/gdbstub/test-signals-s390x.py, \103 mixing signals and debugging)114 EXTRA_RUNS += run-gdbstub-signals-s390x run-gdbstub-svc
25 ${"##"} Signals26 % if len(interface.signals):27 % for s in interface.signals:31 No signals.
76 // Block all signals before changing system state so we guarantee our clean in main()78 sigset_t signals; in main() local79 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()
10 read/write the value of, numerous GPIO signals. Routing of GPIO signals to24 b) GPIO registers, which allow manipulation of the GPIO signals. In some GPIO48 Each GPIO controller can generate a number of interrupt signals. Each signal50 number of interrupt signals generated by a controller varies as a rough function54 Each GPIO controller in fact generates multiple interrupts signals for each set56 interrupt signals generated by a set-of-ports. The intent is for each generated59 per-port-set signals is reported via a separate register. Thus, a driver needs
3 This binding is intended to represent the hardware reset signals present4 internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole24 may be reset. Instead, reset signals should be represented in the DT node27 block node for dedicated reset signals. The intent of this binding is to give28 appropriate software access to the reset signals in order to manage the HW,
2 * Emulation of BSD signals13 * block_signals: block all signals while handling this guest syscall15 * Block all signals, and arrange that the signal mask is returned to21 * emulation of the system call knowing that no signals can be taken26 * Signals will be unblocked again by process_pending_signals().