[android-porting] Re: sensors HAL limitation

2009-01-29 Thread Ken Schultz
So essentially the other drivers would register to the input driver but never write to it. They would need to register so that the framework would can the poll function. And the driver that is the owner of the /dev/input/event# being used would need to set all the input_set_abs_params(,

[android-porting] Re: sensors HAL limitation

2009-01-29 Thread Ken Schultz
Correction. The other drivers would register to the input driver but never write to their own event node. Only the main driver would write to its own event node. On Jan 29, 6:43 pm, Ken Schultz schultz...@gmail.com wrote: So essentially the other drivers would register to the input driver

[android-porting] Re: sensors HAL limitation

2009-01-29 Thread Ken Schultz
The problem I'm running into is how to do this in kernel space. I would suspect you would need to share the input_dev struct between drivers so they each could call input_report_abs on the same input_dev, but since they are separate objects this makes it difficult. Am I missing something simple

[android-porting] Re: sensors HAL limitation

2009-01-29 Thread pramod gurav
On Fri, Jan 30, 2009 at 6:46 AM, Ken Schultz schultz...@gmail.com wrote: The problem I'm running into is how to do this in kernel space. I would suspect you would need to share the input_dev struct between drivers so they each could call input_report_abs on the same input_dev, but since