[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHh0gOi3b+CKMVLwQQxJ+n2XOseirJ6cFhLOVX_BboN9rzM5Jw@mail.gmail.com>
Date: Sat, 23 Feb 2013 15:14:32 +0900
From: Tanaka Takahisa <mc74hc00@...il.com>
To: Joseph Salisbury <joseph.salisbury@...onical.com>
Cc: Joseph Salisbury <josephtsalisbury@...il.com>,
Wim Van Sebroeck <wim@...ana.be>,
linux-watchdog@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Kernel Team <kernel-team@...ts.ubuntu.com>
Subject: Re: [v3.8 Regression] watchdog: sp5100_tco: Add SB8x0 chipset support
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@...onical.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists