Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #816611
| From | Boszormenyi Zoltan <zboszor@pr.hu> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.kernel, linux.debian.kernel |
| Subject | Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset |
| Date | 2017-04-01 18:40 +0200 |
| Message-ID | <trued-5f3-1@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <tr62d-5Sb-1@gated-at.bofh.it> <tr6lA-6eB-25@gated-at.bofh.it> <troit-1f0-1@gated-at.bofh.it> <trrq1-3jA-3@gated-at.bofh.it> <tru4x-5au-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 3 groups.
2017-04-01 18:20 keltezéssel, Boszormenyi Zoltan írta: > The best clean alternative would be add new resource handling infrastructure. > * Expose the currently static alloc_resource() in kernel/resource.c > With this, driver initialization can allocate the resource once > for the lifetime of the driver and it it fails, (unfinished sentence) then the failure is during driver initialization, not during runtime, possibly days or weeks later. > * Add a new insert_muxed_region() / __insert_muxed_region() function with > different semantics from request_muxed_region() / __request_region(): > 1 Accept a pointer to already allocated resource. > 2 If the conflicting resource doesn't have IORESOURCE_MUXED set, > complain loudly in the syslog but still go into the wait queue. > The conflicting resource also has the name which can be printed > so the inconsistent resource / region usage can be fixed. > We can also just modify the __request_region() semantics, so: > 1 It accepts a pointer to an allocated resource or NULL. > In the second case, the resource is allocated internally and can > still fail. > 2 The above second point. But this may cause an error in code that > expects the old semantics. > > The window for request_muxed_region()+release_region() is so short > that the requested I/O port range would not show up in /proc/ioports. > > All this would be to fix only 3 drivers in a no-error scenario and only > achieving the functionality of a mutex seems to be overkill. > > Another alternative is to revert commit 2fee61d22e606fc99ade9079fda15fdee83ec33e > that caused the regression in sp5100_tco in the first place. > > Best regards, > Zoltán Böszörményi >
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Paul Menzel <paulepanter@users.sourceforge.net> - 2017-03-03 10:00 +0100
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Wolfram Sang <wsa@the-dreams.de> - 2017-03-03 11:30 +0100
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Paul Menzel <paulepanter@users.sourceforge.net> - 2017-03-31 09:30 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Guenter Roeck <linux@roeck-us.net> - 2017-03-31 15:20 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Boszormenyi Zoltan <zboszor@pr.hu> - 2017-03-31 16:50 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Guenter Roeck <linux@roeck-us.net> - 2017-03-31 17:10 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Boszormenyi Zoltan <zboszor@pr.hu> - 2017-04-01 12:20 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Guenter Roeck <linux@roeck-us.net> - 2017-04-01 15:40 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Boszormenyi Zoltan <zboszor@pr.hu> - 2017-04-01 18:30 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Boszormenyi Zoltan <zboszor@pr.hu> - 2017-04-01 18:40 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Paul Menzel <paulepanter@users.sourceforge.net> - 2017-04-03 08:40 +0200
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset Boszormenyi Zoltan <zboszor@pr.hu> - 2017-04-03 10:10 +0200
csiph-web