From: Dilip Kota <eswara.kota@linux.intel.com>
To: wim@linux-watchdog.org, linux@roeck-us.net,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
robbh@kernel.org
Cc: linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com,
cheol.yong.kim@intel.com, qi-ming.wu@intel.com,
yixin.zhu@intel.com, Dilip Kota <eswara.kota@linux.intel.com>
Subject: [PATCH 1/2] dt-bindings: watchdog: intel: Add YAML Schemas for Watchdog timer
Date: Mon, 8 Jun 2020 13:49:39 +0800 [thread overview]
Message-ID: <ac89e289b79fec0a82d1dd060e17eeca024885d5.1591584255.git.eswara.kota@linux.intel.com> (raw)
In-Reply-To: <cover.1591584255.git.eswara.kota@linux.intel.com>
In-Reply-To: <cover.1591584255.git.eswara.kota@linux.intel.com>
Add YAML schemas for the watchdog timer on Intel Lightning
Mountain SoC.
Signed-off-by: Dilip Kota <eswara.kota@linux.intel.com>
---
.../bindings/watchdog/intel,lgm-gptc-wdt.yaml | 75 ++++++++++++++++++++++
1 file changed, 75 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/intel,lgm-gptc-wdt.yaml
diff --git a/Documentation/devicetree/bindings/watchdog/intel,lgm-gptc-wdt.yaml b/Documentation/devicetree/bindings/watchdog/intel,lgm-gptc-wdt.yaml
new file mode 100644
index 0000000000000..83dc39a5090c1
--- /dev/null
+++ b/Documentation/devicetree/bindings/watchdog/intel,lgm-gptc-wdt.yaml
@@ -0,0 +1,75 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/watchdog/intel,lgm-gptc-wdt.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Intel Lightning Mountain Watchdog timer.
+
+maintainers:
+ - Dilip Kota <eswara.kota@linux.intel.com>
+
+description: |
+ Intel Lightning Mountain SoC has General Purpose Timer Counter(GPTC) which can
+ be configured as Clocksource, real time clock and Watchdog timer.
+ Each General Purpose Timer Counter has three timers. And total four General
+ Purpose Timer Counters are present on Lightning Mountain SoC which sums up
+ to 12 timers.
+ Lightning Mountain has four CPUs and each CPU is configured with one GPTC
+ timer as watchdog timer. Total four timers are configured as watchdog timers
+ on Lightning Mountain SoC.
+
+allOf:
+ - $ref: "watchdog.yaml#"
+
+properties:
+ compatible:
+ enum:
+ - intel,lgm-gptc-wdt
+
+ reg:
+ maxItems: 1
+
+ clocks:
+ items:
+ - description: Frequency clock
+ - description: Core clock
+
+ clock-names:
+ items:
+ - const: freq
+ - const: gptc
+
+ intel,wdt-rst-hndl:
+ $ref: /schemas/types.yaml#/definitions/phandle
+ description: Watchdog timer registers handle
+
+ intel,timer-cfg:
+ description: Watchdog Timer id and CPU id
+ allOf:
+ - $ref: /schemas/types.yaml#/definitions/uint32-array
+ - minItems: 2
+ maxItems: 4
+ items:
+ minimum: 0
+ maximum: 3
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - clock-names
+ - intel,wdt-rst-hndl
+ - intel,timer-cfg
+
+examples:
+ - |
+ watchdog@e2500000 {
+ compatible = "intel,lgm-gptc-wdt";
+ reg = <0xe2500000 0x10000>;
+ intel,wdt-rst-hndl = <&sysconf>;
+ clocks = <&cgu0 31>, <&cgu0 136>;
+ clock-names = "freq", "gptc";
+ timeout-sec = <30>;
+ intel,timer-cfg = <1 0 2 1>;
+ };
--
2.11.0
next prev parent reply other threads:[~2020-06-08 5:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 5:49 [PATCH 0/2] Driver for watchdog timer on Intel Lightning Mountain SoC Dilip Kota
2020-06-08 5:49 ` Dilip Kota [this message]
2020-06-08 13:37 ` [PATCH 1/2] dt-bindings: watchdog: intel: Add YAML Schemas for Watchdog timer Guenter Roeck
2020-06-09 8:57 ` Dilip Kota
2020-06-09 13:46 ` Guenter Roeck
2020-06-10 7:54 ` Dilip Kota
2020-06-10 13:05 ` Guenter Roeck
2020-06-11 9:38 ` Dilip Kota
2020-06-11 17:09 ` Guenter Roeck
2020-06-08 5:49 ` [PATCH 2/2] watchdog: intel: Watchdog timer support on Lightning Mountain Dilip Kota
2020-06-08 13:36 ` Guenter Roeck
2020-06-09 8:57 ` Dilip Kota
2020-06-09 13:42 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac89e289b79fec0a82d1dd060e17eeca024885d5.1591584255.git.eswara.kota@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=qi-ming.wu@intel.com \
--cc=robbh@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=yixin.zhu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).