Home
last modified time | relevance | path

Searched refs:signal (Results 1 – 25 of 116) sorted by relevance

12345

/u-boot/test/common/
A Devent.c26 test_state->val += data->signal; in h_adder()
34 int signal; in test_event_base() local
39 signal = 17; in test_event_base()
42 ut_assertok(event_notify(EVT_TEST, &signal, sizeof(signal))); in test_event_base()
/u-boot/doc/device-tree-bindings/reset/
A Dreset.txt8 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
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
55 reset-names: List of reset signal name strings sorted in the same order as
57 match reset signal names with reset specifiers.
66 This represents a device with a single reset signal named "reset".
[all …]
/u-boot/doc/device-tree-bindings/serial/
A Dsnps-dw-apb-uart.txt27 - dcd-override : Override the DCD modem status signal. This signal will always
30 - dsr-override : Override the DTS modem status signal. This signal will always
33 - cts-override : Override the CTS modem status signal. This signal will always
36 - ri-override : Override the RI modem status signal. This signal will always be
/u-boot/test/py/
A Du_boot_spawn.py11 import signal
57 signal.signal(signal.SIGHUP, signal.SIG_DFL)
111 self.exit_info = 'signal %d (%s)' % (signum, signal.Signals(signum).name)
/u-boot/test/py/tests/
A Dtest_sandbox_exit.py6 import signal
20 u_boot_console.kill(signal.SIGINT)
A Dtest_stackprotector.py5 import signal
/u-boot/doc/device-tree-bindings/gpio/
A Dfsl,mpc83xx-spisel-boot.txt3 Provide access to MPC83xx SPISEL_BOOT signal as a gpio to allow it to be
6 The SPISEL_BOOT signal is always an output.
A Dgpio.txt93 defined by the binding for the device. If the board inverts the signal between
95 opposite physical level than the signal at the device's pin.
97 When the device's signal polarity is configurable, the binding for the
100 a) Define a single static polarity for the signal, with the expectation that
102 that signal polarity.
114 concepts of configurable signal polarity in the device, and possible board-
115 level signal inversion.
119 b) Pick a single option for device signal polarity, and document this choice
120 in the binding. The gpio-specifier should represent the polarity of the signal
122 particular signal polarity choice. If software chooses to program the device
[all …]
/u-boot/board/buffalo/lsxl/
A Dkwbimage-lschl.cfg139 # bit7-4: 2, 2 cycles from read command to assertion of M_ODT signal
140 # bit11-8: 5, 5 cycles from read command to de-assertion of M_ODT signal
141 # bit15-12: 5, 5 cycles from read command to assertion of internal ODT signal
142 # bit19-16: 8, 8 cycles from read command to de-assertion of internal ODT signal
147 # bit3-0: 2, 2 cycles from write comand to assertion of M_ODT signal
148 # bit7-4: 5, 5 cycles from write command to de-assertion of M_ODT signal
149 # bit15-12: 5, 5 cycles from write command to assertion of internal ODT signal
150 # bit19-16: 8, 8 cycles from write command to de-assertion of internal ODT signal
A Dkwbimage-lsxhl.cfg139 # bit7-4: 2, 2 cycles from read command to assertion of M_ODT signal
140 # bit11-8: 5, 5 cycles from read command to de-assertion of M_ODT signal
141 # bit15-12: 5, 5 cycles from read command to assertion of internal ODT signal
142 # bit19-16: 8, 8 cycles from read command to de-assertion of internal ODT signal
147 # bit3-0: 2, 2 cycles from write comand to assertion of M_ODT signal
148 # bit7-4: 5, 5 cycles from write command to de-assertion of M_ODT signal
149 # bit15-12: 5, 5 cycles from write command to assertion of internal ODT signal
150 # bit19-16: 8, 8 cycles from write command to de-assertion of internal ODT signal
/u-boot/arch/arm/dts/
A Dmeson-sm1-odroid-c4.dts33 * WARNING: The USB Hub on the Odroid-C4 needs a reset signal
35 * This signal should be handled by a USB specific power sequence
A Dpx30-ringneck-haikou-u-boot.dtsi50 * The Qseven BIOS_DISABLE signal on the PX30-µQ7 keeps the on-module
51 * eMMC powered-down initially (in fact it keeps the reset signal
A Drk3399-puma-haikou-u-boot.dtsi72 * The Qseven BIOS_DISABLE signal on the RK3399-Q7 keeps the on-module
74 * reset signal asserted). BIOS_DISABLE_OVERRIDE pin allows to re-enable
A Dmeson-gxbb-odroidc2.dts41 * signal name from schematics: PWREN
46 * signal name from schematics: USB_POWER
87 * signal name from schematics: TFLASH_VDD_EN
103 * signal name from schematics: TF_3V3N_1V8_EN
255 * WARNING: The USB Hub on the Odroid-C2 needs a reset signal
257 * This signal should be handled by a USB specific power sequence
A Dstm32mp15xx-dhcom-picoitx.dtsi45 * NOTE: The USB Port on the PicoITX needs a PWR_EN signal to enable
46 * port power. This signal should be handled by USB power sequencing
A Dimx8mp-verdin-dev.dtsi43 /* Limit frequency on dev board due to long traces and bad signal integrity */
/u-boot/arch/powerpc/include/asm/
A Dsigcontext.h9 int signal; member
/u-boot/board/d-link/dns325/
A Dkwbimage.cfg128 # bit7-4: 2, 2 cycles from read command to assertion of M_ODT signal
129 # bit11-8: 5, 5 cycles from read command to de-assertion of M_ODT signal
130 # bit15-12: 5, 5 cycles from read command to assertion of internal ODT signal
131 # bit19-16: 8, 8 cycles from read command to de-assertion of internal ODT signal
135 # bit3-0: 2, 2 cycles from write comand to assertion of M_ODT signal
136 # bit7-4: 5, 5 cycles from write command to de-assertion of M_ODT signal
137 # bit15-12: 5, 5 cycles from write command to assertion of internal ODT signal
138 # bit19-16: 8, 8 cycles from write command to de-assertion of internal ODT signal
/u-boot/doc/usage/cmd/
A Dgpio.rst25 Switch the GPIO *pin* to output mode and set the signal to 1.
30 Switch the GPIO *pin* to output mode and set the signal to 0.
35 Switch the GPIO *pin* to output mode and reverse the signal state.
40 Read the signal state of the GPIO *pin* and save it in environment variable
/u-boot/doc/device-tree-bindings/thermal/
A Dti_soc_thermal.txt15 the talert signal is routed to;
22 line the tshut signal is routed to. The informed GPIO will
/u-boot/doc/device-tree-bindings/spi/
A Dspi-mcf-dspi.txt17 select and the start of clock signal, at the start of a transfer.
19 signal and deactivating chip select, at the end of a transfer.
/u-boot/doc/device-tree-bindings/net/
A Dsnps,dwc-qos-ethernet.txt25 The EQOS transmit path clock. The HW signal name is clk_tx_i.
30 The EQOS receive path clock. The HW signal name is clk_rx_i.
41 APB, AHB, AXI, etc. The HW signal name is hclk_i (AHB) or clk_csr_i (other
45 separate clock for the master and slave bus interfaces. The HW signal name
48 The PTP reference clock. The HW signal name is clk_ptp_ref_i.
85 - interrupts: Should contain the core's combined interrupt signal
91 - "eqos". The reset to the entire module. The HW signal name is hreset_n
/u-boot/doc/device-tree-bindings/memory/
A Dti,gpmc-child.yaml28 # Chip-select signal timings corresponding to GPMC_CONFIG2:
41 # ADV signal timings corresponding to GPMC_CONFIG3:
129 description: ADV signal is delayed by half GPMC clock
133 description: CS signal is delayed by half GPMC clock
149 description: OE signal is delayed by half GPMC clock
153 description: WE signal is delayed by half GPMC clock
/u-boot/doc/imx/common/
A Dimx5.txt20 This option should be enabled for boards having a SYS_ON_OFF_CTL signal
21 connected to GPIO1[23] and triggering the MAIN_PWR_ON signal like in the
/u-boot/include/
A Devent.h50 int signal; member

Completed in 32 milliseconds

12345