All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Artamonow <mad_soft@inbox.ru>
To: Marc Vertes <marc.vertes@sigfox.com>
Cc: w.sang@pengutronix.de, wim@iguana.be,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
	HaraldWelte@viatech.com, broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH RFC] watchdog: add a new driver for VIA chipsets
Date: Wed, 23 Nov 2011 16:10:51 +0400	[thread overview]
Message-ID: <20111123121051.GA18320@rainbow> (raw)
In-Reply-To: <4ecbf011.dZASXe6D5kH4Uxve%marc.vertes@sigfox.com>

On 19:55 Tue 22 Nov     , Marc Vertes wrote:
> Add a new driver for the hardware watchdog timer on VIA chipsets.
> This driver uses the new watchdog framework.
> Tested on a Artigo A1100, VX855 chipset.
> 
> Signed-off-by: Marc Vertes <marc.vertes@sigfox.com>
> ---

[ .... ]

> +obj-$(CONFIG_VIA_WDT) += via_wdt.o

"via_wdt" seems to be a too generic name. What if someone will want to
write driver for some incompatible watchdog also made by VIA?
Maybe it's worth to use something more specific - say, "via_vx8xx_wdt"?


> + *
> + * The only way to activate the watchdog timer or to set its period is
> + * through BIOS setup.
> + */

Why is to rely on BIOS setup? Is there really no information on what
registers to write to start watchdog? Or you was just lazy to find it?
It took me less than a minute to google up a datasheet[1] on VX800/VX820
and it seems to have all needed information to implement proper start()
and stop() functions. I suppose info on watchdog registers should be
applicable to VX855 as well - but it's better to check on your hardware
anyway.

[1] http://linux.via.com.tw/support/beginDownload.action?eleid=161&fid=241

-- 
Best regards,
Dmitry "MAD" Artamonow


  reply	other threads:[~2011-11-23 12:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 11:17 [PATCH RFC] watchdog: add a new driver for VIA chipsets Marc Vertes
2011-11-22 11:22 ` Wolfram Sang
2011-11-22 12:56   ` Rahul Bedarkar
2011-11-22 12:56     ` Rahul Bedarkar
2011-11-22 17:05   ` Marc Vertes
2011-11-22 17:30     ` Wolfram Sang
2011-11-22 18:09       ` Marc Vertes
2011-11-22 18:55         ` Marc Vertes
2011-11-23 12:10           ` Dmitry Artamonow [this message]
2011-11-23 14:12             ` Marc Vertes
2011-11-23 14:37               ` Mark Brown
2011-11-23 19:25               ` Dmitry Artamonow
2011-11-23 21:43                 ` Wolfram Sang
2011-11-23 18:22             ` Harald Welte
2011-11-23 21:41               ` Wim Van Sebroeck
2011-11-24 19:22                 ` Marc Vertes
2011-11-24 19:34                   ` Wim Van Sebroeck
2011-11-25 20:02                     ` Marc Vertes
2011-11-22 17:32     ` Mark Brown
2011-11-22 18:40       ` Wolfram Sang
2011-11-23  9:59         ` Marc Vertes
2011-11-23 10:49           ` Wolfram Sang
2011-11-23 11:43             ` Marc Vertes
2011-11-23 12:13             ` Wim Van Sebroeck
2011-11-23 12:20               ` Mark Brown
2011-11-23 12:40                 ` Wim Van Sebroeck
2011-11-23 14:46                   ` Marc Vertes
2011-11-23 21:43                     ` Wim Van Sebroeck
2011-11-23 21:52                       ` Wolfram Sang
2011-11-24  8:29                         ` Wim Van Sebroeck
2011-11-23 21:46                     ` Wim Van Sebroeck
2011-11-24 10:57                       ` Marc Vertes
2011-11-24 13:42                         ` Wim Van Sebroeck
2011-11-24 14:42                           ` Marc Vertes
2011-11-24 15:48                             ` Wim Van Sebroeck
2011-11-24 16:47                               ` Marc Vertes

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=20111123121051.GA18320@rainbow \
    --to=mad_soft@inbox.ru \
    --cc=HaraldWelte@viatech.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=marc.vertes@sigfox.com \
    --cc=w.sang@pengutronix.de \
    --cc=wim@iguana.be \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.