From: Guenter Roeck <linux@roeck-us.net> To: Boszormenyi Zoltan <zboszor@pr.hu> 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 06:32:37 -0700 [thread overview] Message-ID: <0b32728a-f545-be43-2870-94688f1f9da5@roeck-us.net> (raw) In-Reply-To: <efce69fc-3899-43f4-c8ee-12b78a571e5a@pr.hu> On 04/01/2017 03:13 AM, Boszormenyi Zoltan wrote: > 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. > Just because you don't want to check for errors ? I am not on favor of your new solution. I think it violates layering all over the place, and I dislike the idea of having a global mutex as you propose. I won't shut it down, but I'll let others provide feedback on your new series of patches. Guenter > 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 >
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org> To: Boszormenyi Zoltan <zboszor-v1d7l9VOqKc@public.gmane.org> Cc: Paul Menzel <paulepanter-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>, Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>, Christian Fetzer <fetzer.ch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Jean Delvare <jdelvare-IBi9RG/b67k@public.gmane.org>, linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-watchdog-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, 853122-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org, Wim Van Sebroeck <wim-IQzOog9fTRqzQB+pC5nmwQ@public.gmane.org>, Tim Small <tim-v0yPK6tSSg/10XsdtD+oqA@public.gmane.org>, Nehal Shah <nehal-bakulchandra.shah-5C7GfCeVMHo@public.gmane.org>, Mika Westerberg <mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>, Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>, Thomas Brandon <tbrandonau-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>, Eddi De Pieri <eddi-soWH+0lSOSbR7s880joybQ@public.gmane.org>, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 06:32:37 -0700 [thread overview] Message-ID: <0b32728a-f545-be43-2870-94688f1f9da5@roeck-us.net> (raw) In-Reply-To: <efce69fc-3899-43f4-c8ee-12b78a571e5a-v1d7l9VOqKc@public.gmane.org> On 04/01/2017 03:13 AM, Boszormenyi Zoltan wrote: > 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. > Just because you don't want to check for errors ? I am not on favor of your new solution. I think it violates layering all over the place, and I dislike the idea of having a global mutex as you propose. I won't shut it down, but I'll let others provide feedback on your new series of patches. Guenter > 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 > -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-04-01 13:32 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <1485728348.3220.10.camel@googlemail.com> 2017-03-03 8:46 ` [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Paul Menzel 2017-03-03 8:46 ` Paul Menzel 2017-03-03 8:46 ` Bug#853122: " Paul Menzel 2017-03-03 10:17 ` Wolfram Sang 2017-03-31 7:17 ` Paul Menzel 2017-03-31 7:17 ` Paul Menzel 2017-03-31 12:49 ` Guenter Roeck 2017-03-31 12:49 ` Guenter Roeck 2017-03-31 14:46 ` Bug#853122: " Boszormenyi Zoltan 2017-03-31 15:05 ` Guenter Roeck 2017-03-31 15:05 ` Guenter Roeck 2017-04-01 10:13 ` Boszormenyi Zoltan 2017-04-01 10:13 ` Boszormenyi Zoltan 2017-04-01 13:32 ` Guenter Roeck [this message] 2017-04-01 13:32 ` Guenter Roeck 2017-04-01 16:20 ` Bug#853122: " Boszormenyi Zoltan 2017-04-01 16:20 ` Boszormenyi Zoltan 2017-04-01 16:31 ` Boszormenyi Zoltan 2017-04-03 6:34 ` Paul Menzel 2017-04-03 6:34 ` Paul Menzel 2017-04-03 7:59 ` Boszormenyi Zoltan 2017-04-03 7:59 ` Boszormenyi Zoltan 2017-06-27 11:52 ` 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=0b32728a-f545-be43-2870-94688f1f9da5@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.