is needed to properly lock chip drivers in memory while anyone uses their
/proc entries. This also brings back compatibility with the 2.4 Linux
kernel.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2784 7894878c-1315-0410-8ee3-d5d059ff63e0
<klh@google.com> received Sept. '04.
No changes by me other than include file path fixups.
Compiles, but will not insmod without i2c-core changes
or stubs to add xxx_nolock() functions.
-----------------
Here you go. I apologize for the fact this code is not integrated
into the lm_sensors package structure and thus will require you to
make various little updates. But I really wanted to get this out
before I'm yanked away again, and am pretty sure you can do it much
faster than I can figure out what needs to be done!
BTW the kernel files are built against 2.4.x where x varies; 18 and 19
should work.
Feel free to clean up anything.
--Ken
On Sat, 18 Sep 2004, Mark Studebaker wrote:
>>> > On Tue, 7 Sep 2004, Mark Studebaker wrote:
>>
>>>> >>sure, send it over.
>>>> >>Sorry for delay, your mail got buried by other mail and just now spotted it.
>>>> >>mds
>>>> >>
>>>> >>Ken Harrenstien wrote:
>>>> >>
>>>
>>>>> >>>It turned out to be a while before I could get back to this, but
>>>>> >>>everything's been working for a while now and I'd like to send in the
>>>>> >>>new pca954x driver.
>>>>> >>>
>>>>> >>>I was looking at the list in the "new_drivers" file -- it *is* kind of
>>>>> >>>intimidating. Since some of the changes affect core i2c files, I was
>>>>> >>>hoping that what I could do to start with is just send you a tar of
>>>>> >>>the modified files in their entirety, or a patch-diff of the changes
>>>>> >>>against the 2.8.7 distribution, so you can scope things out and verify
>>>>> >>>they're on the right track for acceptance. The following files are
>>>>> >>>the ones I've changed so far:
>>>>> >>>
>>>>> >>> New:
>>>>> >>> Documentation/i2c/virtual_i2c
>>>>> >>> drivers/i2c/i2c-virtual.c
>>>>> >>> drivers/sensors/pca954x.c
>>>>> >>> include/linux/i2c-virtual.h
>>>>> >>> Patched:
>>>>> >>> Documentation/Configure.help
>>>>> >>> drivers/i2c/Makefile
>>>>> >>> drivers/i2c/Config.in
>>>>> >>> drivers/i2c/i2c-core.c
>>>>> >>> drivers/sensors/Makefile
>>>>> >>> drivers/sensors/Config.in
>>>>> >>> include/linux/i2c-id.h
>>>>> >>> include/linux/i2c.h
>>>>> >>>
>>>>> >>>
>>>>> >>>I plan to write some additional doc once I know that the code itself
>>>>> >>>is acceptable, and you then can tell me what other files need to be
>>>>> >>>updated.
>>>>> >>>
>>>>> >>>To answer a couple other issues you raised:
>>>>> >>>
>>>>> >>>On Thu, 24 Jun 2004, Mark Studebaker wrote:
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>
>>>>>> >>>>(copying the mailing list, already forwarded the first mail to the list)
>>>>>> >>>>
>>>>>> >>>>First I want to ask whether you are working on kernel 2.4 or 2.6.
>>>>
>>>>> >>>
>>>>> >>>
>>>>> >>>2.4.
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>
>>>>>> >>>>Third, you may not have realized that Khali recently did a (2.4 kernel) pca9540 driver.
>>>>>> >>>>It is in our sensors package. It however doesn't do any of the bootstrapping or
>>>>>> >>>>bus registering either. It may or may not help you.
>>>>
>>>>> >>>
>>>>> >>>
>>>>> >>>I saw it in the 2.8.7 distrib, and used parts of it as a template.
>>>>> >>>The pca954x driver will support that chip, although the external /proc
>>>>> >>>interface it presents is necessarily different.
>>>>> >>>
>>>>> >>>--Ken
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2765 7894878c-1315-0410-8ee3-d5d059ff63e0
> Building (the real) 2.8.8 on RH7.3 uncovered a small C99-ism, patch
> against CVS is attached.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2746 7894878c-1315-0410-8ee3-d5d059ff63e0
* read dynamic VCCP error status for IN7 & IN8 (if we're in that mode)
* unmask #VRDHOT and dynamic VCCP (if we're in that mode) error events
* move 'start monitoring' command to the end of the inits
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2734 7894878c-1315-0410-8ee3-d5d059ff63e0
* VIDs were reading 10x too big - fixed integer magnitude
* enabling smart tach for one fan sometimes disabled it for others -
fixed bit-twiddling during writes
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2689 7894878c-1315-0410-8ee3-d5d059ff63e0
revision should be functionally equivalent with the previous, except one small
bugfix: a typo in one of the smart tach SYSCTL numbers. The unified diff from
this revision to the previous is nearly useless - sorry, it can't be helped.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2672 7894878c-1315-0410-8ee3-d5d059ff63e0
* reading #VRDHOT inputs
* reading GPIO pins (input only for now)
* reading alarms status
* #PROCHOT override control
* #PROCHOT sampling interval control
* Manual PWM output control
* PWM output frequency control
Also, some whitespace cleanup in the driver.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2660 7894878c-1315-0410-8ee3-d5d059ff63e0
Here is a small patch that fixes the setting of limits on the temp2 sensors
in the MTP008 chip. The code (embarassingly written by myself when I wrote
the MTP008 chip driver a long time ago) would always update the hyst and max
limits of the first temp sensor, even when you tried to set it for the 2nd
or 3rd sensors.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2649 7894878c-1315-0410-8ee3-d5d059ff63e0
Drop unneeded variable.
Refine detection using status registers.
Update limit registers again.
Init high limits if they read 0.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2619 7894878c-1315-0410-8ee3-d5d059ff63e0
Mark D. Studebaker