In-vehicle development
- This topic has 4 replies, 3 voices, and was last updated 12 years, 9 months ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Home › Forums › MultiConnect OCG › In-vehicle development
Hello. We would like to use this device as a vehicle locator but with 3G connection. Do you think that that is posible?. For example, is the device able to be suspended in such way that being connected to ignition signal of the vehicle when you start the ignition the device also starts up?. is it possible to implement an interrupt driven GPIO input with the mts_io driver?. Thank you very much.
The device could be powered from a vehicle, but currently it can’t be put into suspend mode, it would simply be powered off if the vehicle is off. Also, the mts_io driver doesn’t support interrupt driven GPIO at this point — it exposes a sysfs interface which allows reading and writing of pins from userspace.
Jesse
What is the timetable for implementation of gpio interrupts? The gpio-notify driver implementation as used in other OpenEmbedded devices would be very helpful for our application, as looping to test status of a gpio input is very processor intensive. – k
Unfortunately this isn’t possible with the existing hardware design.
This is something that could possibly be available in future hardware revisions.
We have an application that will require:
1. the ability to count contact-closure events on 4 gpio inputs simultaneously, and counting those whose closure duration is within certain limits, say between 25 and 800 ms.
2. The ability to output a digital signal (a clock) via a PWM on a digital output gpio, and read back on an digital input gpio, data synchronous to the output clock. The maximum clock rate would be 2000Hz.
Can anybody suggest how the above might be done without interrupt driven events on the input gpio pins?