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 6/7] MIPS: BCM63XX: Provide platform data to watchdog device
Date: Fri, 29 Oct 2021 11:34:29 -0700 [thread overview]
Message-ID: <20211029183430.4086765-7-f.fainelli@gmail.com> (raw)
In-Reply-To: <20211029183430.4086765-1-f.fainelli@gmail.com>
In order to utilize the bcm7038_wdt.c driver which needs to know the
clock name to obtain, pass it via platform data using the
bcm7038_wdt_platform_data structure.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
arch/mips/bcm63xx/dev-wdt.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/mips/bcm63xx/dev-wdt.c b/arch/mips/bcm63xx/dev-wdt.c
index 2a2346a99bcb..42130914a3c2 100644
--- a/arch/mips/bcm63xx/dev-wdt.c
+++ b/arch/mips/bcm63xx/dev-wdt.c
@@ -9,6 +9,7 @@
#include <linux/init.h>
#include <linux/kernel.h>
#include <linux/platform_device.h>
+#include <linux/platform_data/bcm7038_wdt.h>
#include <bcm63xx_cpu.h>
static struct resource wdt_resources[] = {
@@ -19,11 +20,18 @@ static struct resource wdt_resources[] = {
},
};
+static struct bcm7038_wdt_platform_data bcm63xx_wdt_pdata = {
+ .clk_name = "periph",
+};
+
static struct platform_device bcm63xx_wdt_device = {
.name = "bcm63xx-wdt",
.id = -1,
.num_resources = ARRAY_SIZE(wdt_resources),
.resource = wdt_resources,
+ .dev = {
+ .platform_data = &bcm63xx_wdt_pdata,
+ },
};
int __init bcm63xx_wdt_register(void)
--
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 ` [PATCH v2 2/7] dt-bindings: watchdog: Add BCM6345 compatible to BCM7038 binding Florian Fainelli
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 ` Florian Fainelli [this message]
2021-10-29 18:52 ` [PATCH v2 6/7] MIPS: BCM63XX: Provide platform data to watchdog device 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-7-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).