Generic watchdog question

Generic watchdog question

[Gary Thomas]

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?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Generic watchdog question

[Khem Raj]

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

Re: Generic watchdog question

[Gary Thomas]

On 2016-09-26 09:48, Khem Raj wrote:
> 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.

Nothing (it's empty)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------