Messages in this thread | | | Date | Sun, 01 Mar 2009 13:51:25 -0600 | From | Robert Hancock <> | Subject | Re: lis3's ACPI dependency |
| |
Daniel Mack wrote: > Hi Pavel, Eric, > > are there any plans to free the lis3 driver from its ACPI dependency? > In fact, this device is I2C/SPI connected which the ACPI layer seems to > hide from the driver, but to use it on embedded devices, the bus drivers > must be used directly and the dependeny seems entirely unnecessary > anyway.
If ACPI AML code attempts to access the device (which it obviously does, since we're presumably using the same code to access it), then we cannot be accessing it directly at the same time, otherwise the two will stomp on each other.
> > Also I got the feeling that using a globally exported 'adev' symbol all > over the different layers is not the best practice - I suspect all the > occasions could be solved with private pointers and/or container_of(). > Isn't there any cleanup pending? > > Thanks and best regards, > Daniel >
| |