/Linux-v5.15/drivers/gpu/drm/amd/display/include/ |
D | signal_types.h | 29 /* Minimum pixel clock, in KHz. For TMDS signal is 25.00 MHz */ 31 /* Maximum pixel clock, in KHz. For TMDS signal is 165.00 MHz */ 35 SIGNAL_TYPE_NONE = 0L, /* no signal */ 47 /* help functions for signal types manipulation */ 48 static inline bool dc_is_hdmi_tmds_signal(enum signal_type signal) in dc_is_hdmi_tmds_signal() argument 50 return (signal == SIGNAL_TYPE_HDMI_TYPE_A); in dc_is_hdmi_tmds_signal() 53 static inline bool dc_is_hdmi_signal(enum signal_type signal) in dc_is_hdmi_signal() argument 55 return (signal == SIGNAL_TYPE_HDMI_TYPE_A); in dc_is_hdmi_signal() 58 static inline bool dc_is_dp_sst_signal(enum signal_type signal) in dc_is_dp_sst_signal() argument 60 return (signal == SIGNAL_TYPE_DISPLAY_PORT || in dc_is_dp_sst_signal() [all …]
|
/Linux-v5.15/Documentation/driver-api/ |
D | generic-counter.rst | 29 * Signal: 33 Association of a Signal, and evaluation trigger, with a Count. 38 SIGNAL section in Theory 40 A Signal represents a stream of data. This is the input data that is 42 signal output line of a rotary encoder. Not all counter devices provide 43 user access to the Signal data, so exposure is optional for drivers. 45 When the Signal data is available for user access, the Generic Counter 46 interface provides the following available signal values: 49 Signal line is in a low state. 52 Signal line is in a high state. [all …]
|
/Linux-v5.15/drivers/misc/echo/ |
D | echo.h | 31 adequately cover the duration of that impulse response. The signal transmitted 33 properly adapted, the resulting output is an estimate of the echo signal 34 received from the line. This is subtracted from the received signal. The result 35 is an estimate of the signal which originated at the far end of the line, free 36 from echos of our own transmitted signal. 42 very poorly for things like speech echo cancellation, where the signal level 43 varies widely. This is quite easy to fix. If the signal level is normalised - 44 similar to applying AGC - LMS can work as well for a signal of varying 45 amplitude as it does for a modem signal. This normalised least mean squares 52 to adapt best to the strongest parts of a signal. If the signal is white noise, [all …]
|
/Linux-v5.15/drivers/gpu/drm/etnaviv/ |
D | etnaviv_perfmon.c | 20 const struct etnaviv_pm_signal *signal); 31 const struct etnaviv_pm_signal *signal; member 42 const struct etnaviv_pm_signal *signal) in perf_reg_read() argument 44 gpu_write(gpu, domain->profile_config, signal->data); in perf_reg_read() 59 const struct etnaviv_pm_signal *signal) in pipe_perf_reg_read() argument 67 value += perf_reg_read(gpu, domain, signal); in pipe_perf_reg_read() 78 const struct etnaviv_pm_signal *signal) in pipe_reg_read() argument 86 value += gpu_read(gpu, signal->data); in pipe_reg_read() 97 const struct etnaviv_pm_signal *signal) in hi_total_cycle_read() argument 111 const struct etnaviv_pm_signal *signal) in hi_total_idle_cycle_read() argument [all …]
|
/Linux-v5.15/drivers/pinctrl/aspeed/ |
D | pinmux-aspeed.h | 12 * basis where a given pin can provide a number of different signal types. 14 * The signal active on a pin is described by both a priority level and 18 * change from a high to low priority signal), or even in the same register. 28 * corner. The signal priorities are in decending order from P0 (highest). 30 * D6 is a pin with a single function (beside GPIO); a high priority signal 33 * Ball | Default | P0 Signal | P0 Expression | P1 Signal | P1 Expression | Other 38 * C5 is a multi-signal pin (high and low priority signals). Here we touch 39 * different registers for the different functions that enable each signal: 45 * E19 is a single-signal pin with two functions that influence the active 46 * signal. In this case both bits have the same meaning - enable a dedicated [all …]
|
D | pinctrl-aspeed.c | 79 pr_debug("Enabling signal %s for %s\n", expr->signal, in aspeed_sig_expr_enable() 97 pr_debug("Disabling signal %s for %s\n", expr->signal, in aspeed_sig_expr_disable() 111 * aspeed_disable_sig() - Disable a signal on a pin by disabling all provided 112 * signal expressions. 115 * @exprs: The list of signal expressions (from a priority level on a pin) 136 * aspeed_find_expr_by_name - Search for the signal expression needed to 137 * enable the pin's signal for the requested function. 139 * @exprs: List of signal expressions (haystack) 142 * Return: A pointer to the signal expression whose function tag matches the 214 return expr->signal; in aspeed_sig_expr_signal() [all …]
|
/Linux-v5.15/arch/arm/mach-spear/ |
D | pl080.c | 32 unsigned int signal = cd->min_signal, val; in pl080_get_signal() local 37 /* Return if signal is already acquired by somebody else */ in pl080_get_signal() 38 if (signals[signal].busy && in pl080_get_signal() 39 (signals[signal].val != cd->muxval)) { in pl080_get_signal() 45 if (!signals[signal].busy) { in pl080_get_signal() 51 * value by 2 * signal number. in pl080_get_signal() 53 val &= ~(0x3 << (signal * 2)); in pl080_get_signal() 54 val |= cd->muxval << (signal * 2); in pl080_get_signal() 58 signals[signal].busy++; in pl080_get_signal() 59 signals[signal].val = cd->muxval; in pl080_get_signal() [all …]
|
/Linux-v5.15/Documentation/devicetree/bindings/leds/ |
D | leds-bcm6328.txt | 14 should be controlled by a hardware signal instead of the MODE register value, 18 explained later in brcm,link-signal-sources). Even if a LED is hardware 34 - brcm,serial-clk-low : Boolean, makes clock signal active low. 36 - brcm,serial-dat-low : Boolean, makes data signal active low. 59 - brcm,link-signal-sources : An array of hardware link 60 signal sources. Up to four link hardware signals can get muxed into 63 4 to 7. A signal can be muxed to more than one LED, and one LED can 64 have more than one source signal. 65 - brcm,activity-signal-sources : An array of hardware activity 66 signal sources. Up to four activity hardware signals can get muxed into [all …]
|
/Linux-v5.15/Documentation/devicetree/bindings/reset/ |
D | reset.txt | 1 = Reset Signal Device Tree Bindings = 8 Hardware blocks typically receive a reset signal. This signal is generated by 14 A reset signal is represented by the phandle of the provider, plus a reset 15 specifier - a list of DT cells that represents the reset signal within the 20 A word on where to place reset signal consumers in device tree: It is possible 21 in hardware for a reset signal to affect multiple logically separate HW blocks 22 at once. In this case, it would be unwise to represent this reset signal in 26 children of the bus are affected by the reset signal, or an individual HW 29 rather than to slavishly enumerate the reset signal that affects each HW 49 for each reset signal that affects the device, or that the [all …]
|
/Linux-v5.15/tools/testing/selftests/net/mptcp/ |
D | mptcp_join.sh | 338 ip netns exec $ns1 ./pm_nl_ctl add $addr flags signal 998 ip netns exec $ns1 ./pm_nl_ctl add 10.0.2.1 flags signal 1000 chk_join_nr "unused signal address" 0 0 0 1007 ip netns exec $ns1 ./pm_nl_ctl add 10.0.2.1 flags signal 1009 chk_join_nr "signal address" 1 1 1 1013 # note: signal address in server ns and local addresses in client ns must 1017 ip netns exec $ns1 ./pm_nl_ctl add 10.0.2.1 flags signal 1022 chk_join_nr "subflow and signal" 2 2 2 1028 ip netns exec $ns1 ./pm_nl_ctl add 10.0.2.1 flags signal 1033 chk_join_nr "multiple subflows and signal" 3 3 3 [all …]
|
D | pm_netlink.sh | 77 ip netns exec $ns1 ./pm_nl_ctl add 10.0.1.3 flags signal,backup 83 id 3 flags signal,backup 10.0.1.3" "dump addrs" 89 id 3 flags signal,backup 10.0.1.3" "dump addrs after del" 94 ip netns exec $ns1 ./pm_nl_ctl add 10.0.1.4 flags signal 95 check "ip netns exec $ns1 ./pm_nl_ctl get 4" "id 4 flags signal 10.0.1.4" "id addr increment" 98 ip netns exec $ns1 ./pm_nl_ctl add 10.0.1.$i flags signal >/dev/null 2>&1 100 check "ip netns exec $ns1 ./pm_nl_ctl get 9" "id 9 flags signal 10.0.1.9" "hard addr limit" 109 id 3 flags signal,backup 10.0.1.3 110 id 4 flags signal 10.0.1.4 111 id 5 flags signal 10.0.1.5 [all …]
|
/Linux-v5.15/drivers/tty/ |
D | tty_jobctrl.c | 8 #include <linux/signal.h> 9 #include <linux/sched/signal.h> 25 * @sig: signal to send 28 * not in the foreground, send a SIGTTOU. If the signal is blocked or 39 if (current->signal->tty != tty) in __tty_check_change() 81 tty = p->signal->tty; in proc_clear_tty() 82 p->signal->tty = NULL; in proc_clear_tty() 112 if (current->signal->tty) { in __proc_set_tty() 114 current->signal->tty->name); in __proc_set_tty() 115 tty_kref_put(current->signal->tty); in __proc_set_tty() [all …]
|
/Linux-v5.15/tools/testing/selftests/powerpc/tm/ |
D | Makefile | 2 SIGNAL_CONTEXT_CHK_TESTS := tm-signal-context-chk-gpr tm-signal-context-chk-fpu \ 3 tm-signal-context-chk-vmx tm-signal-context-chk-vsx 5 TEST_GEN_PROGS := tm-resched-dscr tm-syscall tm-signal-msr-resv tm-signal-stack \ 7 $(SIGNAL_CONTEXT_CHK_TESTS) tm-sigreturn tm-signal-sigreturn-nt \ 8 tm-signal-context-force-tm tm-poison tm-signal-pagefault 26 $(OUTPUT)/tm-signal-context-force-tm: CFLAGS += -pthread -m64 27 $(OUTPUT)/tm-signal-pagefault: CFLAGS += -pthread -m64 31 $(SIGNAL_CONTEXT_CHK_TESTS): tm-signal.S
|
D | .gitignore | 4 tm-signal-msr-resv 5 tm-signal-stack 11 tm-signal-context-chk-fpu 12 tm-signal-context-chk-gpr 13 tm-signal-context-chk-vmx 14 tm-signal-context-chk-vsx 15 tm-signal-context-force-tm 16 tm-signal-sigreturn-nt 17 tm-signal-pagefault
|
D | tm-signal-context-force-tm.c | 5 * This test raises a SIGUSR1 signal, and toggle the MSR[TS] 6 * fields at the signal handler. With MSR[TS] being set, the kernel will 12 * saved prior to the signal being raised, and it is restored when there is 22 #include <signal.h> 47 /* count is changed in the signal handler, so it must be volatile */ 56 * Allocating memory in a signal handler, and never freeing it on in usr_signal_handler() 82 * A fork inside a signal handler seems to be more efficient than a in usr_signal_handler() 83 * fork() prior to the signal being raised. in usr_signal_handler() 126 /* Allocated an alternative signal stack area */ in tm_trap_test() 145 * the signal is raised. in tm_trap_test() [all …]
|
/Linux-v5.15/Documentation/ABI/testing/ |
D | sysfs-bus-counter | 118 Rising edges on signal A updates the respective count. 119 The input level of signal B determines direction. 123 signal A updates the respective count; if the direction 124 is backward, falling edges on quadrature pair signal A 130 signal B updates the respective count; if the direction 131 is backward, falling edges on quadrature pair signal B 136 Any state transition on quadrature pair signal A updates 141 Any state transition on quadrature pair signal B updates 187 Action mode of Count Y for Signal Z. This attribute indicates 188 the condition of Signal Z that triggers the count function [all …]
|
/Linux-v5.15/kernel/ |
D | signal.c | 3 * linux/kernel/signal.c 32 #include <linux/signal.h> 50 #include <trace/events/signal.h> 60 * SLAB caches for signal bits. 89 if (unlikely(t->signal->flags & SIGNAL_UNKILLABLE) && in sig_task_ignored() 105 * signal handler may change by the time it is in sig_ignored() 112 * Tracers may want to know about even ignored signal unless it in sig_ignored() 126 static inline bool has_pending_signals(sigset_t *signal, sigset_t *blocked) in has_pending_signals() argument 134 ready |= signal->sig[i] &~ blocked->sig[i]; in has_pending_signals() 137 case 4: ready = signal->sig[3] &~ blocked->sig[3]; in has_pending_signals() [all …]
|
/Linux-v5.15/tools/testing/selftests/arm64/signal/ |
D | README | 1 KSelfTest arm64/signal/ 9 signal-test (setup/trigger/run/result/cleanup) 14 - Each signal testcase is compiled into its own executable: a separate 16 by receiving some kind of fatal signal from the Kernel, so it's safer 27 - 'mangle_' tests: a real signal (SIGUSR1) is raised and used as a trigger 28 and then the test case code modifies the signal frame from inside the 29 signal handler itself. 33 real signal return. This kind of tests does not use a trigger usually and 37 some fatal signal: usually SIGSEGV or SIGBUS. Since while writing this 57 - some fatal signal sent by the Kernel to the test process
|
/Linux-v5.15/Documentation/driver-api/gpio/ |
D | intro.rst | 30 digital signal. They are provided from many kinds of chips, and are familiar 83 It is natural to assume that a GPIO is "active" when its output signal is 1 84 ("high"), and inactive when it is 0 ("low"). However in practice the signal of a 89 means "active") so that drivers only need to worry about the logical signal and 94 Sometimes shared signals need to use "open drain" (where only the low signal 95 level is actually driven), or "open source" (where only the high signal level is 97 used for TTL. A pullup or pulldown resistor causes the high or low signal level. 101 One common example of an open drain signal is a shared active-low IRQ line. 109 **LOW**: ``gpiod_direction_output(gpio, 0)`` ... this drives the signal and 113 the pullup (or some other device) controls the signal. [all …]
|
/Linux-v5.15/Documentation/devicetree/bindings/display/panel/ |
D | panel-common.yaml | 84 (hot plug detect) signal, but the signal isn't hooked up so we should 103 Specifier for a GPIO connected to the panel enable control signal. The 104 enable signal is active high and enables operation of the panel. This 106 signal, which is a negated version of the enable signal. Active low enable 110 Note that the enable signal control panel operation only and must not be 111 confused with a backlight enable signal. 116 Specifier for a GPIO connected to the panel reset control signal. 117 The reset signal is active low and resets the panel internal logic 124 GPIO spec for the tearing effect synchronization signal. 125 The tearing effect signal is active high. Active low signals can be
|
/Linux-v5.15/Documentation/devicetree/bindings/sound/ |
D | cs35l35.txt | 26 - cirrus,audio-channel : Set Location of Audio Signal on Serial Port 30 - cirrus,advisory-channel : Set Location of Advisory Signal on Serial Port 34 - cirrus,shared-boost : Boolean to enable ClassH tracking of Advisory Signal 105 Optional Monitor Signal Format sub-node: 107 The cs35l35 node can have a single "cirrus,monitor-signal-format" sub-node 113 -cirrus,monitor-signal-format : Sub-node for the Monitor Signaling Formating 120 for each monitoring signal. 123 scale of the IMON monitor signal. 126 of the VMON monitor signal. 129 of the VPMON monitor signal. [all …]
|
/Linux-v5.15/scripts/kconfig/ |
D | gconf.glade | 20 <signal name="destroy" handler="on_window1_destroy" object="window1"/> 21 …<signal name="size_request" handler="on_window1_size_request" object="vpaned1" last_modification_t… 22 …<signal name="delete_event" handler="on_window1_delete_event" object="window1" last_modification_t… 49 <signal name="activate" handler="on_load1_activate"/> 50 <accelerator key="L" modifiers="GDK_CONTROL_MASK" signal="activate"/> 72 <signal name="activate" handler="on_save_activate"/> 73 <accelerator key="S" modifiers="GDK_CONTROL_MASK" signal="activate"/> 95 <signal name="activate" handler="on_save_as1_activate"/> 122 <signal name="activate" handler="on_quit1_activate"/> 123 <accelerator key="Q" modifiers="GDK_CONTROL_MASK" signal="activate"/> [all …]
|
/Linux-v5.15/tools/perf/Documentation/ |
D | perf-daemon.txt | 17 'perf daemon signal' [<options>] 80 SIGNAL COMMAND 82 The signal command sends signal to configured sessions. 85 Send signal to specific session. 177 Send USR2 signal to session 'cycles' to generate perf.data file: 179 # perf daemon signal --session cycles 180 signal 12 sent to session 'cycles [603452]' 187 Send USR2 signal to all sessions: 189 # perf daemon signal 190 signal 12 sent to session 'cycles [603452]' [all …]
|
/Linux-v5.15/include/linux/sched/ |
D | signal.h | 6 #include <linux/signal.h> 17 * Types defining task->signal and task->sighand and APIs using them: 71 sigset_t signal; member 90 /* current thread group signal load-balancing target: */ 93 /* shared signal handling: */ 103 * - everyone except group_exit_task is stopped during signal delivery 104 * of fatal signals, group_exit_task processes the signal. 362 * TIF_NOTIFY_SIGNAL isn't really a signal, but it requires the same in signal_pending() 364 * so that notify signal callbacks can be processed. in signal_pending() 373 return unlikely(sigismember(&p->pending.signal, SIGKILL)); in __fatal_signal_pending() [all …]
|
/Linux-v5.15/Documentation/userspace-api/media/v4l/ |
D | ext-ctrls-rf-tuner.rst | 14 converts that received signal to lower intermediate frequency (IF) or 43 Filter(s) on tuner signal path are used to filter signal according 59 The RF amplifier is the very first amplifier on the receiver signal 68 signal path. It is located very close to tuner antenna input. Used 75 Mixer gain is second gain stage on the RF tuner signal path. It is 76 located inside mixer block, where RF signal is down-converted by the 81 IF gain is last gain stage on the RF tuner signal path. It is 82 located on output of RF tuner. It controls signal level of
|