On Tue, Jan 3, 2017 at 8:50 PM, Pali Rohár <pali.rohar@xxxxxxxxx> wrote: > On Tuesday 03 January 2017 19:38:43 Dmitry Torokhov wrote: >> "IIRC both dell-smo8800 and lis3lv02d represent one HW device (that >> ST microelectronics accelerometer) but due to complicated HW >> abstraction and layers on Dell laptops it is handled by two drivers, >> one ACPI and one i2c." >> >> and that is the core of the issue. You have 2 drivers fighting over >> the same device. Fix this and it will all work. > > With my current implementation (which I sent in this patch), they are > not fighting. > > dell-smo8800 exports /dev/freefall (and nothing more) and lis3lv02d only > accelerometer device as lis3lv02d driver does not get IRQ number in > platform data. > >> As far as I can see hp_accel instantiates lis3lv02d and accesses it >> via ACPI methods, can the same be done for Dell? > > No, Dell does not have any ACPI methods. > And as I wrote in ACPI or DMI > is even not i2c address of device, so it needs to be specified in code > itself. And as I wrote there is still a way to provide it without hardcoding on model basis. > Really there is no other way... :-( -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
