From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422686AbeCBGiC (ORCPT ); Fri, 2 Mar 2018 01:38:02 -0500 Received: from mail-pg0-f66.google.com ([74.125.83.66]:34307 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1164731AbeCBGh7 (ORCPT ); Fri, 2 Mar 2018 01:37:59 -0500 X-Google-Smtp-Source: AG47ELuelAwLdD46oFAdQQQBQvY+ggYO0ZHgzCH2+YdmCf1aKqgsqhx7eY+j1g1lMca75MHi/MOxtg== From: Joel Stanley To: Wim Van Sebroeck , Guenter Roeck , Rob Herring , Mark Rutland Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Tomer Maimon , Avi Fishman , Brendan Higgins Subject: [PATCH 0/2] watchdog: Add Nuvoton NPCM (Poleg) driver Date: Fri, 2 Mar 2018 17:07:44 +1030 Message-Id: <20180302063746.10993-1-joel@jms.id.au> X-Mailer: git-send-email 2.15.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is a driver for the Poleg board that is in the process of being upstreamed. I have tested it on an evaluation board. The watchdog is a single register inside of the timer IP. This made me think about how to describe the device tree bindings for a while, but after some discussion I settled on describing the watchdog separately, and giving it's own compatible string, and it's own driver. The timer is being reviewed over here: https://lkml.org/lkml/2018/2/26/492 Joel Stanley (2): dt-bindings: watchdog: Add Nuvoton NPCM description watchdog: Add Nuvoton NPCM watchdog driver .../bindings/watchdog/nuvoton,npcm-wdt.txt | 25 +++ drivers/watchdog/Kconfig | 11 + drivers/watchdog/Makefile | 1 + drivers/watchdog/npcm_wdt.c | 223 +++++++++++++++++++++ 4 files changed, 260 insertions(+) create mode 100644 Documentation/devicetree/bindings/watchdog/nuvoton,npcm-wdt.txt create mode 100644 drivers/watchdog/npcm_wdt.c -- 2.15.1