Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Driver for the ST LIS302DL MEMS motion sensor

On 15/03/2013, Jukka Ruohonen <> wrote:
> On Thu, Mar 14, 2013 at 11:43:12PM +0100, Pierre Pronchery wrote:
>> I am not sure what to do next; should I move parts of hpacel(4) to
>> sys/dev/ic/hpacel.c, make sure it still works on ACPI, and then write
>> the i2c glue? Or am I better off working on my own driver separately?
> As the comments in the hpacel(4) say, it is problematic exactly because of
> this.  (The laptop I wrote it for did not provide any information about the
> interrupt source via ACPI, so I couldn't make it function properly.)
> So by all means, if you make this chip work by non-ACPI code, let's use
> that
> and deprecate hpacel(4). You could perhaps still call some auxilliary
> ACPI-methods (like turning a laptop light on when the interrupt is
> registered, etc.).

Supposedly, the i2c controller is hidden on some of those HP laptops:

So, with i2c v. acpi, it might as well be an either-or situation on
that hardware.


Home | Main Index | Thread Index | Old Index