hal/include/HAL/Notifier.hpp

#pragma once

#include <stdint.h>

extern "C"
{
	void* initializeNotifier(void (*process)(uint32_t, void*), void* param, int32_t *status);
	void cleanNotifier(void* notifier_pointer, int32_t *status);
	void* getNotifierParam(void* notifier_pointer, int32_t *status);
	void updateNotifierAlarm(void* notifier_pointer, uint32_t triggerTime, int32_t *status);
	void stopNotifierAlarm(void* notifier_pointer, int32_t *status);
}
Reverting back to static .a files for C++ and fixing lots of other assorted items 2014-05-02 17:54:01 -04:00			`#pragma once`

			`#include <stdint.h>`

			`extern "C"`
			`{`
Rewrite Java Notifier and update Interrupt JNI. Notifier takes advantage of the multi-notifier support now in HAL. Each Notifier is now handled by a separate thread at the JNI level, so one notifier taking longer to process (or being breakpointed) does not stop the other notifiers from running. These threads are configured as daemon threads. In both Notifier and Interrupt JNI, the JNI thread attachment no longer repeatedly calls AttachCurrentThread(). This improves performance but more importantly avoids impacting the Eclipse debugger, which attempts to track each call to AttachCurrentThread() as a separate Java thread. Note: There is currently no way to free an interrupt handler. Repeatedly calling attachInterruptHandler() will result in leaking previous handlers. Change-Id: Ib12e3df88943c03e0269d3906e5b153767139391 2015-12-17 16:19:44 -08:00			`void* initializeNotifier(void (process)(uint32_t, void), void* param, int32_t *status);`
Reverting back to static .a files for C++ and fixing lots of other assorted items 2014-05-02 17:54:01 -04:00			`void cleanNotifier(void* notifier_pointer, int32_t *status);`
Rewrite Java Notifier and update Interrupt JNI. Notifier takes advantage of the multi-notifier support now in HAL. Each Notifier is now handled by a separate thread at the JNI level, so one notifier taking longer to process (or being breakpointed) does not stop the other notifiers from running. These threads are configured as daemon threads. In both Notifier and Interrupt JNI, the JNI thread attachment no longer repeatedly calls AttachCurrentThread(). This improves performance but more importantly avoids impacting the Eclipse debugger, which attempts to track each call to AttachCurrentThread() as a separate Java thread. Note: There is currently no way to free an interrupt handler. Repeatedly calling attachInterruptHandler() will result in leaking previous handlers. Change-Id: Ib12e3df88943c03e0269d3906e5b153767139391 2015-12-17 16:19:44 -08:00			`void* getNotifierParam(void* notifier_pointer, int32_t *status);`
Reverting back to static .a files for C++ and fixing lots of other assorted items 2014-05-02 17:54:01 -04:00			`void updateNotifierAlarm(void* notifier_pointer, uint32_t triggerTime, int32_t *status);`
Rewrite Java Notifier and update Interrupt JNI. Notifier takes advantage of the multi-notifier support now in HAL. Each Notifier is now handled by a separate thread at the JNI level, so one notifier taking longer to process (or being breakpointed) does not stop the other notifiers from running. These threads are configured as daemon threads. In both Notifier and Interrupt JNI, the JNI thread attachment no longer repeatedly calls AttachCurrentThread(). This improves performance but more importantly avoids impacting the Eclipse debugger, which attempts to track each call to AttachCurrentThread() as a separate Java thread. Note: There is currently no way to free an interrupt handler. Repeatedly calling attachInterruptHandler() will result in leaking previous handlers. Change-Id: Ib12e3df88943c03e0269d3906e5b153767139391 2015-12-17 16:19:44 -08:00			`void stopNotifierAlarm(void* notifier_pointer, int32_t *status);`
Reverting back to static .a files for C++ and fixing lots of other assorted items 2014-05-02 17:54:01 -04:00			`}`