From: Boszormenyi Zoltan <zboszor@pr.hu>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Paul Menzel <paulepanter@users.sourceforge.net>,
Wolfram Sang <wsa@the-dreams.de>,
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: Sat, 1 Apr 2017 12:13:08 +0200 [thread overview]
Message-ID: <efce69fc-3899-43f4-c8ee-12b78a571e5a@pr.hu> (raw)
In-Reply-To: <20170331150524.GA31555@roeck-us.net>
2017-03-31 17:05 keltezéssel, Guenter Roeck írta:
> On Fri, Mar 31, 2017 at 04:46:02PM +0200, Boszormenyi Zoltan wrote:
>> 2017-03-31 14:49 keltezéssel, Guenter Roeck írta:
>>> request_muxed_region() can fail, and literally every other driver
>>> using it checks for that failure. Please do the same.
>>
>> In what circumstances can request_muxed_region() fail? As far as
>> I can see, only if two drivers use the same I/O port base and the
>> already present region did not use IORESOURCE_MUXED which is
>> not the case here. When request_muxed_region() is used consistently,
>> subsequent requests are put on a wait queue and the first one is
>> woken up when the region is released. So, it's basically a mutex.
>> Am I missing something here?
>>
>
> Yes. failure to allocate the resource is one.
So, a common mutex should be used.
I have also added synchronization to the USB PCI quirks code and
have split the patch into three pieces now (USB quirks, i2c-piix4 and
sp5100_tco) and they were sent to the relevant mailing lists.
I don't know which subsystem wants to take it, all 3 patches are
needed at once.
Best regards,
Zoltán Böszörményi
next prev parent reply other threads:[~2017-04-01 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1485728348.3220.10.camel@googlemail.com>
2017-03-03 8:46 ` Paul Menzel
2017-03-03 10:17 ` Wolfram Sang
2017-03-31 7:17 ` Paul Menzel
2017-03-31 12:49 ` Guenter Roeck
[not found] ` <d1152062-77c5-f1b7-6be9-d24ee221ada9@pr.hu>
2017-03-31 15:05 ` Guenter Roeck
2017-04-01 10:13 ` Boszormenyi Zoltan [this message]
2017-04-01 13:32 ` Guenter Roeck
[not found] ` <14472f36-3c8d-e77d-4077-bd0db3587281@pr.hu>
2017-04-01 16:31 ` Boszormenyi Zoltan
2017-04-03 6:34 ` Paul Menzel
2017-04-03 7:59 ` Boszormenyi Zoltan
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=efce69fc-3899-43f4-c8ee-12b78a571e5a@pr.hu \
--to=zboszor@pr.hu \
--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=paulepanter@users.sourceforge.net \
--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
all inboxes | Powered by JetHome®