From: vijayakannan.ayyathurai@intel.com
To: wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
andriy.shevchenko@linux.intel.com, mgross@linux.intel.com,
wan.ahmad.zainie.wan.mohamad@intel.com,
lakshmi.bai.raja.subramanian@intel.com,
vijayakannan.ayyathurai@intel.com
Subject: [PATCH v3 0/2] Add drivers for Intel Keem Bay SoC watchdog
Date: Tue, 1 Dec 2020 23:10:32 +0800 [thread overview]
Message-ID: <cover.1606833303.git.vijayakannan.ayyathurai@intel.com> (raw)
From: Vijayakannan Ayyathurai <vijayakannan.ayyathurai@intel.com>
Hi,
This patch set adds the watchdog timer driver support for Intel Keem Bay Soc.
Patch 1 holds the driver and Patch 2 holds the Device Tree
binding documentation.
This driver was tested on the Keem Bay evaluation module board.
Thank you,
Vijay
Changes since v2:
- Remove reduntant write to TIM_WATCHDOG as per Guenter.
- Rebase the driver with 5.10-rc5 tag.
Changes since v1:
- Fix indentation error in the dt-bindings file.
- Use true/false in the second arg of keembay_wdt_set_timeout_reg().
- Fix the watchdog start sequence.
- Avoid reduntant timeout register setting.
- Remove min usage to find actual time at keembay_wdt_set_timeout().
- Remove timeout configuration boundary check at
keembay_wdt_set_pretimeout().
- Use devm_watchdog_register_device() for wdt registration, which
eventually supports driver unload functionality as well.
Vijayakannan Ayyathurai (2):
watchdog: Add watchdog driver for Intel Keembay Soc
dt-bindings: watchdog: Add bindings for Intel Keem Bay SoC
.../bindings/watchdog/intel,keembay-wdt.yaml | 57 ++++
drivers/watchdog/Kconfig | 13 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/keembay_wdt.c | 284 ++++++++++++++++++
4 files changed, 355 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/intel,keembay-wdt.yaml
create mode 100644 drivers/watchdog/keembay_wdt.c
base-commit: 418baf2c28f3473039f2f7377760bd8f6897ae18
prerequisite-patch-id: 822987dcf4c969ef6ac70359b088af06ba39042b
prerequisite-patch-id: 0a348762b660d0d817b8e70cc71647e83173c78c
prerequisite-patch-id: 54c661a006c7362053cb7602448d6c77419d5cf9
prerequisite-patch-id: d140d8534fb828778e0652fe5fcf6282e027f985
--
2.17.1
next reply other threads:[~2020-12-01 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 15:10 vijayakannan.ayyathurai [this message]
2020-12-01 15:10 ` [PATCH v3 1/2] watchdog: Add watchdog driver for Intel Keembay Soc vijayakannan.ayyathurai
2020-12-01 16:30 ` Guenter Roeck
2020-12-02 14:55 ` Ayyathurai, Vijayakannan
2020-12-02 16:32 ` Guenter Roeck
2020-12-02 17:12 ` Ayyathurai, Vijayakannan
2020-12-01 15:10 ` [PATCH v3 2/2] dt-bindings: watchdog: Add bindings for Intel Keem Bay SoC vijayakannan.ayyathurai
2020-12-01 15:41 ` Ayyathurai, Vijayakannan
2020-12-07 18:23 ` Rob Herring
2020-12-08 2:21 ` Ayyathurai, Vijayakannan
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=cover.1606833303.git.vijayakannan.ayyathurai@intel.com \
--to=vijayakannan.ayyathurai@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mgross@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=wan.ahmad.zainie.wan.mohamad@intel.com \
--cc=wim@linux-watchdog.org \
/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).