mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Takahisa Tanaka <mc74hc00@gmail.com>
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
	Arkadiusz Miskiewicz <arekm@maven.pl>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Nieder <jrnieder@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sp5100_tco: Add SB8x0 chipset support
Date: Wed, 28 Nov 2012 10:19:28 +0100	[thread overview]
Message-ID: <1354094368.4467.4.camel@mattotaupa> (raw)
In-Reply-To: <1352993009-3448-1-git-send-email-mc74hc00@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]

Dear Takahisa,


as replied to ticket #43176 in Bugzilla thanks a lot for your work.


Am Freitag, den 16.11.2012, 00:23 +0900 schrieb Takahisa Tanaka:
> The current sp5100_tco driver only supports SP5100/SB7x0 chipset, doesn't
> support SB8x0 chipset, because current sp5100_tco driver doesn't know that the
> offset address for watchdog timer was changed from SB8x0 chipset.
> 
> The offset address of SP5100 and SB7x0 chipsets are as follows, quote from the
> AMD SB700/710/750 Register Reference Guide(Page 164) and the AMD SP5100

In English you leave a space before parentheses: … Guide (page 164) …

> Register Reference Guide(Page 166).

Dito.

>   WatchDogTimerControl 69h
>   WatchDogTimerBase0   6Ch
>   WatchDogTimerBase1   6Dh
>   WatchDogTimerBase2   6Eh
>   WatchDogTimerBase3   6Fh
> 
> In contrast, the offset address of SB8x0 chipset is as follows, quote from
> AMD SB800-Series Southbridges Register Reference Guide(Page 147).

Dito.

>   WatchDogTimerEn      48h
>   WatchDogTimerConfig  4Ch
> 
> So, In the case of SB8x0 chipset, sp5100_tco reads meaningless MMIO
> address(for example, 0xbafe00) from wrong offset address, and the following

Dito.

> message is logged.
> 
>    SP5100 TCO timer: mmio address 0xbafe00 already in use
> 
> With this patch, sp5100_tco driver supports SB8x0 chipset, and can avoid
> iomem resource conflict.
> 
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43176
> Tested-by: Arkadiusz Miskiewicz <arekm@maven.pl>
> Signed-off-by: Takahisa Tanaka <mc74hc00@gmail.com>
> 
> ---
> v1 -> v2
>  -Fix typo in module description and source code.
>  -Fix a bug that can't correctly determine the watchdog fired.
>  -Improve syslog messages.
>  -Truncate the commit log, because previous commit log is too long.

There are no too long commit messages. ;-)

> ---
>  drivers/watchdog/sp5100_tco.c | 321 +++++++++++++++++++++++++++++++++++-------
>  drivers/watchdog/sp5100_tco.h |  46 ++++--
>  2 files changed, 306 insertions(+), 61 deletions(-)

[…]

Tested-by: Paul Menzel <paulepanter@users.sourceforge.net>


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2012-11-28  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 15:23 Takahisa Tanaka
2012-11-28  9:19 ` Paul Menzel [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=1354094368.4467.4.camel@mattotaupa \
    --to=paulepanter@users.sourceforge.net \
    --cc=akpm@linux-foundation.org \
    --cc=arekm@maven.pl \
    --cc=bhelgaas@google.com \
    --cc=jrnieder@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mc74hc00@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

all inboxes | Powered by JetHome®