All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rongqing Li <rongqing.li@windriver.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] watchdog: enable systemd support
Date: Fri, 22 Jan 2016 13:29:41 +0800	[thread overview]
Message-ID: <56A1BE45.3040900@windriver.com> (raw)
In-Reply-To: <56A162A5.1000802@windriver.com>



On 2016年01月22日 06:58, Randy MacLeod wrote:
> On 2016-01-19 09:01 PM, rongqing.li@windriver.com wrote:
>> 1. inherit systemd, and add two unit files which are from Fedora 23
>
> Fine.
>> 2. auto load soft dog kernel module
>
> I haven't used a hardware watchdog for a while. Does softdog
> abstract that away so that it's hidden by the BSP? If not,
> can a user ditch the softdog for a hardware watchdog? Does that
> over-ride process need to be documented?
>
>

Usually, watchdog timers are implemented as add-on cards, or as on-chip
peripherals within microcontrollers. But if there is no hardware watchdog,
the Linux kernel can provide a software watchdog implemented using kernel
timers.

https://en.wikibooks.org/wiki/The_Linux_Kernel/Softdog_Driver


if the machine has the hardware watchdog, and drivers are compiled in,
the /dev/watchdog will be generated; softdog is /dev/watchdog1 or
/dev/watchdog2, and the watchdog daemon will use the hardware watchdog


if drivers are compiled as module, udev will auto load it, but udev
will be run after systemd-modules-load.service, and softdog will be
used


-- 
Best Reagrds,
Roy | RongQing Li


  reply	other threads:[~2016-01-22  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20  2:01 [PATCH] watchdog: enable systemd support rongqing.li
2016-01-21 13:03 ` Burton, Ross
2016-01-21 22:58 ` Randy MacLeod
2016-01-22  5:29   ` Rongqing Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-27  6:27 rongqing.li
2015-11-27 11:20 ` Otavio Salvador

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=56A1BE45.3040900@windriver.com \
    --to=rongqing.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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.