Re: [RFC] (almost) booting allyesconfig -- please don't poke super-io without request_region

From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Jean Delvare <khali@linux-fr.org>
Cc: Milton Miller <miltonm@bga.com>,
	linuxppc-dev@ozlabs.org, Samuel Ortiz <samuel@sortiz.org>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [RFC] (almost) booting allyesconfig -- please  don't poke super-io without request_region
Date: Fri, 11 Jul 2008 09:27:26 +0200	[thread overview]
Message-ID: <48770B5E.7000308@hhs.nl> (raw)
In-Reply-To: <20080711085246.1ead773b@hyperion.delvare>

Jean Delvare wrote:
> Hi Hans, hi Milton,
> 

<snip>

>> One could make a superio driver, and create sub-devices for the IR, 
>> I2C, floppy, parallel, etc
>> nodes.
> 
> There have been proposals to do this, and this would indeed be a very
> good idea, but unfortunately nobody took the time to implement this
> properly, push it upstream and volunteer to maintain it. The problem is
> that you don't need just a "driver", but a new subsystem, that needs to
> be designed and maintained.
> 

Well, I believe there have been some lightweight superio locking coordinator 
patches been floating around on the lm_sensors list, and I have reviewed them 
and then a new version was done with my issues fixed.

I kinda liked the proposed solution there, it was quite simple, moved all the 
generic superio stuff into generic superio code, and added locking for super io 
access from multiple drivers, what ever happened to those patches?

If were to start using those, we could actually do a request region and then 
never release it, as things should be.

Regards,

Hans