From: "Pali Rohár" <pali@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: max63xx_wdt: Add support for specifying WDI logic via GPIO
Date: Thu, 28 Apr 2022 16:32:10 +0200 [thread overview]
Message-ID: <20220428143210.6cbvik2kmjul3qo5@pali> (raw)
In-Reply-To: <b19ce453-1235-689b-8796-fa6cba35c1f0@roeck-us.net>
On Thursday 28 April 2022 06:10:56 Guenter Roeck wrote:
> On 4/28/22 02:16, Pali Rohár wrote:
> > On some boards is WDI logic of max6370 chip connected via GPIO. So extend
> > max63xx_wdt driver and DTS schema to allow specifying WDI logic via GPIO.
> >
> > Signed-off-by: Pali Rohár <pali@kernel.org>
>
> How is that different to just using the gpio watchdog driver ?
GPIO watchdog driver does not support max6370 memory mapped
configuration.
With this change, max6370 can use memory mapped space for watchdog
configuration and GPIO WDI for pinging.
> Guenter
>
> > ---
> > .../bindings/watchdog/maxim,max63xx.yaml | 4 +++
> > drivers/watchdog/max63xx_wdt.c | 28 +++++++++++++++++++
> > 2 files changed, 32 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/watchdog/maxim,max63xx.yaml b/Documentation/devicetree/bindings/watchdog/maxim,max63xx.yaml
> > index ab9641e845db..a97aa0135ef9 100644
> > --- a/Documentation/devicetree/bindings/watchdog/maxim,max63xx.yaml
> > +++ b/Documentation/devicetree/bindings/watchdog/maxim,max63xx.yaml
> > @@ -27,6 +27,10 @@ properties:
> > description: This is a 1-byte memory-mapped address
> > maxItems: 1
> > + gpios:
> > + description: Optional GPIO used for controlling WDI when WDI bit is not mapped to memory
> > + maxItems: 1
> > +
> > required:
> > - compatible
> > - reg
> > diff --git a/drivers/watchdog/max63xx_wdt.c b/drivers/watchdog/max63xx_wdt.c
> > index 9e1541cfae0d..eaf00c3f06a5 100644
> > --- a/drivers/watchdog/max63xx_wdt.c
> > +++ b/drivers/watchdog/max63xx_wdt.c
> > @@ -27,6 +27,7 @@
> > #include <linux/io.h>
> > #include <linux/slab.h>
> > #include <linux/property.h>
> > +#include <linux/gpio/consumer.h>
> > #define DEFAULT_HEARTBEAT 60
> > #define MAX_HEARTBEAT 60
> > @@ -53,6 +54,9 @@ struct max63xx_wdt {
> > void __iomem *base;
> > spinlock_t lock;
> > + /* GPIOs */
> > + struct gpio_desc *gpio_wdi;
> > +
> > /* WDI and WSET bits write access routines */
> > void (*ping)(struct max63xx_wdt *wdt);
> > void (*set)(struct max63xx_wdt *wdt, u8 set);
> > @@ -158,6 +162,17 @@ static const struct watchdog_info max63xx_wdt_info = {
> > .identity = "max63xx Watchdog",
> > };
> > +static void max63xx_gpio_ping(struct max63xx_wdt *wdt)
> > +{
> > + spin_lock(&wdt->lock);
> > +
> > + gpiod_set_value_cansleep(wdt->gpio_wdi, 1);
> > + udelay(1);
> > + gpiod_set_value_cansleep(wdt->gpio_wdi, 0);
> > +
> > + spin_unlock(&wdt->lock);
> > +}
> > +
> > static void max63xx_mmap_ping(struct max63xx_wdt *wdt)
> > {
> > u8 val;
> > @@ -225,6 +240,19 @@ static int max63xx_wdt_probe(struct platform_device *pdev)
> > return -EINVAL;
> > }
> > + wdt->gpio_wdi = devm_gpiod_get(dev, NULL, GPIOD_FLAGS_BIT_DIR_OUT);
> > + if (IS_ERR(wdt->gpio_wdi) && PTR_ERR(wdt->gpio_wdi) != -ENOENT) {
> > + if (PTR_ERR(wdt->gpio_wdi) != -EPROBE_DEFER)
> > + dev_err(dev, "unable to request gpio: %ld\n",
> > + PTR_ERR(wdt->gpio_wdi));
> > + return PTR_ERR(wdt->gpio_wdi);
> > + }
> > +
> > + if (!IS_ERR(wdt->gpio_wdi))
> > + wdt->ping = max63xx_gpio_ping;
> > + else
> > + wdt->gpio_wdi = NULL;
> > +
> > err = max63xx_mmap_init(pdev, wdt);
> > if (err)
> > return err;
>
next prev parent reply other threads:[~2022-04-28 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 9:16 [PATCH] watchdog: max63xx_wdt: Add support for specifying WDI logic via GPIO Pali Rohár
2022-04-28 13:10 ` Guenter Roeck
2022-04-28 14:32 ` Pali Rohár [this message]
2022-04-28 15:29 ` Guenter Roeck
2022-04-28 18:25 ` Pali Rohár
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=20220428143210.6cbvik2kmjul3qo5@pali \
--to=pali@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--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