linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tanaka Takahisa <mc74hc00@gmail.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Joseph Salisbury <josephtsalisbury@gmail.com>,
	Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Kernel Team <kernel-team@lists.ubuntu.com>
Subject: Re: [v3.8 Regression] watchdog: sp5100_tco: Add SB8x0 chipset support
Date: Sat, 23 Feb 2013 15:14:32 +0900	[thread overview]
Message-ID: <CAHh0gOi3b+CKMVLwQQxJ+n2XOseirJ6cFhLOVX_BboN9rzM5Jw@mail.gmail.com> (raw)
In-Reply-To: <5126B617.6010405@canonical.com>

Hi Joseph,

Thank you for testing!
I will submit this patch to the linux-watchdog community after adding
commit log to patch.

2013/2/22 Joseph Salisbury <joseph.salisbury@canonical.com>:
> The I/O data can be seen at:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116835/+attachment/3540738/+files/iomem.txt

In the case of SP5100 and SB7x0 chipset, the sp5100_tco driver
overwrites a free resource I/O memory address obtained by
allocate_resource() to the MMIO address registers for watchdog timer.
In the case of M3A78-CM, the sp5100_tco driver was using 0xfed45000 as
a MMIO address. Since 0xfed45000 is the free I/O memory resource
address, this is the expected behavior.

  [   18.852540] sp5100_tco: Using 0xfed45000 for watchdog MMIO address

However, Rewriting the MMIO address registers for the watchdog timer
must have generated the problem. I think that the problem has occurred
with the chipset or the BIOS layer. So, It's difficult for me to
investigate the problem, and the problem is critical. Thus, I decided
to delete the concerned codes.


Regards,
Takahisa

      reply	other threads:[~2013-02-23  6:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 16:07 [v3.8 Regression] watchdog: sp5100_tco: Add SB8x0 chipset support Joseph Salisbury
2013-02-15  7:32 ` Wim Van Sebroeck
2013-02-15 14:54   ` Joseph Salisbury
2013-02-17  9:44     ` Tanaka Takahisa
2013-02-18  3:13       ` Joseph Salisbury
2013-02-18  7:26         ` Joseph Salisbury
2013-02-18 17:14           ` Tanaka Takahisa
2013-02-22  0:04             ` Joseph Salisbury
2013-02-23  6:14               ` Tanaka Takahisa [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=CAHh0gOi3b+CKMVLwQQxJ+n2XOseirJ6cFhLOVX_BboN9rzM5Jw@mail.gmail.com \
    --to=mc74hc00@gmail.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=josephtsalisbury@gmail.com \
    --cc=kernel-team@lists.ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).