From nobody Tue Sep 29 04:12:52 2026 Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 368AD29AAEA for ; Thu, 13 Aug 2026 00:24:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.214.178 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786580652; cv=none; b=Cvj5Nj5g0v5SaRmPmVAmWMo+gpvhV4UrxvcTM6etEX9/9Va/TLy3tbZe9bZS4BfX5j/dnWBolw3vGJFXyUMPLSEynAyobJLFRzMoRmZjKIfDXknw+EIlcq2NOFHYNoWrnC4kQBZ5cPL0E9E85KmdjUyjN4oQHwd0971zc9s49Kg= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786580652; c=relaxed/simple; bh=KKhbaM4BxrQAo99VUNbaxK5TbHK9MBI5zEqik+L6/eg=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:To:Cc; b=gq791W8XXTmh/etHuS5WeKXgLn3Ypal8UNNChv8TzlCBDPLnjtDt2scB9T+qdSMd0j/GD/5a3o5ivXqtu7d+uVoqlUWA3tf1Pl/T0TigpHLPnMdVwmpwuenfKgbkpW9se+eW5iEaiC354FTOSxZAghYDgaaBA27mVIcajZnaVMY= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=oWxgwHgx; arc=none smtp.client-ip=209.85.214.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="oWxgwHgx" Received: by mail-pl1-f178.google.com with SMTP id d9443c01a7336-2d03fcd26a6so2473865ad.2 for ; Wed, 12 Aug 2026 17:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1786580650; x=1787185450; darn=vger.kernel.org; h=cc:to:message-id:content-transfer-encoding:content-type :mime-version:subject:date:from:from:to:cc:subject:date:message-id :reply-to:content-type; bh=NKCLFuxWFMT16xVoGG+Whvfm+fbrPxkhcIeAiIoBa7w=; b=oWxgwHgxCv9nonA/gPWu3q/GHr808vZFjXwYo+6c622vQzs944229HPra58SfeC58C Sih1XoepeR4ri8Fll7JR4FolkqK6ITkoerr4qsQ8StdhUx7kFuBDBBOtB1xbyLlR7Lbd Qj2tlbf4Irhcxj767QsQYX2zEpBFk7vHlPiw2/eesQ087+OmDMr4QTJmaRSksg7Y7UEi aauJVgPr67wnkNcq5TU4201Te0YMKrc3clULY6qauKku9WZaGRxkYhEbfq9wZaE3B62B +mnzL4zACIFCNoarZ4IzOovsyCVaY+zhqK5JY7xN7lEsEbS6hC710CFwQhGXj6T30D/t u94w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1786580650; x=1787185450; h=cc:to:message-id:content-transfer-encoding:content-type :mime-version:subject:date:from:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to:content-type; bh=NKCLFuxWFMT16xVoGG+Whvfm+fbrPxkhcIeAiIoBa7w=; b=i1C1cu4TxZnvcB97l/nTmqdDBRV91YaaUIlztB/j4/64Zvz8ecb8mGpCFuhA59X7eE v3Zwhj2NfDAr4hXhfDxXOZ/obqYYFYCwUKHpcDf39snfhV8X6GVIAH9X3gyEnPARBS8M E0MlMXspYcuT9m3lwLSpyZkBQm4IGxrOZIgODxoWKaMygXJCS4X2rDAH581L0SNNmv4n lWVwZwunIzhcn3jZ+5AVSCIxa0fq7NTiVT1mjBpnhwD+BEgxjJ2YbBI+HitwdTcupAZO FW3tpRI3wFYtihoQDmik9PEtHlHEjJuJq11o75/h7XVPh0B/kJFfNIG/DXhg+EzDyoDr mKxg== X-Forwarded-Encrypted: i=1; AHgh+Rp6ITynj+s5dOYuzcY2kcqmPmN4+QheuhPSbjvGCi1zAz7XLz70BtrYylN1+RCscXMC+PktCP2pUmHP/sI=@vger.kernel.org X-Gm-Message-State: AOJu0Yx4PwzR5SAohBAIKW4fKlBxGsrrdict4TlUFDPTw2UOOhsBbU8h mBViY2nYybfD/jMlVIyvbi1Xkff93FIKqzeEXLkKuHIPZcIlEjEtkUMEZYbXBg== X-Gm-Gg: AR+sD10as1LDO8HvkcOE8/pvs4QZYJ2GhcdWhhYcasa1L6FyAQt+QWF909UROSbM16J J8pZEMh9xTZumc6u49+DwcVnAVsUNkiax6m6bZ4xPEt64rYL9e3qDCF2z+UJxur9tcfyoyn7VDn mSm8VRNahQK+3M3Y6APUiwjgMuCJBEjBd9DEKH/7FR6ldczg0YAbW0+Ipuw4wrefho8wM7esA/d VmM4B0g+1yHt4DkA7fQC9BhqBmFZjUHSomGG3v9PgIJxq5a5/Cd166f1RihK2zEHTAaeANhd1ew fwTtKtrvw+qNwmxDcPQeW+xWs4CnHL3PCtf/rZyyFCqMoB7Ck5YuszQ7eLquWs0O5HOAQ0HSs09 zwiDrY9kJjMNn/z9wQAAjAHtmMSuYBzvECSlJcG+oNAx5W/Kp8OFrxsWwlwxOtJ9quh97DSL5b2 4js4H07NtoSMlveQ08dd+SyTZKsaxjFGsfQIzdWq0zt6QDGJr7T8Hb2cXS91Sm1LMJyP3UvA== X-Received: by 2002:a17:903:2c50:b0:2c9:ed4a:c3a4 with SMTP id d9443c01a7336-2d37d19f10fmr16271005ad.0.1786580650275; Wed, 12 Aug 2026 17:24:10 -0700 (PDT) Received: from [10.219.45.252] ([2409:40c2:504e:6b:b46f:70e9:d340:f24c]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-31ebc75d8casm1281289eec.3.2026.08.12.17.24.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 Aug 2026 17:24:09 -0700 (PDT) From: Bhargav Joshi Date: Thu, 13 Aug 2026 05:53:55 +0530 Subject: [PATCH] dt-bindings: power: reset: ti,keystone-reset: Convert to DT schema Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20260813-ti-keystone-reset-v1-1-189389503324@gmail.com> X-B4-Tracking: v=1; b=H4sIAAAAAAAC/6tWKk4tykwtVrJSqFYqSi3LLM7MzwNyDHUUlJIzE vPSU3UzU4B8JSMDIzMDC0Nj3ZJM3ezUyuKS/LxU3aLU4tQSXcvEJKNkC2MLQzNTQyWgvoKi1LT MCrCZ0bG1tQAIMI4MYwAAAA== X-Change-ID: 20260813-ti-keystone-reset-9ab2c8381651 To: Sebastian Reichel , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Andrew Davis Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, goledhruva@gmail.com, m-chawdhry@ti.com, daniel.baluta@gmail.com, simona.toaca@nxp.com, j.bhargav.u@gmail.com X-Mailer: b4 0.14.3 X-Developer-Signature: v=1; a=ed25519-sha256; t=1786580640; l=5960; i=j.bhargav.u@gmail.com; h=from:subject:message-id; bh=KKhbaM4BxrQAo99VUNbaxK5TbHK9MBI5zEqik+L6/eg=; b=rfvimOCvmz/n3PG+Z4uohyIHgOufEyjXp0KoHzEkCWj2NIX5R2s6a2f2YKxUyHeuQXlP+pTZC lPH/5tSSLhIB9fsXouPWuNxQi94GKXS4u6AxUL5QhbimD1uBPThRp33 X-Developer-Key: i=j.bhargav.u@gmail.com; a=ed25519; pk=IqNDwUZKECEA+n8wXctFLBbYL9NhFstZNbOznm/nX1k= Convert Texas Instruments Keystone SoC Reset Controller from text to DT schema. no new functional changes. Signed-off-by: Bhargav Joshi --- .../bindings/power/reset/keystone-reset.txt | 67 ------------------ .../bindings/power/reset/ti,keystone-reset.yaml | 81 ++++++++++++++++++= ++++ 2 files changed, 81 insertions(+), 67 deletions(-) diff --git a/Documentation/devicetree/bindings/power/reset/keystone-reset.t= xt b/Documentation/devicetree/bindings/power/reset/keystone-reset.txt deleted file mode 100644 index c5c03789ed1e..000000000000 --- a/Documentation/devicetree/bindings/power/reset/keystone-reset.txt +++ /dev/null @@ -1,67 +0,0 @@ -* Device tree bindings for Texas Instruments keystone reset - -This node is intended to allow SoC reset in case of software reset -of selected watchdogs. - -The Keystone SoCs can contain up to 4 watchdog timers to reset -SoC. Each watchdog timer event input is connected to the Reset Mux -block. The Reset Mux block can be configured to cause reset or not. - -Additionally soft or hard reset can be configured. - -Required properties: - -- compatible: ti,keystone-reset - -- ti,syscon-pll: phandle/offset pair. The phandle to syscon used to - access pll controller registers and the offset to use - reset control registers. - -- ti,syscon-dev: phandle/offset pair. The phandle to syscon used to - access device state control registers and the offset - in order to use mux block registers for all watchdogs. - -Optional properties: - -- ti,soft-reset: Boolean option indicating soft reset. - By default hard reset is used. - -- ti,wdt-list: WDT list that can cause SoC reset. It's not related - to WDT driver, it's just needed to enable a SoC related - reset that's triggered by one of WDTs. The list is - in format: <0>, <2>; It can be in random order and - begins from 0 to 3, as keystone can contain up to 4 SoC - reset watchdogs and can be in random order. - -Example 1: -Setup keystone reset so that in case software reset or -WDT0 is triggered it issues hard reset for SoC. - -pllctrl: pll-controller@2310000 { - compatible =3D "ti,keystone-pllctrl", "syscon"; - reg =3D <0x02310000 0x200>; -}; - -devctrl: device-state-control@2620000 { - compatible =3D "ti,keystone-devctrl", "syscon"; - reg =3D <0x02620000 0x1000>; -}; - -rstctrl: reset-controller { - compatible =3D "ti,keystone-reset"; - ti,syscon-pll =3D <&pllctrl 0xe4>; - ti,syscon-dev =3D <&devctrl 0x328>; - ti,wdt-list =3D <0>; -}; - -Example 2: -Setup keystone reset so that in case of software reset or -WDT0 or WDT2 is triggered it issues soft reset for SoC. - -rstctrl: reset-controller { - compatible =3D "ti,keystone-reset"; - ti,syscon-pll =3D <&pllctrl 0xe4>; - ti,syscon-dev =3D <&devctrl 0x328>; - ti,wdt-list =3D <0>, <2>; - ti,soft-reset; -}; diff --git a/Documentation/devicetree/bindings/power/reset/ti,keystone-rese= t.yaml b/Documentation/devicetree/bindings/power/reset/ti,keystone-reset.ya= ml new file mode 100644 index 000000000000..ecc68d37f07e --- /dev/null +++ b/Documentation/devicetree/bindings/power/reset/ti,keystone-reset.yaml @@ -0,0 +1,81 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/reset/ti,keystone-reset.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: TI Keystone SoC Reset Controller + +maintainers: + - Andrew Davis + +description: + This is intended to allow SoC reset in case of software reset of selected + watchdogs. The Keystone SoCs can contain up to 4 watchdog timers to reset + SoC. Each watchdog timer event input is connected to the Reset Mux block= . The + Reset Mux block can be configured to cause reset or not. Additionally so= ft or + hard reset can be configured. + +properties: + compatible: + const: ti,keystone-reset + + reg: + maxItems: 1 + + ti,syscon-pll: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: + The phandle to syscon used to access pll controller registers and the + offset to use reset control registers. + items: + - items: + - description: phandle to pll controller syscon + - description: offset within pll controller register space + + ti,syscon-dev: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: + The phandle to syscon used to access device state control registers = and + the offset in order to use mux block registers for all watchdogs. + items: + - items: + - description: phandle to device state control syscon + - description: offset within device state control register + + ti,soft-reset: + type: boolean + description: + Boolean option indicating soft reset. By default hard reset is used. + + ti,wdt-list: + $ref: /schemas/types.yaml#/definitions/uint32-array + description: + WDT list that can cause SoC reset. It's not related to WDT driver, i= t's + just needed to enable a SoC related reset that's triggered by one of + WDTs. The list is in format- <0>, <2>; It can be in random order and + begins from 0 to 3, as keystone can contain up to 4 SoC reset watchd= ogs + and can be in random order. + minItems: 1 + maxItems: 4 + items: + minimum: 0 + maximum: 3 + +required: + - compatible + - reg + - ti,syscon-pll + - ti,syscon-dev + +additionalProperties: false + +examples: + - | + reset-controller@328 { + compatible =3D "ti,keystone-reset"; + reg =3D <0x328 0x10>; + ti,syscon-pll =3D <&pllctrl 0xe4>; + ti,syscon-dev =3D <&devctrl 0x328>; + ti,wdt-list =3D <0>; + }; --- base-commit: 3d6d817622b0a9721e3cc404df3469171582be13 change-id: 20260813-ti-keystone-reset-9ab2c8381651 Best regards, --=20 Bhargav