Message ID | 20240131221957.213717-1-afd@ti.com |
---|---|
Headers |
Return-Path: <linux-kernel+bounces-47239-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:693c:2685:b0:106:209c:c626 with SMTP id mn5csp59485dyc; Wed, 31 Jan 2024 14:21:21 -0800 (PST) X-Google-Smtp-Source: AGHT+IHHLMYTo6Q3/g3WF9QZ+QiNlldi3peEA5RSJ7h52mF4dxbyqfzQGw5qcFoX6E7DeSHaEkmF X-Received: by 2002:a05:6358:63a5:b0:175:4f0f:bbab with SMTP id k37-20020a05635863a500b001754f0fbbabmr3481166rwh.22.1706739681562; Wed, 31 Jan 2024 14:21:21 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706739681; cv=pass; d=google.com; s=arc-20160816; b=YmYdi4YbxHkc7yV2D0oC402StIlvoS8Ie6OOuq6/NimxXzyzNcahVGUPKYGdOeoN0Q OMe1s4W73zD0HoRcbS6uhhjFFulLYwB/N/g5qkEh3VNV4UpeAkLIsyhfMxCfjdTV7Nmg RFgjA0svoaCeioZm/OwCLsqy5YE9U7YdIODBg2Y5fpvFO8w/vLPOYGUduGHTvw6448/3 rdrugIkdO//XMMIItWhm4Hwmg8cgkHAUqBlHT22opP2K7DEixSARvNYi/5cOe5oK/IGt rUG5ldA7+sDGSL/k0rRrcE05NbU0qbImEjGZxlTSuGgL2x6QH+y9cul8A2ejbf3Gh3Q0 33dw== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=oxfY+NQUBrJCOZE6uSbWk7em4uytovOm7ANLLvlhJLU=; fh=wVW5YK8I55LZiPUbGZ0jviIM3lckcSEg+TJHjEo9vXg=; b=STGilh/6vakXYd2sgRwpSFbgY7imRtVdLneFeX7JqFBJWmdZMvEF89Xu8T6kMJ4gkz fmBvI6GJTmcR2Twa/elubJWj6/1uAOo/Vsf/YwZVNsvX7NwC3AbyTtJ3IrJpO2/uUNt5 MbGuDUtyH6isxAhpIM7Do8PY83XHtPQE1jfU/jEVHjopCcz+/ETvrujANNajfT4aOj1q zHppv6Jyubr1LSPmNTB7xbB7X5dTfxztejxDv+4GUbIUDhZWoZ4UX3+hQ10SFuRlP03b +ipU13bim8rTR1ZjaiT8eHDyUEIRQI+N4XBxdzu8ZfW/hrqD/0TlTmsAW0ztVzLbzGv1 ebZg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=wDwTMp9z; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-47239-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-47239-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com X-Forwarded-Encrypted: i=1; AJvYcCUrzXmj2I7a0ZSGiHQq0eApL0DtZXk51SGOvoLDv3jCfc5auxHFe7I3TVjbev2nZMf69O99CrR99XM7nXXDQDsOQM4eRg== Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id s28-20020a63525c000000b005d3fa779f4esi8248256pgl.344.2024.01.31.14.21.21 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 31 Jan 2024 14:21:21 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-47239-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=wDwTMp9z; arc=pass (i=1 spf=pass spfdomain=ti.com dkim=pass dkdomain=ti.com dmarc=pass fromdomain=ti.com); spf=pass (google.com: domain of linux-kernel+bounces-47239-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-47239-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 4524F291296 for <ouuuleilei@gmail.com>; Wed, 31 Jan 2024 22:21:21 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 597443B2A2; Wed, 31 Jan 2024 22:20:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="wDwTMp9z" Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7586739AE6; Wed, 31 Jan 2024 22:20:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.47.19.141 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706739608; cv=none; b=krNXN1MZM0UCYEemz67/hqy4MV1I5bI2TZqFO2FdD9wuL7zjw4TEJlceJZmPDFpwXjjVHX8vMIuMTutRhn0fFXiKyY5RlUevVl1tNDnKvFbFa/K45iLQySy7pIkyxO/g9UeWX1Faq7aFIxfQf2q1LCk5VX2xKdXjps2DAcJ45nM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706739608; c=relaxed/simple; bh=HEiByU47X4szvoKot6Qi4UvZvWQwUxoeP2aw/yIdkGo=; h=From:To:CC:Subject:Date:Message-ID:MIME-Version:Content-Type; b=fEp7JKHm0+zYocBQviDJ3VNj2gTiZVMjORI3uNu2Ca+F2kYRVmNEfHR8I/zUWe7X7RtdDBPSBTtpXAIbrv21mI8qkRJ+Bmv/eHPETcB40S9gv/JcnM7IyvwSC3HiIjNVeiJcnrCjQlUhW3Q45uJItDcUUKU6YiRkFLGC/pE/OW4= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com; spf=pass smtp.mailfrom=ti.com; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b=wDwTMp9z; arc=none smtp.client-ip=198.47.19.141 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=ti.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ti.com Received: from fllv0035.itg.ti.com ([10.64.41.0]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 40VMJxeY004316; Wed, 31 Jan 2024 16:19:59 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1706739599; bh=oxfY+NQUBrJCOZE6uSbWk7em4uytovOm7ANLLvlhJLU=; h=From:To:CC:Subject:Date; b=wDwTMp9z16PtwTgdyWMduRQ3Rr9ypGsPlc4vQW6rgC04yJqs0J6ofVm+qxH5rlw1k 6qP1onbHSC8bcOYQA71ChorAohuKFFXGb2I56CmgrZnNTG18ILuOQ9vGZrXG3YO2RK kV4qMm5hHjiR0RvYLHVOYvJOgDRDsp/oH9eeCnA0= Received: from DLEE112.ent.ti.com (dlee112.ent.ti.com [157.170.170.23]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 40VMJxtN100443 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 31 Jan 2024 16:19:59 -0600 Received: from DLEE109.ent.ti.com (157.170.170.41) by DLEE112.ent.ti.com (157.170.170.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 31 Jan 2024 16:19:59 -0600 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DLEE109.ent.ti.com (157.170.170.41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 31 Jan 2024 16:19:59 -0600 Received: from lelvsmtp5.itg.ti.com ([10.249.42.149]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 40VMJwx2102504; Wed, 31 Jan 2024 16:19:58 -0600 From: Andrew Davis <afd@ti.com> To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>, Santosh Shilimkar <ssantosh@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, Sebastian Reichel <sre@kernel.org>, Vignesh Raghavendra <vigneshr@ti.com> CC: <linux-arm-kernel@lists.infradead.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>, Andrew Davis <afd@ti.com> Subject: [PATCH 00/12] Add TI-SCI reboot driver Date: Wed, 31 Jan 2024 16:19:45 -0600 Message-ID: <20240131221957.213717-1-afd@ti.com> X-Mailer: git-send-email 2.39.2 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1789646268463103930 X-GMAIL-MSGID: 1789646268463103930 |
Series |
Add TI-SCI reboot driver
|
|
Message
Andrew Davis
Jan. 31, 2024, 10:19 p.m. UTC
Hello all, While PCSI normally handles reboot for K3, this is an available fallback in case PCSI reboot fails. This driver is registered with low priority as we want PSCI to remain the main way these devices are rebooted. The important part is the binding/DT changes. Currently in U-Boot (which use the Linux device trees) we may not have PSCI available yet (pre TF-A) and so we need this node to correctly reboot. Adding this node in U-Boot is one of the last remaining deltas between the two project DT files. Thanks, Andrew Andrew Davis (12): dt-bindings: power: reset: Document ti,sci-reboot compatible dt-bindings: arm: keystone: ti-sci: Add reboot-controller child node power: reset: Add TI-SCI reboot driver arm64: dts: ti: k3-am64: Add reboot-controller node arm64: dts: ti: k3-am62: Add reboot-controller node arm64: dts: ti: k3-am62a: Add reboot-controller node arm64: dts: ti: k3-am62p: Add reboot-controller node arm64: dts: ti: k3-am65: Add reboot-controller node arm64: dts: ti: k3-j7200: Add reboot-controller node arm64: dts: ti: k3-j721e: Add reboot-controller node arm64: dts: ti: k3-j721s2: Add reboot-controller node arm64: dts: ti: k3-j784s4: Add reboot-controller node .../bindings/arm/keystone/ti,sci.yaml | 8 +++ .../bindings/power/reset/ti,sci-reboot.yaml | 33 ++++++++++ MAINTAINERS | 2 + arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 5 ++ arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 4 ++ arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 5 ++ arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 5 ++ arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 4 ++ .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 5 ++ drivers/power/reset/Kconfig | 7 +++ drivers/power/reset/Makefile | 1 + drivers/power/reset/ti-sci-reboot.c | 63 +++++++++++++++++++ 15 files changed, 154 insertions(+) create mode 100644 Documentation/devicetree/bindings/power/reset/ti,sci-reboot.yaml create mode 100644 drivers/power/reset/ti-sci-reboot.c
Comments
On 16:19-20240131, Andrew Davis wrote: > Hello all, > > While PCSI normally handles reboot for K3, this is an available > fallback in case PCSI reboot fails. This driver is registered > with low priority as we want PSCI to remain the main way these > devices are rebooted. > > The important part is the binding/DT changes. Currently in > U-Boot (which use the Linux device trees) we may not have > PSCI available yet (pre TF-A) and so we need this node > to correctly reboot. Adding this node in U-Boot is one of > the last remaining deltas between the two project DT files. > > Thanks, > Andrew > > Andrew Davis (12): > dt-bindings: power: reset: Document ti,sci-reboot compatible > dt-bindings: arm: keystone: ti-sci: Add reboot-controller child node > power: reset: Add TI-SCI reboot driver > arm64: dts: ti: k3-am64: Add reboot-controller node > arm64: dts: ti: k3-am62: Add reboot-controller node > arm64: dts: ti: k3-am62a: Add reboot-controller node > arm64: dts: ti: k3-am62p: Add reboot-controller node > arm64: dts: ti: k3-am65: Add reboot-controller node > arm64: dts: ti: k3-j7200: Add reboot-controller node > arm64: dts: ti: k3-j721e: Add reboot-controller node > arm64: dts: ti: k3-j721s2: Add reboot-controller node > arm64: dts: ti: k3-j784s4: Add reboot-controller node Maybe after the driver has been accepted, a defconfig patch(module) might be useful? > > .../bindings/arm/keystone/ti,sci.yaml | 8 +++ > .../bindings/power/reset/ti,sci-reboot.yaml | 33 ++++++++++ > MAINTAINERS | 2 + > arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 5 ++ > arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 4 ++ > arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 5 ++ > arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 5 ++ > arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 4 ++ > .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 4 ++ > .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 4 ++ > .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 4 ++ > .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 5 ++ > drivers/power/reset/Kconfig | 7 +++ > drivers/power/reset/Makefile | 1 + > drivers/power/reset/ti-sci-reboot.c | 63 +++++++++++++++++++ > 15 files changed, 154 insertions(+) > create mode 100644 Documentation/devicetree/bindings/power/reset/ti,sci-reboot.yaml > create mode 100644 drivers/power/reset/ti-sci-reboot.c