Home
last modified time | relevance | path

Searched refs:reset (Results 1 – 25 of 3290) sorted by relevance

12345678910>>...132

/Linux-v6.1/drivers/misc/habanalabs/include/gaudi2/
Dgaudi2_async_ids_map_extended.h21 int reset; member
27 .msg = 0, .reset = 0, .name = "" },
29 .msg = 0, .reset = 0, .name = "" },
31 .msg = 0, .reset = 0, .name = "" },
33 .msg = 0, .reset = 0, .name = "" },
35 .msg = 0, .reset = 0, .name = "" },
37 .msg = 0, .reset = 0, .name = "" },
39 .msg = 0, .reset = 0, .name = "" },
41 .msg = 0, .reset = 0, .name = "" },
43 .msg = 0, .reset = 0, .name = "" },
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/reset/
Dzynq-reset.txt8 - 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 …]
Dreset.txt3 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 …]
Dti-syscon-reset.txt4 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 exposed to
33 Cell #1 : offset of the reset assert control
35 Cell #2 : bit position of the reset in the reset
[all …]
Dsnps,hsdk-reset.txt1 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 …]
Dxlnx,zynqmp-reset.txt2 = 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 …]
Dimg,pistachio-reset.txt4 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 …]
Dsnps,dw-reset.txt4 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>;
Doxnas,reset.txt4 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>;
/Linux-v6.1/drivers/reset/
DMakefile6 obj-$(CONFIG_RESET_A10SR) += reset-a10sr.o
7 obj-$(CONFIG_RESET_ATH79) += reset-ath79.o
8 obj-$(CONFIG_RESET_AXS10X) += reset-axs10x.o
9 obj-$(CONFIG_RESET_BCM6345) += reset-bcm6345.o
10 obj-$(CONFIG_RESET_BERLIN) += reset-berlin.o
11 obj-$(CONFIG_RESET_BRCMSTB) += reset-brcmstb.o
12 obj-$(CONFIG_RESET_BRCMSTB_RESCAL) += reset-brcmstb-rescal.o
13 obj-$(CONFIG_RESET_HSDK) += reset-hsdk.o
14 obj-$(CONFIG_RESET_IMX7) += reset-imx7.o
15 obj-$(CONFIG_RESET_INTEL_GW) += reset-intel-gw.o
[all …]
Dreset-sunplus.c115 struct sp_reset *reset = to_sp_reset(rcdev); in sp_reset_update() local
121 writel(val, reset->base + (index * 4)); in sp_reset_update()
141 struct sp_reset *reset = to_sp_reset(rcdev); in sp_reset_status() local
146 reg = readl(reset->base + (index * 4)); in sp_reset_status()
160 struct sp_reset *reset = container_of(nb, struct sp_reset, notifier); in sp_restart() local
162 sp_reset_assert(&reset->rcdev, 0); in sp_restart()
163 sp_reset_deassert(&reset->rcdev, 0); in sp_restart()
171 struct sp_reset *reset; in sp_reset_probe() local
175 reset = devm_kzalloc(dev, sizeof(*reset), GFP_KERNEL); in sp_reset_probe()
176 if (!reset) in sp_reset_probe()
[all …]
DKconfig11 This framework is designed to abstract reset handling of devices
12 via GPIOs or SoC-internal reset controller modules.
22 This option enables support for the external reset functions for
29 This enables the ATH79 reset controller driver that supports the
30 AR71xx SoC reset controller.
36 This enables the reset controller driver for AXS10x.
43 This enables the reset controller driver for BCM6345 SoCs.
50 This enables the reset controller driver for Marvell Berlin SoCs.
53 tristate "Broadcom STB reset controller"
57 This enables the reset controller driver for Broadcom STB SoCs using
[all …]
/Linux-v6.1/drivers/power/reset/
Dat91-reset.c117 struct at91_reset *reset = container_of(this, struct at91_reset, nb); in at91_reset() local
140 : "r" (reset->ramc_base[0]), in at91_reset()
141 "r" (reset->ramc_base[1]), in at91_reset()
142 "r" (reset->rstc_base), in at91_reset()
145 "r" (reset->data->reset_args), in at91_reset()
146 "r" (reset->ramc_lpr) in at91_reset()
250 struct at91_reset *reset = to_at91_reset(rcdev); in at91_reset_update() local
254 spin_lock_irqsave(&reset->lock, flags); in at91_reset_update()
255 val = readl_relaxed(reset->dev_base); in at91_reset_update()
260 writel_relaxed(val, reset->dev_base); in at91_reset_update()
[all …]
/Linux-v6.1/Documentation/driver-api/
Dreset.rst10 Reset controllers are central units that control the reset signals to multiple
12 The reset controller API is split into two parts:
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
15 over their reset input signals, and the `reset controller driver interface
16 <#reset-controller-driver-interface>`__ (`API reference
17 <#reset-controller-driver-api>`__), which is used by drivers for reset
18 controller devices to register their reset controls to provide them to the
21 While some reset controller hardware units also implement system restart
22 functionality, restart handlers are out of scope for the reset controller API.
27 The reset controller API uses these terms with a specific meaning:
[all …]
/Linux-v6.1/drivers/clk/visconti/
Dreset.c25 struct visconti_reset *reset = to_visconti_reset(rcdev); in visconti_reset_assert() local
26 const struct visconti_reset_data *data = &reset->resets[id]; in visconti_reset_assert()
31 spin_lock_irqsave(reset->lock, flags); in visconti_reset_assert()
32 ret = regmap_update_bits(reset->regmap, data->rson_offset, rst, rst); in visconti_reset_assert()
33 spin_unlock_irqrestore(reset->lock, flags); in visconti_reset_assert()
40 struct visconti_reset *reset = to_visconti_reset(rcdev); in visconti_reset_deassert() local
41 const struct visconti_reset_data *data = &reset->resets[id]; in visconti_reset_deassert()
46 spin_lock_irqsave(reset->lock, flags); in visconti_reset_deassert()
47 ret = regmap_update_bits(reset->regmap, data->rsoff_offset, rst, rst); in visconti_reset_deassert()
48 spin_unlock_irqrestore(reset->lock, flags); in visconti_reset_deassert()
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/power/reset/
Dkeystone-reset.txt1 * 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 …]
Docelot-reset.txt1 Microsemi Ocelot reset controller
3 The DEVCPU_GCB:CHIP_REGS have a SOFT_RST register that can be used to reset the
6 The reset registers are both present in the MSCC vcoreiii MIPS and
11 - compatible: "mscc,ocelot-chip-reset", "mscc,luton-chip-reset",
12 "mscc,jaguar2-chip-reset" or "microchip,sparx5-chip-reset"
15 reset@1070008 {
16 compatible = "mscc,ocelot-chip-reset";
/Linux-v6.1/arch/arm64/boot/dts/apple/
Dt8103-pmgr.dtsi14 #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 …]
/Linux-v6.1/drivers/soc/ti/
Domap_prm.c723 static bool _is_valid_reset(struct omap_reset_data *reset, unsigned long id) in _is_valid_reset() argument
725 if (reset->mask & BIT(id)) in _is_valid_reset()
731 static int omap_reset_get_st_bit(struct omap_reset_data *reset, in omap_reset_get_st_bit() argument
734 const struct omap_rst_map *map = reset->prm->data->rstmap; in omap_reset_get_st_bit()
749 struct omap_reset_data *reset = to_omap_reset_data(rcdev); in omap_reset_status() local
751 int st_bit = omap_reset_get_st_bit(reset, id); in omap_reset_status()
752 bool has_rstst = reset->prm->data->rstst || in omap_reset_status()
753 (reset->prm->data->flags & OMAP_PRM_HAS_RSTST); in omap_reset_status()
760 v = readl_relaxed(reset->prm->base + reset->prm->data->rstctrl); in omap_reset_status()
768 v = readl_relaxed(reset->prm->base + reset->prm->data->rstst); in omap_reset_status()
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/power/
Damlogic,meson-gx-pwrc.txt24 - 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 …]
/Linux-v6.1/drivers/clk/actions/
Dowl-reset.c17 struct owl_reset *reset = to_owl_reset(rcdev); in owl_reset_assert() local
18 const struct owl_reset_map *map = &reset->reset_map[id]; in owl_reset_assert()
20 return regmap_update_bits(reset->regmap, map->reg, map->bit, 0); in owl_reset_assert()
26 struct owl_reset *reset = to_owl_reset(rcdev); in owl_reset_deassert() local
27 const struct owl_reset_map *map = &reset->reset_map[id]; in owl_reset_deassert()
29 return regmap_update_bits(reset->regmap, map->reg, map->bit, map->bit); in owl_reset_deassert()
45 struct owl_reset *reset = to_owl_reset(rcdev); in owl_reset_status() local
46 const struct owl_reset_map *map = &reset->reset_map[id]; in owl_reset_status()
50 ret = regmap_read(reset->regmap, map->reg, &reg); in owl_reset_status()
64 .reset = owl_reset_reset,
/Linux-v6.1/arch/arm/boot/dts/
Dmeson8m2.dtsi36 resets = <&reset RESET_ETHERNET>;
37 reset-names = "stmmaceth";
66 resets = <&reset RESET_DBLK>,
67 <&reset RESET_PIC_DC>,
68 <&reset RESET_HDMI_APB>,
69 <&reset RESET_HDMI_SYSTEM_RESET>,
70 <&reset RESET_VENCI>,
71 <&reset RESET_VENCP>,
72 <&reset RESET_VDAC_4>,
73 <&reset RESET_VENCL>,
[all …]
/Linux-v6.1/arch/m68k/coldfire/
DMakefile19 obj-$(CONFIG_M5206) += m5206.o intc.o reset.o
20 obj-$(CONFIG_M5206e) += m5206.o intc.o reset.o
21 obj-$(CONFIG_M520x) += m520x.o intc-simr.o reset.o
22 obj-$(CONFIG_M523x) += m523x.o dma_timer.o intc-2.o reset.o
23 obj-$(CONFIG_M5249) += m5249.o intc.o intc-5249.o reset.o
24 obj-$(CONFIG_M525x) += m525x.o intc.o intc-525x.o reset.o
25 obj-$(CONFIG_M527x) += m527x.o intc-2.o reset.o
27 obj-$(CONFIG_M528x) += m528x.o intc-2.o reset.o
28 obj-$(CONFIG_M5307) += m5307.o intc.o reset.o
29 obj-$(CONFIG_M53xx) += m53xx.o intc-simr.o reset.o
[all …]
/Linux-v6.1/drivers/gpu/drm/i915/selftests/
Digt_reset.c19 pr_debug("%s: current gpu_error=%08lx\n", __func__, gt->reset.flags); in igt_global_reset_lock()
21 while (test_and_set_bit(I915_RESET_BACKOFF, &gt->reset.flags)) in igt_global_reset_lock()
22 wait_event(gt->reset.queue, in igt_global_reset_lock()
23 !test_bit(I915_RESET_BACKOFF, &gt->reset.flags)); in igt_global_reset_lock()
27 &gt->reset.flags)) in igt_global_reset_lock()
28 wait_on_bit(&gt->reset.flags, I915_RESET_ENGINE + id, in igt_global_reset_lock()
39 clear_and_wake_up_bit(I915_RESET_ENGINE + id, &gt->reset.flags); in igt_global_reset_unlock()
41 clear_bit(I915_RESET_BACKOFF, &gt->reset.flags); in igt_global_reset_unlock()
42 wake_up_all(&gt->reset.queue); in igt_global_reset_unlock()
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-platform-intel-pmc7 reset bits. The bits are used during an Intel platform
8 manufacturing process to indicate that consequent reset
9 of the platform is a "global reset". This type of reset
13 Display global reset setting bits for PMC.
15 * bit 31 - global reset is locked
16 * bit 20 - global reset is set
19 a platform "global reset" upon consequent platform reset,
21 The "global reset bit" should be locked on a production

12345678910>>...132