linux-toradex.git/drivers/char/i8k.c, branch v3.0.92

i8k: Integrate with the hwmon subsystem

2011-05-25T18:43:33+00:00

Let i8k create an hwmon class device so that libsensors will expose
the CPU temperature and fan speeds to monitoring applications.

Signed-off-by: Jean Delvare 
Acked-by: Guenter Roeck 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Massimo Dal Zotto

i8k: Avoid lahf in 64-bit code

2011-05-25T18:43:31+00:00

i8k uses lahf to read the flag register in 64-bit code; early x86-64
CPUs, however, lack this instruction and we get an invalid opcode
exception at runtime.
Use pushf to load the flag register into the stack instead.

Signed-off-by: Luca Tettamanti 
Reported-by: Jeff Rickman 
Tested-by: Jeff Rickman 
Tested-by: Harry G McGavran Jr 
Cc: stable@kernel.org
Cc: Massimo Dal Zotto 
Signed-off-by: Jean Delvare

Fix gcc 4.5.1 miscompiling drivers/char/i8k.c (again)

2010-11-15T21:27:06+00:00

The fix in commit 6b4e81db2552 ("i8k: Tell gcc that *regs gets
clobbered") to work around the gcc miscompiling i8k.c to add "+m
(*regs)" caused register pressure problems and a build failure.

Changing the 'asm' statement to 'asm volatile' instead should prevent
that and works around the gcc bug as well, so we can remove the "+m".

[ Background on the gcc bug: a memory clobber fails to mark the function
  the asm resides in as non-pure (aka "__attribute__((const))"), so if
  the function does nothing else that triggers the non-pure logic, gcc
  will think that that function has no side effects at all. As a result,
  callers will be mis-compiled.

  Adding the "+m" made gcc see that it's not a pure function, and so
  does "asm volatile". The problem was never really the need to mark
  "*regs" as changed, since the memory clobber did that part - the
  problem was just a bug in the gcc "pure" function analysis  - Linus ]

Signed-off-by: Jim Bos 
Acked-by: Jakub Jelinek 
Cc: Andi Kleen 
Cc: Andreas Schwab 
Signed-off-by: Linus Torvalds

i8k: Tell gcc that *regs gets clobbered

2010-11-13T17:54:43+00:00

More recent GCC caused the i8k driver to stop working, on Slackware
compiler was upgraded from gcc-4.4.4 to gcc-4.5.1 after which it didn't
work anymore, meaning the driver didn't load or gave total nonsensical
output.

As it turned out the asm(..) statement forgot to mention it modifies the
*regs variable.

Credits to Andi Kleen and Andreas Schwab for providing the fix.

Signed-off-by: Jim Bos 
Cc: Andi Kleen 
Cc: Andreas Schwab 
Signed-off-by: Linus Torvalds

drivers: autoconvert trivial BKL users to private mutex

2010-10-05T13:01:04+00:00

All these files use the big kernel lock in a trivial
way to serialize their private file operations,
typically resulting from an earlier semi-automatic
pushdown from VFS.

None of these drivers appears to want to lock against
other code, and they all use the BKL as the top-level
lock in their file operations, meaning that there
is no lock-order inversion problem.

Consequently, we can remove the BKL completely,
replacing it with a per-file mutex in every case.
Using a scripted approach means we can avoid
typos.

These drivers do not seem to be under active
maintainance from my brief investigation. Apologies
to those maintainers that I have missed.

file=$1
name=$2
if grep -q lock_kernel ${file} ; then
    if grep -q 'include.*linux.mutex.h' ${file} ; then
            sed -i '/include.*/d' ${file}
    else
            sed -i 's/include.*.*$/include /g' ${file}
    fi
    sed -i ${file} \
        -e "/^#include.*linux.mutex.h/,$ {
                1,/^\(static\|int\|long\)/ {
                     /^\(static\|int\|long\)/istatic DEFINE_MUTEX(${name}_mutex);

} }"  \
    -e "s/\(un\)*lock_kernel\>[ ]*()/mutex_\1lock(\&${name}_mutex)/g" \
    -e '/[      ]*cycle_kernel_lock();/d'
else
    sed -i -e '/include.*\/d' ${file}  \
                -e '/cycle_kernel_lock()/d'
fi

Signed-off-by: Arnd Bergmann

procfs: Push down the bkl from ioctl

2010-05-17T01:06:12+00:00

Push down the bkl from procfs's ioctl main handler to its users.
Only three procfs users implement an ioctl (non unlocked) handler.
Turn them into unlocked_ioctl and push down the Devil inside.

v2: PDE(inode)->data doesn't need to be under bkl
v3: And don't forget to git-add the result
v4: Use wrappers to pushdown instead of an invasive and error prone
    handlers surgery.

Signed-off-by: Frederic Weisbecker 
Acked-by: Arnd Bergmann 
Cc: Thomas Gleixner 
Cc: Andrew Morton 
Cc: Ingo Molnar 
Cc: John Kacur 
Cc: KAMEZAWA Hiroyuki 
Cc: Al Viro 
Cc: Alexey Dobriyan

i8k: Add Dell Vostro systems

2009-01-02T18:28:32+00:00

This trivial patch adds support for i8k on the new Dell Vostro models.
I tested it on my Vostro 1400, and it works. It does print a warning
when loading the module:

	i8k: unable to get SMM BIOS version

But I couldn't figure out how to fix that. The module seems to work fine,
anyway...

Signed-off-by: Federico Heinz 
Signed-off-by: Alan Cox 
Signed-off-by: Linus Torvalds

i8k: Enable i8k on Dell Precision Systems

2009-01-02T18:28:32+00:00

Patch to enable i8k on Dell Precisions.

Signed-off-by: Andy Spencer 
Signed-off-by: Alan Cox 
Signed-off-by: Linus Torvalds

i8k: make fan multiplier tunable with a module parameter

2008-05-01T15:04:00+00:00

The i8k driver multiplies the fan speed reported by the BIOS with a factor of
30.  On my Dell Latitude D800, this factor is not required.

I'd suggest to make this configurable.

Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drivers: use non-racy method for proc entries creation

2008-04-29T15:06:22+00:00

Use proc_create()/proc_create_data() to make sure that ->proc_fops and ->data
be setup before gluing PDE to main tree.

Signed-off-by: Denis V. Lunev 
Acked-by: Greg Kroah-Hartman 
Cc: Alexey Dobriyan 
Cc: "Eric W. Biederman" 
Acked-by: Dmitry Torokhov 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds