20 Sep, 2008

1 commit


07 Aug, 2008

2 commits


08 Feb, 2008

4 commits

  • In commit f8d0c19a93cea3a26a90f2462295e1e01a4cd250 I forgot to delete
    the pwmN_freq files on driver removal, here's the fix.

    Signed-off-by: Jean Delvare
    Acked-by: Riku Voipio
    Signed-off-by: Mark M. Hoffman

    Jean Delvare
     
  • The new libsensors needs this.

    Signed-off-by: Jean Delvare
    Signed-off-by: Mark M. Hoffman

    Jean Delvare
     
  • Signed-off-by: Jean Delvare
    Signed-off-by: Mark M. Hoffman

    Jean Delvare
     
  • While it is possible to force SMBus-based hardware monitoring chip
    drivers to drive a not officially supported device, we do not have this
    possibility for Super-I/O-based drivers. That's unfortunate because
    sometimes newer chips are fully compatible and just forcing the driver
    to load would work. Instead of that we have to tell the users to
    recompile the kernel driver, which isn't an easy task for everyone.

    So, I propose that we add a module parameter to all Super-I/O based
    hardware monitoring drivers, letting advanced users force the driver
    to load on their machine. The user has to provide the device ID of a
    supposedly compatible device. This requires looking at the source code or
    a datasheet, so I am confident that users can't randomly force a driver
    without knowing what they are doing. Thus this should be relatively safe.

    As you can see from the code, the implementation is pretty simple and
    unintrusive.

    Signed-off-by: Jean Delvare
    Acked-by: Hans de Goede
    Signed-off-by: Mark M. Hoffman

    Jean Delvare
     

22 Jan, 2008

1 commit

  • The IT8705F and related parts are Super I/O controllers that contain
    many separate devices.

    Some BIOSes describe IT8705F I/O port usage under a motherboard device
    (PNP0C02) with overlapping regions, e.g., 0x290-0x29f and 0x290-0x294.

    The it87 driver supports only the Environment Controller, which requires
    only two ISA ports, but it used to request an eight-port range. If that
    range exceeds a range reported by the BIOS, as 0x290-0x297 would, the
    request fails, and the it87 driver cannot claim the device.

    This patch makes the it87 driver request only the two ports used for the
    Environment Controller device.

    Systems where this problem has been reported:
    Gigabyte GA-K8N Ultra 9
    Gigabyte M56S-S3
    Gigabyte GA-965G-DS3

    Kernel bug reports:
    http://bugzilla.kernel.org/show_bug.cgi?id=9514
    http://lkml.org/lkml/2007/12/4/466

    Related change:
    http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a7839e960675b549f06209d18283d5cee2ce9261

    The patch above increases the number of PNP port resources we support.
    Prior to this patch, we ignored some port resources, which masked the
    it87 problem.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Mark M. Hoffman

    Bjorn Helgaas
     

10 Oct, 2007

3 commits


31 Jul, 2007

1 commit

  • On Sun, 22 Jul 2007 00:30:56 +0200, Gabriel C wrote:
    > I noticed this warnings on current git:
    >
    > drivers/hwmon/pc87360.c:1082: warning: 'pc87360_remove' defined but not used
    > drivers/hwmon/sis5595.c:580: warning: 'sis5595_remove' defined but not used
    > drivers/hwmon/smsc47m1.c:608: warning: 'smsc47m1_remove' defined but not used
    > drivers/hwmon/via686a.c:648: warning: 'via686a_remove' defined but not used
    > drivers/hwmon/vt8231.c:755: warning: 'vt8231_remove' defined but not used

    Signed-off-by: Jean Delvare
    Signed-off-by: Mark M. Hoffman

    Jean Delvare
     

20 Jul, 2007

2 commits


15 Feb, 2007

3 commits

  • Cleanup a bogus legacy comment that has been replicated to many
    hardware monitoring drivers.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • Many hardware monitoring drivers use two different mutexes, one to
    protect their per-device data structure, and one to protect the
    access to the device registers. These mutexes are essentially
    redundant, as the drivers are transfering values between the device
    registers and the data cache, so they almost always end up holding
    both mutexes at the same time. Using a single mutex will make the
    code more simple and faster.

    I am changing only two of the affected drivers here, the authors
    of the other affected drivers are welcome to submit similar patches
    if they want.

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • Let the user select the base PWM frequency when using the it87
    hardware monitoring driver. Different frequencies can give better
    control on some fans.

    Also update the documentation to mention the PWM frequency control
    files, with misc cleanups to the PWM section.

    Signed-off-by: Jean Delvare

    Jean Delvare
     

13 Dec, 2006

1 commit

  • This interface was useless as the LPC ISA-like interface is always
    available, is faster, and is more reliable. This cuts the driver
    size by some 20%.

    This change is also required to later convert the it87 driver to a
    platform driver, so that we can get rid of i2c-isa in a near future.

    Signed-off-by: Jean Delvare

    Jean Delvare
     

29 Sep, 2006

9 commits

  • hwmon: Fix unchecked return status, batch 5

    Fix up some hwmon drivers so that they no longer ignore return status
    from device_create_file().

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: Copyright update

    I think my contributions to the it87 driver over the past two
    years qualify me as a co-author of this driver.

    Also drop old comments of dubious usefulness.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: Overwrite broken default limits

    Some IT8716F chips where seen with unreasonable defaults for low
    voltage and high temperature limits. Overwrite them with sane defaults
    so as to not generate meaningless alarms.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: Add support for the IT8718F

    The IT8718F is a Super-I/O chip with integrated hardware monitoring
    functions. It is very similar to the IT8716F, so adding support to the
    it87 driver was pretty straightforward. The most significant difference
    is that the IT8718F has up to 8 VID pins, instead of 6 for the older
    chips.

    For the IT8718F, the VID value can only be read from Super-I/O space.

    Userspace support is already in lm_sensors SVN (to be soon released
    as 2.10.1.)

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: Cleanup set_fan_div

    We only change one fan clock divider at a time, so there is only one
    fan min which needs to be saved and restored.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: in8 has no limit registers

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: Prevent overflow on fan clock divider write

    The highest possible clock divider for fan1 and fan2 is 128.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: No sysfs files for disabled fans

    Only create the fan attributes for enabled fan tachometers. Some
    motherboards have a nice BIOS which only enables the fan inputs which
    are wired to a fan header on the board. This makes the configuration
    easier for the user.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     
  • it87: Add support for the IT8716F

    The IT8716F is a Super-I/O chip with integrated hardware monitoring
    functions. It is very similar to the IT8712F, so adding support to the
    it87 driver was pretty straightforward. The most significant change here
    is that the IT8716F has 16-bit fan speed counters, so the user no more
    needs to tweak the fan clock dividers to get the best readings.

    Userspace support is already in lm_sensors SVN (to be soon released
    as 2.10.1.)

    Thanks to Stian Oksavik, Olivier Nicolas, Prakash Punnoor and
    Juergen Kilb for testing the early versions of this patch.

    Thanks also to ITE for providing datasheets and answering my questions.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

27 Sep, 2006

1 commit

  • i2c-isa: Restore driver owner

    Commit 2b48716d1d2f2edb1e7cbc5ecf1cb2cb39373e33 back in January
    2006 was a bit overzealous. It removed .owner from all i2c drivers,
    including i2c-isa ones, while they still need it.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

24 Mar, 2006

2 commits

  • "register" is a reserved keyword so using it as a parameter name
    can confuse some compilers, most notably ICC.

    The patch below just renames all occurences to reg which fits the actual
    function declarations.

    Signed-off-by: Darren Jenkins
    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Darren Jenkins
     
  • convert drivers/hwmon/*.c semaphore use to mutexes.

    the conversion was generated via scripts, and the result was validated
    automatically via a script as well.

    all affected hwmon drivers were build-tested.

    Signed-off-by: Ingo Molnar
    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Ingo Molnar
     

14 Feb, 2006

1 commit


07 Feb, 2006

1 commit

  • Only scan I2C address 0x2d. This is the default address and no IT87xxF
    chip was ever seen on I2C at a different address. These chips are
    better accessed through their ISA interface anyway.

    This fixes bug #5889, although it doesn't address the whole class
    of problems. We'd need the ability to blacklist arbitrary I2C addresses
    on systems known to contain I2C devices which behave badly when probed.

    Plan the I2C interface for removal as well. If nobody complains within
    a year, it will confirm my impression that the I2C interface isn't
    actually needed by anyone.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman

    Jean Delvare
     

06 Jan, 2006

4 commits


24 Nov, 2005

1 commit

  • Fix a bug where setting the low fan speed limits will not work if no
    data was ever read through the sysfs interface and the fan clock
    dividers have not been explicitely set yet either. The reason is that
    data->fan_div[nr] may currently be used before it is initialized from
    the chip register values. The fix is to explicitely initialize
    data->fan_div[nr] before using it.

    Bug reported, and fix tested, by Nicolas Mailhot.

    Signed-off-by: Jean Delvare
    Signed-off-by: Greg Kroah-Hartman
    Signed-off-by: Linus Torvalds

    Jean Delvare
     

29 Oct, 2005

3 commits