/freebsd/sys/contrib/device-tree/Bindings/reset/ |
H A D | zynq-reset.txt | 8 - compatible: "xlnx,zynq-reset" 12 - #reset-cells: Must be 1 18 compatible = "xlnx,zynq-reset"; 20 #reset-cells = <1>; 25 0 : soft reset 26 32 : ddr reset 27 64 : topsw reset 28 96 : dmac reset 29 128: usb0 reset 30 129: usb1 reset [all …]
|
H A D | reset.txt | 3 This binding is intended to represent the hardware reset signals present 8 Hardware blocks typically receive a reset signal. This signal is generated by 9 a reset provider (e.g. power management or clock module) and received by a 10 reset consumer (the module being reset, or a module managing when a sub- 11 ordinate module is reset). This binding exists to represent the provider and 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 16 provider. The length (number of cells) and semantics of the reset specifier 17 are dictated by the binding of the reset provider, although common schemes 20 A word on where to place reset signal consumers in device tree: It is possible [all …]
|
H A D | ti-syscon-reset.txt | 4 Almost all SoCs have hardware modules that require reset control in addition 5 to clock and power control for their functionality. The reset control is 13 and provides reset management functionality for various hardware modules 18 Each of the reset provider/controller nodes should be a child of a syscon 27 "ti,syscon-reset" 28 - #reset-cells : Should be 1. Please see the reset consumer node below 30 - ti,reset-bits : Contains the reset control register information 31 Should contain 7 cells for each reset expose [all...] |
H A D | fsl,imx7-src.txt | 4 Please also refer to reset.txt in this directory for common reset 17 - #reset-cells: 1, see below 21 src: reset-controller@30390000 { 25 #reset-cells = <1>; 29 Specifying reset lines connected to IP modules 32 The system reset controller can be used to reset various set of 33 peripherals. Device nodes that need access to reset lines should 34 specify them as a reset phandle in their corresponding node as 35 specified in reset.txt. 45 reset-names = "pciephy", "apps"; [all …]
|
H A D | snps,hsdk-reset.txt | 1 Binding for the Synopsys HSDK reset controller 3 This binding uses the common reset binding[1]. 5 [1] Documentation/devicetree/bindings/reset/reset.txt 8 - compatible: should be "snps,hsdk-reset". 9 - reg: should always contain 2 pairs address - length: first for reset 10 configuration register and second for corresponding SW reset and status bits 12 - #reset-cells: from common reset binding; Should always be set to 1. 15 reset: reset@880 { 16 compatible = "snps,hsdk-reset"; 17 #reset-cells = <1>; [all …]
|
H A D | xlnx,zynqmp-reset.txt | 2 = Zynq UltraScale+ MPSoC and Versal reset driver binding = 9 Please also refer to reset.txt in this directory for common reset 13 - compatible: "xlnx,zynqmp-reset" for Zynq UltraScale+ MPSoC platform 14 "xlnx,versal-reset" for Versal platform 15 - #reset-cells: Specifies the number of cells needed to encode reset 27 zynqmp_reset: reset-controller { 28 compatible = "xlnx,zynqmp-reset"; 29 #reset-cells = <1>; 34 Specifying reset lines connected to IP modules 37 Device nodes that need access to reset lines should [all …]
|
H A D | snps,axs10x-reset.txt | 1 Binding for the AXS10x reset controller 4 to control reset signals of selected peripherals. For example DW GMAC, etc... 6 represents up-to 32 reset lines. 11 This binding uses the common reset binding[1]. 13 [1] Documentation/devicetree/bindings/reset/reset.txt 16 - compatible: should be "snps,axs10x-reset". 17 - reg: should always contain pair address - length: for creg reset 19 - #reset-cells: from common reset binding; Should always be set to 1. 22 reset: reset-controller@11220 { 23 compatible = "snps,axs10x-reset"; [all …]
|
H A D | img,pistachio-reset.txt | 4 This binding describes a reset controller device that is used to enable and 5 disable individual IP blocks within the Pistachio SoC using "soft reset" 8 The actual action taken when soft reset is asserted is hardware dependent. 13 Please refer to Documentation/devicetree/bindings/reset/reset.txt 14 for common reset controller binding usage. 18 - compatible: Contains "img,pistachio-reset" 20 - #reset-cells: Contains 1 31 pistachio_reset: reset-controller { 32 compatible = "img,pistachio-reset"; 33 #reset-cells = <1>; [all …]
|
H A D | uniphier-reset.txt | 1 UniPhier glue reset controller 4 Peripheral core reset in glue layer 7 Some peripheral core reset belongs to its own glue layer. Before using 8 this core reset, it is necessary to control the clocks and resets to enable 13 "socionext,uniphier-pro4-usb3-reset" - for Pro4 SoC USB3 14 "socionext,uniphier-pro5-usb3-reset" - for Pro5 SoC USB3 15 "socionext,uniphier-pxs2-usb3-reset" - for PXs2 SoC USB3 16 "socionext,uniphier-ld20-usb3-reset" - for LD20 SoC USB3 17 "socionext,uniphier-pxs3-usb3-reset" - for PXs3 SoC USB3 18 "socionext,uniphier-pro4-ahci-reset" - for Pro4 SoC AHCI [all …]
|
H A D | brcm,brcmstb-reset.txt | 1 Broadcom STB SW_INIT-style reset controller 4 Broadcom STB SoCs have a SW_INIT-style reset controller with separate 6 reset lines. 8 Please also refer to reset.txt in this directory for common reset 12 - compatible: should be brcm,brcmstb-reset 14 - #reset-cells: must be set to 1 18 reset: reset-controller@8404318 { 19 compatible = "brcm,brcmstb-reset"; 21 #reset-cells = <1>; 25 resets = <&reset 26>; [all …]
|
H A D | hisilicon,hi3660-reset.txt | 4 Please also refer to reset.txt in this directory for common reset 7 The reset controller registers are part of the system-ctl block on 12 "hisilicon,hi3660-reset" for HI3660 13 "hisilicon,hi3670-reset", "hisilicon,hi3660-reset" for HI3670 14 - hisi,rst-syscon: phandle of the reset's syscon. 15 - #reset-cells : Specifies the number of cells needed to encode a 16 reset source. The type shall be a <u32> and the value shall be 2. 18 Cell #1 : offset of the reset assert control 22 Cell #2 : bit position of the reset in the reset control register 31 compatible = "hisilicon,hi3660-reset"; [all …]
|
H A D | nuvoton,npcm-reset.txt | 4 - compatible : "nuvoton,npcm750-reset" for NPCM7XX BMC 6 - #reset-cells: must be set to 2 9 - nuvoton,sw-reset-number - Contains the software reset number to restart the SoC. 10 NPCM7xx contain four software reset that represent numbers 1 to 4. 12 If 'nuvoton,sw-reset-number' is not specified software reset is disabled. 16 compatible = "nuvoton,npcm750-reset"; 18 #reset-cells = <2>; 19 nuvoton,sw-reset-number = <2>; 22 Specifying reset lines connected to IP NPCM7XX modules 32 The index could be found in <dt-bindings/reset/nuvoton,npcm7xx-reset.h>.
|
H A D | lantiq,reset.txt | 1 Lantiq XWAY SoC RCU reset controller binding 4 This binding describes a reset-controller found on the RCU module on Lantiq 12 "lantiq,danube-reset" 13 "lantiq,xrx200-reset" 16 - Offset of the reset set register 17 - Offset of the reset status register 18 - #reset-cells : Specifies the number of cells needed to encode the 19 reset line, should be 2. 20 The first cell takes the reset set bit and the 24 Example for the reset-controllers on the xRX200 SoCs: [all …]
|
H A D | ath79-reset.txt | 1 Binding for Qualcomm Atheros AR7xxx/AR9XXX reset controller 3 Please also refer to reset.txt in this directory for common reset 7 - compatible: has to be "qca,<soctype>-reset", "qca,ar7100-reset" 10 - #reset-cells : Specifies the number of cells needed to encode reset 15 reset-controller@1806001c { 16 compatible = "qca,ar9132-reset", "qca,ar7100-reset"; 19 #reset-cells = <1>;
|
H A D | snps,dw-reset.txt | 4 Please also refer to reset.txt in this directory for common reset 10 "snps,dw-high-reset" - for active high configuration 11 "snps,dw-low-reset" - for active low configuration 16 - #reset-cells: must be 1. 20 dw_rst_1: reset-controller@0000 { 21 compatible = "snps,dw-high-reset"; 23 #reset-cells = <1>; 26 dw_rst_2: reset-controller@1000 { 27 compatible = "snps,dw-low-reset"; 29 #reset-cells = <1>;
|
H A D | ti,sci-reset.txt | 14 This reset controller node uses the TI SCI protocol to perform the reset 20 - compatible : Should be "ti,sci-reset" 21 - #reset-cells : Should be 2. Please see the reset consumer node below for 26 Each of the reset consumer nodes should have the following properties, 31 - resets : A phandle and reset specifier pair, one pair for each reset 33 The phandle should point to the TI-SCI reset controller node, 34 and the reset specifier should have 2 cell-values. The first 36 contain the reset mask value used by system controller. 41 Please also refer to Documentation/devicetree/bindings/reset/reset.txt for 42 common reset controller usage by consumers. [all …]
|
H A D | sirf,rstc.txt | 4 Please also refer to reset.txt in this directory for common reset 11 - #reset-cells: 1, see below 15 rstc: reset-controller@88010000 { 18 #reset-cells = <1>; 21 Specifying reset lines connected to IP modules 24 The reset controller(rstc) manages various reset sources. This module provides 25 reset signals for most blocks in system. Those device nodes should specify the 26 reset line on the rstc in their resets property, containing a phandle to the 27 rstc device node and a RESET_INDEX specifying which module to reset, as described 28 in reset.txt.
|
H A D | oxnas,reset.txt | 4 Please also refer to reset.txt in this directory for common reset 8 - compatible: For OX810SE, should be "oxsemi,ox810se-reset" 9 For OX820, should be "oxsemi,ox820-reset" 10 - #reset-cells: 1, see below 19 - For OX810SE: include/dt-bindings/reset/oxsemi,ox810se.h 20 - For OX820: include/dt-bindings/reset/oxsemi,ox820.h 28 reset: reset-controller { 29 compatible = "oxsemi,ox810se-reset"; 30 #reset-cells = <1>;
|
/freebsd/sys/contrib/device-tree/Bindings/power/reset/ |
H A D | keystone-reset.txt | 1 * Device tree bindings for Texas Instruments keystone reset 3 This node is intended to allow SoC reset in case of software reset 6 The Keystone SoCs can contain up to 4 watchdog timers to reset 8 block. The Reset Mux block can be configured to cause reset or not. 10 Additionally soft or hard reset can be configured. 14 - compatible: ti,keystone-reset 18 reset control registers. 26 - ti,soft-reset: Boolean option indicating soft reset. 27 By default hard reset is used. 29 - ti,wdt-list: WDT list that can cause SoC reset. It's not related [all …]
|
/freebsd/sys/contrib/device-tree/src/arm64/apple/ |
H A D | t8103-pmgr.dtsi | 14 #reset-cells = <0>; 23 #reset-cells = <0>; 32 #reset-cells = <0>; 41 #reset-cells = <0>; 49 #reset-cells = <0>; 57 #reset-cells = <0>; 65 #reset-cells = <0>; 73 #reset-cells = <0>; 82 #reset-cells = <0>; 91 #reset-cells = <0>; [all …]
|
H A D | t8112-pmgr.dtsi | 14 #reset-cells = <0>; 23 #reset-cells = <0>; 32 #reset-cells = <0>; 41 #reset-cells = <0>; 49 #reset-cells = <0>; 57 #reset-cells = <0>; 66 #reset-cells = <0>; 75 #reset-cells = <0>; 84 #reset-cells = <0>; 93 #reset-cells = <0>; [all …]
|
H A D | t600x-pmgr.dtsi | 13 #reset-cells = <0>; 22 #reset-cells = <0>; 31 #reset-cells = <0>; 40 #reset-cells = <0>; 49 #reset-cells = <0>; 58 #reset-cells = <0>; 67 #reset-cells = <0>; 76 #reset-cells = <0>; 84 #reset-cells = <0>; 92 #reset-cells = <0>; [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/pci/ |
H A D | qcom,pcie.txt | 195 Definition: List of phandle and reset specifier pairs as listed 196 in reset-names property 198 - reset-names: 202 - "axi" AXI reset 203 - "ahb" AHB reset 204 - "por" POR reset 205 - "pci" PCI reset 206 - "phy" PHY reset 208 - reset-names: 212 - "core" Core reset [all …]
|
/freebsd/contrib/llvm-project/lldb/source/Target/ |
H A D | ExecutionContext.cpp | 167 m_target_sp.reset(); in Clear() 168 m_process_sp.reset(); in Clear() 169 m_thread_sp.reset(); in Clear() 170 m_frame_sp.reset(); in Clear() 265 m_target_sp.reset(); in SetTargetPtr() 272 m_process_sp.reset(); in SetProcessPtr() 279 m_thread_sp.reset(); in SetThreadPtr() 286 m_frame_sp.reset(); in SetFramePtr() 295 m_process_sp.reset(); in SetContext() 296 m_thread_sp.reset(); in SetContext() [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/power/ |
H A D | amlogic,meson-gx-pwrc.txt | 24 - resets: phandles to the reset lines needed for this power demain sequence 25 as described in ../reset/reset.txt 45 resets = <&reset RESET_VIU>, 46 <&reset RESET_VENC>, 47 <&reset RESET_VCBUS>, 48 <&reset RESET_BT656>, 49 <&reset RESET_DVIN_RESET>, 50 <&reset RESET_RDMA>, 51 <&reset RESET_VENCI>, 52 <&reset RESET_VENCP>, [all …]
|