From: Paul Menzel <paulepanter@users.sourceforge.net>
To: Christian Fetzer <fetzer.ch@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>,
Jean Delvare <jdelvare@suse.com>
Cc: linux-i2c@vger.kernel.org, linux-watchdog@vger.kernel.org,
853122@bugs.debian.org, Wim Van Sebroeck <wim@iguana.be>,
Guenter Roeck <linux@roeck-us.net>, Tim Small <tim@seoss.co.uk>,
Nehal Shah <nehal-bakulchandra.shah@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thomas Brandon <tbrandonau@gmail.com>,
Eddi De Pieri <eddi@depieri.net>,
linux-kernel@vger.kernel.org
Subject: Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset
Date: Fri, 03 Mar 2017 09:46:22 +0100 [thread overview]
Message-ID: <1488530782.2457.41.camel@users.sourceforge.net> (raw)
In-Reply-To: <1485728348.3220.10.camel@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 2182 bytes --]
Dear Linux folks,
Unfortunately, commit 2fee61d22e (i2c: piix4: Add support for
multiplexed main adapter in SB800) [1] caused a regression. Tim
reported that to the Linux Kernel Bugtracker as bug #170741 last
September [2], but it looks like the affected subsystems don’t use it.
So I just copy his report in here, and put all the people in CC
mentioned in the commit, the bug report, and in the subsystems
I2C/SMBUS CONTROLLER DRIVERS FOR PC and WATCHDOG DEVICE DRIVERS
mentioned in the file `MAINTAINERS`.
> On the AMD Turion N40L and other related SoCs, the i2c-piix4 driver
> now claims the 0xcd6 ioport, preventing the sp5100_tco watchdog
> driver from loading:
>
> piix4_smbus 0000:00:14.0: SMBus Host Controller at 0xb00, revision 0
> piix4_smbus 0000:00:14.0: Using register 0x2c for SMBus port selection
> piix4_smbus 0000:00:14.0: Auxiliary SMBus Host Controller at 0xb20
> sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05
> sp5100_tco: PCI Vendor ID: 0x1002, Device ID: 0x4385, Revision ID: 0x42
> sp5100_tco: I/O address 0x0cd6 already in use
>
>
> This breaks watchdog operation on existing systems on upgrade and new
> deployments unless the i2c-piix4 driver is blacklisted.
>
> See:
>
> drivers/watchdog/sp5100_tco.c
>
> tco_timer_enable(void)
>
> (SB800_IO_PM_INDEX_REG is defined in drivers/watchdog/sp5100_tco.h)
>
> This is the commit which prevents the watchdog driver from loading:
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2fee61d22e606fc99ade9079fda15fdee83ec33e
>
> See also AMD docs
>
> 45483_sb800_bdg_pub_3.03
>
> Perhaps a fix is to switch both drivers from static to dynamic
> allocation of the IO ports in question, since the watchdog driver
> only accesses the port during initialisation (with backoff/retry
> maybe to avoid races?).
Is there somebody having the resources to implement the dynamic
allocation to solve this regression?
Thanks,
Paul
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2fee61d22e606fc99ade9079fda15fdee83ec33e
[2] https://bugzilla.kernel.org/show_bug.cgi?id=170741
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next parent reply other threads:[~2017-03-03 8:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1485728348.3220.10.camel@googlemail.com>
2017-03-03 8:46 ` Paul Menzel [this message]
2017-03-03 10:17 ` [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Wolfram Sang
2017-03-31 7:17 ` Paul Menzel
2017-03-31 12:49 ` Guenter Roeck
2017-03-31 14:46 ` Bug#853122: " Boszormenyi Zoltan
2017-03-31 15:05 ` Guenter Roeck
[not found] ` <20170331150524.GA31555-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2017-04-01 10:13 ` Boszormenyi Zoltan
[not found] ` <efce69fc-3899-43f4-c8ee-12b78a571e5a-v1d7l9VOqKc@public.gmane.org>
2017-04-01 13:32 ` Guenter Roeck
2017-04-01 16:20 ` Bug#853122: " Boszormenyi Zoltan
2017-04-01 16:31 ` Boszormenyi Zoltan
2017-04-03 6:34 ` Paul Menzel
2017-04-03 7:59 ` Boszormenyi Zoltan
[not found] ` <b42d979b-9172-48ba-dba9-a67d9a143bca-v1d7l9VOqKc@public.gmane.org>
2017-06-27 11:52 ` Boszormenyi Zoltan
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=1488530782.2457.41.camel@users.sourceforge.net \
--to=paulepanter@users.sourceforge.net \
--cc=853122@bugs.debian.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=eddi@depieri.net \
--cc=fetzer.ch@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mika.westerberg@linux.intel.com \
--cc=nehal-bakulchandra.shah@amd.com \
--cc=tbrandonau@gmail.com \
--cc=tim@seoss.co.uk \
--cc=wim@iguana.be \
--cc=wsa@the-dreams.de \
/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).