From: Guenter Roeck <linux@roeck-us.net>
To: Paul Menzel <paulepanter@users.sourceforge.net>,
Wolfram Sang <wsa@the-dreams.de>,
Zoltan Boszormenyi <zboszor@pr.hu>
Cc: Christian Fetzer <fetzer.ch@gmail.com>,
Jean Delvare <jdelvare@suse.com>,
linux-i2c@vger.kernel.org, linux-watchdog@vger.kernel.org,
853122@bugs.debian.org, Wim Van Sebroeck <wim@iguana.be>,
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: Re: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset
Date: Fri, 31 Mar 2017 05:49:50 -0700 [thread overview]
Message-ID: <585a27fb-be15-df9f-00a9-bd4c3a654142@roeck-us.net> (raw)
In-Reply-To: <1490944639.2653.182.camel@users.sourceforge.net>
Hi Paul,
On 03/31/2017 12:17 AM, Paul Menzel wrote:
> Dear Wolfram,
>
>
> Thank you for the reply, which we talked about briefly at the
> Chemnitzer LinuxTage.
>
>
> Am Freitag, den 03.03.2017, 11:17 +0100 schrieb Wolfram Sang:
>>> 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.
>>
>> Jean Delvare pointed out this issue amongst others[1] last year already.
>> Let me quote:
>>
>> ===
>>
>> 5* The I/O ports used for SMBus configuration and port switching are
>> also needed by a watchdog driver, sp5100_tco. Both drivers request the
>> region, so the first one wins, and the other driver can't be loaded.
>> sp5100_tco was there first, so the changes done to the i2c-piix4 driver
>> recently will cause a regression for some users by preventing them
>> from using the sp5100_tco and i2c-piix4 drivers at the same time. In
>> the long run I guess we will need a helper module to handle this shared
>> resource. Unless IORESOURCE_MUXED can be used for that. Either way,
>> that's more work than I can put into this before kernel v4.5 is
>> released. For the time being, I think we should simply make it
>> non-fatal if the I/O ports can't be requested, and continue without
>> multiplexing (as before.)
>>
>> ===
>>
>> Seems nobody had the resources, so far.
>
> I still don’t understand, why Jean then not immediately reverted the
> commit to adhere to the Linux Kernel’s no-regression-policy.
>
>> I don't have the HW and not much experience with non-embedded
>> platforms. I wonder, though, if we really need to convert the drivers
>> to MFD ones, or if we could use the simpler MFD_SYSCON mechanism
>> which helps in exactly such cases for embedded platforms. But I am
>> really lacking details here and am afraid this is probably all the
>> input I can give currently.
>
> Zoltan stepped up, and uploaded a patch for review to the Kernel.org
> Bugzilla [2], also attached to this message.
>
Please don't send patches as attachments.
request_muxed_region() can fail, and literally every other driver
using it checks for that failure. Please do the same.
The sp5100_tco_dev_name change in the watchdog driver is unnecessary.
There are some unnecessary { } in the watchdog driver after the patch
is applied.
Please split the patch into two patches so they can be reviewed and
applied separately.
Thanks,
Guenter
next prev parent reply other threads:[~2017-03-31 12:49 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 ` Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Paul Menzel
2017-03-03 10:17 ` Wolfram Sang
2017-03-31 7:17 ` Paul Menzel
2017-03-31 12:49 ` Guenter Roeck [this message]
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=585a27fb-be15-df9f-00a9-bd4c3a654142@roeck-us.net \
--to=linux@roeck-us.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=mika.westerberg@linux.intel.com \
--cc=nehal-bakulchandra.shah@amd.com \
--cc=paulepanter@users.sourceforge.net \
--cc=tbrandonau@gmail.com \
--cc=tim@seoss.co.uk \
--cc=wim@iguana.be \
--cc=wsa@the-dreams.de \
--cc=zboszor@pr.hu \
/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).