mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: William Breathitt Gray <vilhelm.gray@gmail.com>, wim@iguana.be
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] watchdog: Add watchdog timer support for the WinSystems EBC-C384
Date: Wed, 27 Jan 2016 17:51:50 -0800	[thread overview]
Message-ID: <56A97436.1090703@roeck-us.net> (raw)
In-Reply-To: <20160128001836.GA15216@sophia>

On 01/27/2016 04:18 PM, William Breathitt Gray wrote:
> On Tue, Jan 26, 2016 at 09:02:45PM -0800, Guenter Roeck wrote:
>>> Unfortunately, the sensors-detect only reported "No" for each Super I/O
>>> chip test, while the superiotool gave an unhelpful "No Super I/O chip
>>> detected" message.
>>>
>>
>> Too bad. That suggests that the watchdog may in fact be implemented in the fpga.
>
> I received a response from WinSystems: the watchdog timer is implemented
> in the Lattice FPGA (base address 0x298), along with other WinSystems
> firmware. I was offered two methods of identifying the chip.
>
> The first method is to use a 16-bit read of the register at port address
> 0x29E to get the version number of the watchdog timer; my machine
> reported a value of 0x0009. Unfortunately, I don't believe this method
> is very reliable since the version number may not be consistent across
> these motherboards, and the same value could easily happen to be
> returned by an unknown hardware.
>
> The second method is slightly more involved so I'll quote WinSystems:
>
>> 8-bit read of 299h – save this value
>> 8-bit write of 60h to 299h
>> 16-bit read of 29ah should return the base address of the WDT which is 564h
>> 8-bit write of saved value to 299h - don’t want t accidentally change the WDT base address
>
> If the system does return a value of 0x564, then it's pretty safe to say
> that the watchdog timer is implemented on the chip. However, I'm not
> sure it would be safe to send write commands to a port address until the
> hardware has been identified; this second method may not be the best
> route either.
>
> What do you think?
>
Let's stick with DMI.

Thanks,
Guenter

  reply	other threads:[~2016-01-28  1:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 19:09 William Breathitt Gray
2016-01-25 19:28 ` One Thousand Gnomes
2016-01-25 20:42   ` Guenter Roeck
2016-01-25 23:36     ` William Breathitt Gray
2016-01-26  1:26       ` Guenter Roeck
2016-01-26 23:38         ` William Breathitt Gray
2016-01-27  5:02           ` Guenter Roeck
2016-01-28  0:18             ` William Breathitt Gray
2016-01-28  1:51               ` Guenter Roeck [this message]
2016-01-28 11:05               ` One Thousand Gnomes
2016-01-26  1:58       ` Guenter Roeck
2016-02-28 14:07   ` Wim Van Sebroeck
2016-02-28 14:36     ` William Breathitt Gray
2016-02-28 15:02     ` Guenter Roeck
2016-02-28 16:24       ` Wim Van Sebroeck
2016-01-26  1:11 ` Guenter Roeck
2016-01-26  9:09 ` Paul Bolle
2016-01-26 12:33   ` William Breathitt Gray
2016-01-26 14:31 William Breathitt Gray
2016-01-26 15:30 ` Guenter Roeck

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=56A97436.1090703@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=vilhelm.gray@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome