10 Sep, 2010

1 commit


12 May, 2010

1 commit

  • The work queue has to be flushed after the device has been made
    inaccessible. The patch closes a window during which a work queue might
    remain active after the device is removed and would then lead to ACPI
    calls with undefined behavior.

    Signed-off-by: Oliver Neukum
    Acked-by: Eric Piel
    Acked-by: Pavel Machek
    Cc: Pavel Herrmann
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Oliver Neukum
     

25 Apr, 2010

1 commit


29 Oct, 2009

3 commits

  • I have an HP HDX 18 laptop, and noted that the configuration of the
    accelerometer needs to be x_inverted.

    Signed-off-by: Ian E. Morgan
    Signed-off-by: Éric Piel
    Cc: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ian E. Morgan
     
  • Correct orientation for HP EliteBook 8530w.

    Reported-by: Jörgen Jonssson
    Signed-off-by: Éric Piel
    Cc: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Éric Piel
     
  • I have learned that the 6730b and 6730s have different accelerometer
    orientation, and have modified the driver accordingly (diff attached),
    while dropping the wild guess for AMD based 6735 having the same
    orientation as Intel based 6730 (this is not true for any other related
    series/family, thus is not probable for 673x).

    Signed-off-by: Pavel Herrmann
    Signed-off-by: Éric Piel
    Cc: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Herrmann
     

17 Jun, 2009

3 commits

  • Separate the 6710 and 6715, and set the right axis information for the
    6715.
    Reported-by: Isaac702

    Add the 6930.
    Reported-by: Christian Weidle

    Add the 2710.
    Reported-by: Pavel Herrmann

    Signed-off-by: Eric Piel
    Signed-off-by: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Piel
     
  • Now that there is no need to hookup on the open/close of the joystick,
    it's possible to use the simplified interface input_polled_device, instead
    of creating our own kthread.

    [randy.dunlap@oracle.com: fix Kconfig]
    [randy.dunlap@oracle.com: fix Kconfig some more]
    Signed-off-by: Eric Piel
    Signed-off-by: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Piel
     
  • After measurement on my laptop, it seems that turning off the device does
    not bring any energy saving (within 0.1W precision). So let's keep the
    device always on. It simplifies the code, and it avoids the problem of
    reading a wrong value sometimes just after turning the device on.

    Moreover, since commit ef2cfc790bf5f0ff189b01eabc0f4feb5e8524df had been
    too zealous, the device was actually never turned off anyway. This patch
    also restores the damages done by this commit concerning the
    initialisation/poweroff.

    Also do more clean up with the usage of the lis3_dev global variable.

    Signed-off-by: Eric Piel
    Signed-off-by: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Piel
     

14 Apr, 2009

1 commit


01 Apr, 2009

4 commits

  • This solves the dependency between lis3lv02d.[ch] and ACPI specific
    methods. It introduces a ->bus_priv pointer to the device struct which is
    casted to 'struct acpi_device' in the ACIP layer. Changed hp_accel.c
    accordingly.

    Signed-off-by: Daniel Mack
    Acked-by: Pavel Machek
    Acked-by: Eric Piel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daniel Mack
     
  • I have a laptop HP Compaq 8710W, I compiled into my kernel the LIS3LV02DL
    and HP_ACCEL module drivers. While loading it cannot recognize the laptop
    model, so i am sending the necessary information to update the database of
    axis orientations.

    >When the laptop is horizontal the position reported is about 0 for X and Y
    >and a positive value for Z
    Yes, it is about 0,0,1000, the actual reading says: (-17,-26,1018);

    > If the left side is elevated, X increases (becomes positive)
    Yes, X goes toward to positive 1000.

    >If the front side (where the touchpad is) is elevated, Y decreases (becomes negative)
    No, Y goes toward to positive 1000.

    >If the laptop is put upside-down, Z becomes negative
    Yes, the laptop on a table Z gives 1000, and if upsidedown the Z reads
    -1000.

    So in few words the Y axis is inverted.

    Cc: Eric Piel
    Signed-off-by: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Luca Cappa
     
  • Add two more laptops to whitelist.

    Signed-off-by: Michal Marek
    Signed-off-by: Pavel Machek
    Cc: Daniel Mack
    Cc: Eric Piel
    Cc: Vladimir Botka
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • As Andrew noted, adev is pretty poor name for symbol being exported.
    Rename it to lis3.

    Signed-off-by: Pavel Machek
    Cc: Eric Piel
    Cc: Vladimir Botka
    Cc:
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     

19 Feb, 2009

3 commits

  • Add support for HP Pavilion dv5.

    Since Intel-based models have an inverted x axis, while AMD-based models
    have an inverted y axis, we introduce a new macro that special-cases axis
    orientation based on two DMI entries: HP dv5 axis configuration is then
    based on both the PRODUCT and BOARD name.

    Signed-off-by: Giuseppe Bilotta
    Cc: Eric Piel
    Cc: Pavel Machek
    Tested-by: Palatis Tseng
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Giuseppe Bilotta
     
  • Sensors responding with 0x3B to WHO_AM_I only have one data register per
    direction, thus returning a signed byte from the position which is
    occupied by the MSB in sensors responding with 0x3A.

    Since multiple sensors share the reply to WHO_AM_I, we rename the defines
    to better indicate what they identify (family of single and double
    precision sensors).

    We support both kind of sensors by checking for the sensor type on init
    and defining appropriate data-access routines and sensor limits (for the
    joystick) depending on what we find.

    [akpm@linux-foundation.org: coding-style fixes]
    Signed-off-by: Giuseppe Bilotta
    Acked-by: Eric Piel
    Cc: Pavel Machek
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Giuseppe Bilotta
     
  • This adds freefall handling to hp_accel driver. According to HP, it
    should just work, without us having to set the chip up by hand.

    hpfall.c is example .c program that parks the disk when accelerometer
    detects free fall. It should work; for now, it uses fixed 20seconds
    protection period.

    Signed-off-by: Pavel Machek
    Cc: Thomas Renninger
    Cc: Éric Piel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     

06 Feb, 2009

4 commits


16 Jan, 2009

2 commits

  • The LED on HP notebooks is connected through ACPI. That unfortunately
    means that it needs to be delayed by using schedule_work() to avoid
    calling the ACPI interpreter from an invalid context.

    [akpm@linux-foundation.org: use flush_work() rather than sort-of reimplementing it]
    Signed-off-by: Pavel Machek
    Cc: Éric Piel
    Cc: Len Brown
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Pavel Machek
     
  • Move the second part of the HP laptop disk protection functionality (a red
    led) to the same driver. From a purely Linux developer's point of view,
    the led and the accelerometer have nothing related. However, they
    correspond to the same ACPI functionality, and so will always be used
    together, moreover as they share the same ACPI PNP alias, there is no
    other simple to allow to have same loaded at the same time if they are not
    in the same module. Also make it requires the led class to compile and
    update the Kconfig text.

    Signed-off-by: Pavel Machek
    Signed-off-by: Eric Piel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Piel
     

10 Jan, 2009

1 commit

  • The sensor can be accessed via various buses. In particular, SPI, I²C
    and, on HP laptops, via a specific ACPI API (the only one currently
    supported). Separate this latest platform from the core of the sensor
    driver to allow support for the other bus type. The second, and more
    direct goal is actually to be able to merge this part with the
    hp-disk-leds driver, which has the same ACPI PNP number.

    Signed-off-by: Pavel Machek
    Signed-off-by: Eric Piel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Piel