All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Generic watchdog question
Date: Mon, 26 Sep 2016 00:48:07 -0700	[thread overview]
Message-ID: <CAMKF1sqJoOt3=OJVrjcCoh2S+Y3PQ3F0_CbL6GzEcbpbcX6MUQ@mail.gmail.com> (raw)
In-Reply-To: <6bb7a3dc-56fd-7fed-07a7-15229d8a99ab@mlbassoc.com>

On Mon, Sep 26, 2016 at 12:37 AM, Gary Thomas <gary@mlbassoc.com> wrote:
> A little off-topic but driven by some recent changes in OE-core.
>
> My board has two watchdog devices - one on the SoC and the
> other is an external device.  With my latest kernel (4.1.15)
> I have these devices:
>
>   # ls -l /dev/watch*
>   crw------- 1 root root  10, 130 Jan  3  1970 /dev/watchdog
>   crw------- 1 root root 251,   0 Jan  3  1970 /dev/watchdog0
>   crw------- 1 root root 251,   1 Jan  3  1970 /dev/watchdog1
>
> I've only been able to get my watchdog to "feel happy" when I
> use /dev/watchdog1 as the device being watched over by the
> watchdog processes.  I'm just wondering what those other devices
> are - maybe /dev/watchdog is supposed to be a composite (although
> that doesn't seem to be the case)
>
> Can anyone explain how this is expected to work, especially in
> light of the recent changes to the watchdog recipes in OE-core?
>

could be that its a software warchdog what does

dmesg | grep -i watchdog

tell you.


> Thanks
>
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


  reply	other threads:[~2016-09-26  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26  7:37 Generic watchdog question Gary Thomas
2016-09-26  7:48 ` Khem Raj [this message]
2016-09-26  8:05   ` Gary Thomas

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='CAMKF1sqJoOt3=OJVrjcCoh2S+Y3PQ3F0_CbL6GzEcbpbcX6MUQ@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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 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.