Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1630189

Re: [PATCH 0/2] DS1374 Watchdog fixes

From Guenter Roeck <linux@roeck-us.net>
Newsgroups linux.kernel
Subject Re: [PATCH 0/2] DS1374 Watchdog fixes
Date 2017-04-25 07:10 +0200
Message-ID <tA0TD-ex-9@gated-at.bofh.it> (permalink)
References <tzUlb-4gQ-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 04/24/2017 03:05 PM, Moritz Fischer wrote:
> Hi all,
>
> this series fixes two issues that I ran into when trying to use the
> watchdog part of the DS1374 on of our products.
>
> This series is basically a precursor to some further cleanup work,
> that turns the DS1374 into a MFD device with an RTC and WDT in
> separate drivers [1] each integrated in either the watchdog and
> the rtc frameworks.
>
> I'm very unhappy with the CONFIG_DRV_RTC_DS1374_WDT way of enabling
> the watchdog behavior and currently I'm investigating how to make
> that work via DT.
>
> Watchdog maintainers, do you have an idea on how to do that in a
> non breaking fashion?
>

Depends on what you mean with "non breaking". Just using the normal mfd
mechanisms, ie define an mfd cell for each client driver, should work.
Do you see any problems with that ? Either case, that doesn't seem
to be a watchdog driver problem, or am I missing something ?

> Thanks,
> Moritz
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/mdf/linux.git/log/?h=wip/mfd-ds1374-rfc
>
> Moritz Fischer (2):
>   rtc: ds1374: wdt: Fix issue with timeout scaling from secs to wdt
>     ticks
>   rtc: ds1374: wdt: Fix stop/start ioctl always returning -EINVAL
>

I don't really see the point of doing that if you plan to move the watchdog
part of the driver into the watchdog directory. We for sure won't accept a
watchdog driver that does not use the watchdog infrastructure.

Regarding
+	/* WHY? */
+	ds1374->wdd.timeout = t;

Assuming you mean why the driver has to set the timeout value - not every
watchdog hardware supports timeouts in multiples of 1 second. The driver
is expected to set the value to the real timeout, not to the timeout asked
for by the infrastructure.

Guenter

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 0/2] DS1374 Watchdog fixes Moritz Fischer <mdf@kernel.org> - 2017-04-25 00:10 +0200
  Re: [PATCH 0/2] DS1374 Watchdog fixes Guenter Roeck <linux@roeck-us.net> - 2017-04-25 07:10 +0200
    Re: [PATCH 0/2] DS1374 Watchdog fixes Moritz Fischer <moritz.fischer.private@gmail.com> - 2017-04-25 17:00 +0200
      Re: [PATCH 0/2] DS1374 Watchdog fixes Guenter Roeck <linux@roeck-us.net> - 2017-04-25 18:20 +0200
        Re: [PATCH 0/2] DS1374 Watchdog fixes Alexandre Belloni <alexandre.belloni@free-electrons.com> - 2017-04-25 18:40 +0200
          Re: [PATCH 0/2] DS1374 Watchdog fixes Guenter Roeck <linux@roeck-us.net> - 2017-04-25 19:00 +0200
            Re: [PATCH 0/2] DS1374 Watchdog fixes Moritz Fischer <mdf@kernel.org> - 2017-04-25 22:00 +0200
              Re: [PATCH 0/2] DS1374 Watchdog fixes Guenter Roeck <linux@roeck-us.net> - 2017-04-25 22:30 +0200
                Re: [PATCH 0/2] DS1374 Watchdog fixes Moritz Fischer <mdf@kernel.org> - 2017-04-25 22:40 +0200
                Re: [PATCH 0/2] DS1374 Watchdog fixes Guenter Roeck <linux@roeck-us.net> - 2017-04-25 23:10 +0200

csiph-web