mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: ashishj3 <ashish.jangam@kpitcummins.com>
Cc: linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
	Dajun <dajun.chen@diasemi.com>,
	linaro-dev@lists.linaro.org
Subject: Re: [PATCH 07/11] Watchdog: DA9052 watchdog support v1
Date: Thu, 14 Jul 2011 12:29:28 +0200	[thread overview]
Message-ID: <20110714102928.GL3834@infomag.iguana.be> (raw)
In-Reply-To: <1310630232.284.16.camel@L-0532.kpit.com>

Hi Ashish, Dajun,

> > This driver adds support for the watchdog functionality provided by the Dialog
> > Semiconductor DA9052 PMIC chip.
> > 
> > Signed-off-by: David Dajun Chen <dchen@diasemi.com>
> > Signed-off-by: Ashish Jangam <ashish.jangam@kpitcummins.com>
> > ---
> If there are no comments then can you ACK this patch?

I remain with my comment of Wed 26 Jan 2011:
> The ioctl WDIOC_SETOPTIONS call is not in line with the watchdog API.
> the supported options are:
> #define WDIOS_DISABLECARD       0x0001  /* Turn off the watchdog timer */
> #define WDIOS_ENABLECARD        0x0002  /* Turn on the watchdog timer */
> #define WDIOS_TEMPPANIC         0x0004  /* Kernel panic on temperature trip */
> Your options are:
> #define DA9052_STROBING_FILTER_ENABLE   0x0001
> #define DA9052_STROBING_FILTER_DISABLE  0x0002
> #define DA9052_SET_STROBING_MODE_MANUAL 0x0004
> #define DA9052_SET_STROBING_MODE_AUTO   0x0008
> 
> Please explain what you want to do.

FYI: this is how the code looks now:
+       case WDIOC_SETOPTIONS:
+               if (get_user(new_value, p))
+                       return -EFAULT;
+               if (new_value == DA9052_ENABLE || new_value == DA9052_DISABLE)
+                       da9052_sm_set_strobing_filter(wdt, new_value);
+               else
+                       wdt->pwdt->sm_strobe_mode_flag = new_value;
+               return 0;

Since the code is still not in line with the watchdog API and since I did not get
an answer yet on what you (or Dajun) want to do, there is definitely NO ACK yet.
If there is a good reasoning behind your needs, we might conclude that this is indeed
worthwhile and extend the API in a proper way. But as it is now, it's not correct.

Kind regards,
Wim.


  reply	other threads:[~2011-07-14 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 13:21 ashishj3
2011-07-14  7:57 ` ashishj3
2011-07-14 10:29   ` Wim Van Sebroeck [this message]
2011-07-25 11:37     ` Ashish Jangam

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=20110714102928.GL3834@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=ashish.jangam@kpitcummins.com \
    --cc=dajun.chen@diasemi.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.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

all inboxes | Powered by JetHome®