From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: rafal@milecki.pl, Florian Fainelli <f.fainelli@gmail.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
bcm-kernel-feedback-list@broadcom.com (maintainer:BROADCOM
BCM63XX ARM ARCHITECTURE), Justin Chen <justinpopo6@gmail.com>,
linux-watchdog@vger.kernel.org (open list:WATCHDOG DEVICE
DRIVERS),
devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
FLATTENED DEVICE TREE BINDINGS),
linux-mips@vger.kernel.org (open list:MIPS),
linux-arm-kernel@lists.infradead.org (moderated list:BROADCOM
BCM63XX ARM ARCHITECTURE)
Subject: [PATCH v2 2/7] dt-bindings: watchdog: Add BCM6345 compatible to BCM7038 binding
Date: Fri, 29 Oct 2021 11:34:25 -0700 [thread overview]
Message-ID: <20211029183430.4086765-3-f.fainelli@gmail.com> (raw)
In-Reply-To: <20211029183430.4086765-1-f.fainelli@gmail.com>
The BCM7038 watchdog binding is updated to include a "brcm,bcm6345-wdt"
compatible string which is the first instance of a DSL (BCM63xx) SoC
seeing the integration of such a watchdog timer block.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
.../devicetree/bindings/watchdog/brcm,bcm7038-wdt.yaml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.yaml b/Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.yaml
index bbf2e91f9db7..72cce0a046a6 100644
--- a/Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.yaml
+++ b/Documentation/devicetree/bindings/watchdog/brcm,bcm7038-wdt.yaml
@@ -4,7 +4,7 @@
$id: http://devicetree.org/schemas/watchdog/brcm,bcm7038-wdt.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
-title: BCM7038 watchdog timer
+title: BCM63xx and BCM7038 watchdog timer
allOf:
- $ref: "watchdog.yaml#"
@@ -15,7 +15,9 @@ maintainers:
properties:
compatible:
- const: brcm,bcm7038-wdt
+ enum:
+ - brcm,bcm6345-wdt
+ - brcm,bcm7038-wdt
reg:
maxItems: 1
--
2.25.1
next prev parent reply other threads:[~2021-10-29 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 18:34 [PATCH v2 0/7] Removal of bcm63xx-wdt Florian Fainelli
2021-10-29 18:34 ` [PATCH v2 1/7] dt-bindings: watchdog: convert Broadcom's WDT to the json-schema Florian Fainelli
2021-10-29 18:34 ` Florian Fainelli [this message]
2021-10-29 18:34 ` [PATCH v2 3/7] watchdog: bcm7038_wdt: Support platform data configuration Florian Fainelli
2021-10-29 18:34 ` [PATCH v2 4/7] watchdog: Allow building BCM7038_WDT for BCM63XX Florian Fainelli
2021-10-29 18:34 ` [PATCH v2 5/7] watchdog: bcm7038_wdt: Add platform device id for bcm63xx-wdt Florian Fainelli
2021-10-29 18:34 ` [PATCH v2 6/7] MIPS: BCM63XX: Provide platform data to watchdog device Florian Fainelli
2021-10-29 18:52 ` Guenter Roeck
2021-10-29 18:34 ` [PATCH v2 7/7] watchdog: Remove BCM63XX_WDT Florian Fainelli
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=20211029183430.4086765-3-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=justinpopo6@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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).