mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boszormenyi Zoltan <zboszor@pr.hu>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
	Lyude Paul <lyude@redhat.com>
Subject: Re: [PATCH 12/12] watchdog: sp5100_tco: Add support for recent FCH versions
Date: Wed, 10 Jan 2018 09:34:08 +0100	[thread overview]
Message-ID: <d5184137-e909-9fc5-aa12-a551924c4241@pr.hu> (raw)
In-Reply-To: <20180104192114.GA28864@roeck-us.net>

I'm trying to remove non-ASCII chars from the mail body in the hope
it reaches the lists... My ISP still adds that X-Spam-Report: header
quoting large part of the mail body without MIME-encoding it.

On 2018-01-04 20:21, Guenter Roeck wrote:
> On Thu, Jan 04, 2018 at 01:01:22PM +0100, Boszormenyi Zoltan wrote:
>> On 2017-12-24 22:04, Guenter Roeck wrote:
>>> Starting with Family 16h Models 30h-3Fh and Family 15h Models 60h-6Fh,
>>> watchdog address space decoding has changed. The cutover point is already
>>> identified in the i2c-piix2 driver, so use the same mechanism.
>>
>> "i2c-piix4".
>>
> Thanks!
> 
>> Otherwise, I only have an older AMD FX CPU, so I can only test
>> whether it is not broken there.
>>
> 
> That is actually the important test. I tested myself on Ryzen 1700X.

I was able to test on a Kabini APU at work, my AMD FX at home still
needs to be tested. The driver loads properly:

[    5.620836] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[    5.621002] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[    5.621611] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=1)

echo "1" >/dev/watchdog rebooted the machine after one minute properly.

You can add my Tested-by: line.

Best regards,
Zoltan Boszormenyi

      reply	other threads:[~2018-01-10  8:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-24 21:04 [PATCH 00/12] watchdog: sp5100_tco: Various improvements Guenter Roeck
2017-12-24 21:04 ` [PATCH 01/12] watchdog: sp5100_tco: Always use SP5100_IO_PM_{INDEX_REG,DATA_REG} Guenter Roeck
2017-12-24 21:04 ` [PATCH 02/12] watchdog: sp5100_tco: Fix watchdog disable bit Guenter Roeck
2017-12-24 21:04 ` [PATCH 03/12] watchdog: sp5100_tco: Use request_muxed_region where possible Guenter Roeck
2018-01-16 19:44   ` [03/12] " Lyude Paul
2018-01-16 20:16     ` Guenter Roeck
2017-12-24 21:04 ` [PATCH 04/12] watchdog: sp5100_tco: Use standard error codes Guenter Roeck
2018-01-16 19:46   ` [04/12] " Lyude Paul
2017-12-24 21:04 ` [PATCH 05/12] watchdog: sp5100_tco: Clean up sp5100_tco_setupdevice Guenter Roeck
2018-01-16 19:55   ` [05/12] " Lyude Paul
2018-01-16 20:22     ` Guenter Roeck
2018-01-17  1:28       ` Guenter Roeck
2017-12-24 21:04 ` [PATCH 06/12] watchdog: sp5100_tco: Match PCI device early Guenter Roeck
2018-01-16 19:58   ` [06/12] " Lyude Paul
2017-12-24 21:04 ` [PATCH 07/12] watchdog: sp5100_tco: Use dev_ print functions where possible Guenter Roeck
2018-01-16 20:00   ` [07/12] " Lyude Paul
2017-12-24 21:04 ` [PATCH 08/12] watchdog: sp5100_tco: Clean up function and variable names Guenter Roeck
2018-01-16 20:05   ` [08/12] " Lyude Paul
2017-12-24 21:04 ` [PATCH 09/12] watchdog: sp5100_tco: Convert to use watchdog subsystem Guenter Roeck
2017-12-24 21:04 ` [PATCH 10/12] watchdog: sp5100_tco: Use bit operations Guenter Roeck
2017-12-24 21:04 ` [PATCH 11/12] watchdog: sp5100-tco: Abort if watchdog is disabled by hardware Guenter Roeck
2018-01-09 22:58   ` [11/12] " Lyude Paul
2018-01-09 23:37     ` Guenter Roeck
2018-01-09 23:58       ` Gabriel C
2018-01-10  0:05         ` Guenter Roeck
2018-01-10  1:26           ` Gabriel C
2018-01-10  2:09             ` Guenter Roeck
2018-01-10  2:41               ` Gabriel C
2018-01-10  5:02                 ` Guenter Roeck
2018-01-10  0:04       ` Lyude Paul
2018-01-10  0:11         ` Guenter Roeck
2018-01-10  0:30           ` Lyude Paul
2017-12-24 21:04 ` [PATCH 12/12] watchdog: sp5100_tco: Add support for recent FCH versions Guenter Roeck
     [not found]   ` <9bac4f60-e385-fef8-0a8f-7a473b079055@pr.hu>
2018-01-04 19:21     ` Guenter Roeck
2018-01-10  8:34       ` Boszormenyi Zoltan [this message]

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=d5184137-e909-9fc5-aa12-a551924c4241@pr.hu \
    --to=zboszor@pr.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lyude@redhat.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

all inboxes | Powered by JetHome®