From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
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 v4 5/7] watchdog: bcm7038_wdt: Add platform device id for bcm63xx-wdt
Date: Fri, 5 Nov 2021 08:42:06 -0700 [thread overview]
Message-ID: <20211105154208.614260-6-f.fainelli@gmail.com> (raw)
In-Reply-To: <20211105154208.614260-1-f.fainelli@gmail.com>
In order to phase out bcm63xx_wdt and use bcm7038_wdt instead, introduce
a platform_device_id table that allows both names to be matched.
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
drivers/watchdog/bcm7038_wdt.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/watchdog/bcm7038_wdt.c b/drivers/watchdog/bcm7038_wdt.c
index 506cd7ef9c77..a8a0e8485125 100644
--- a/drivers/watchdog/bcm7038_wdt.c
+++ b/drivers/watchdog/bcm7038_wdt.c
@@ -223,8 +223,16 @@ static const struct of_device_id bcm7038_wdt_match[] = {
};
MODULE_DEVICE_TABLE(of, bcm7038_wdt_match);
+static const struct platform_device_id bcm7038_wdt_devtype[] = {
+ { .name = "bcm7038-wdt" },
+ { .name = "bcm63xx-wdt" },
+ { /* sentinel */ },
+};
+MODULE_DEVICE_TABLE(platform, bcm7038_wdt_devtype);
+
static struct platform_driver bcm7038_wdt_driver = {
.probe = bcm7038_wdt_probe,
+ .id_table = bcm7038_wdt_devtype,
.driver = {
.name = "bcm7038-wdt",
.of_match_table = bcm7038_wdt_match,
--
2.25.1
next prev parent reply other threads:[~2021-11-05 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 15:42 [PATCH v4 0/7] Removal of bcm63xx-wdt Florian Fainelli
2021-11-05 15:42 ` [PATCH v4 1/7] dt-bindings: watchdog: convert Broadcom's WDT to the json-schema Florian Fainelli
2021-11-12 22:39 ` Rob Herring
2021-11-05 15:42 ` [PATCH v4 2/7] dt-bindings: watchdog: Add BCM6345 compatible to BCM7038 binding Florian Fainelli
2021-11-12 22:40 ` Rob Herring
2021-11-05 15:42 ` [PATCH v4 3/7] watchdog: bcm7038_wdt: Support platform data configuration Florian Fainelli
2021-11-05 15:42 ` [PATCH v4 4/7] watchdog: Allow building BCM7038_WDT for BCM63XX Florian Fainelli
2021-11-05 15:42 ` Florian Fainelli [this message]
2021-11-09 10:38 ` [PATCH v4 5/7] watchdog: bcm7038_wdt: Add platform device id for bcm63xx-wdt Rafał Miłecki
2021-11-12 22:43 ` Florian Fainelli
2021-11-05 15:42 ` [PATCH v4 6/7] MIPS: BCM63XX: Provide platform data to watchdog device Florian Fainelli
2021-11-05 15:42 ` [PATCH v4 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=20211105154208.614260-6-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=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).