7 Commits (218fee80b6cd095ef631ba78be22478b3705fefa)

Author	SHA1	Message	Date
thesupershan	e5000abd93	Merge pull request #1 from thesupershan/lpc1768-us-ticker ... choose which lpc1768 timer to use for us_ticker.c	2018-09-13 11:56:58 -07:00
Aleshandre Diaz	190803ae6a	choose which lpc1768 timer to use for us_ticker.c	2018-09-13 05:57:13 -07:00
Przemyslaw Stekiel	ace821017f	Add implementation of ticker_free() function to CI boards. ... This PR provides implementation of ticker_free() function for the following boards: ARCH_PRO EV_COG_AD3029LZ EV_COG_AD4050LZ K22F K64F K82F KW24D KW41Z LPC546XX NRF51_DK NRF52_DK NUCLEO_F207ZG NUCLEO_F401RE NUCLEO_F429ZI NUCLEO_F746ZG REALTEK_RTL8195AM	2018-08-02 09:48:10 +02:00
Przemyslaw Stekiel	c0ee843d63	Add lp/us ticker_free() functions stub. ... This patch adds only empty stubs of `us_ticker_free()` and `lp_ticker_free()` for all boards where these functions are not implemented.	2018-07-25 08:58:38 +02:00
Mahesh Mahadevan	870600400d	LPC1768: Enable usticker ... Signed-off-by: Mahesh Mahadevan <mahesh.mahadevan@nxp.com>	2018-05-25 12:30:53 -05:00
Martin Kojtal	10ea63b8e7	Ticker: add fire interrupt now function ... fire_interrupt function should be used for events in the past. As we have now 64bit timestamp, we can figure out what is in the past, and ask a target to invoke an interrupt immediately. The previous attemps in the target HAL tickers were not ideal, as it can wrap around easily (16 or 32 bit counters). This new functionality should solve this problem. set_interrupt for tickers in HAL code should not handle anything but the next match interrupt. If it was in the past is handled by the upper layer. It is possible that we are setting next event to the close future, so once it is set it is already in the past. Therefore we add a check after set interrupt to verify it is in future. If it is not, we fire interrupt immediately. This results in two events - first one immediate, correct one. The second one might be scheduled in far future (almost entire ticker range), that should be discarded. The specification for the fire_interrupts are: - should set pending bit for the ticker interrupt (as soon as possible), the event we are scheduling is already in the past, and we do not want to skip any events - no arguments are provided, neither return value, not needed - ticker should be initialized prior calling this function (no need to check if it is already initialized) All our targets provide this new functionality, removing old misleading if (timestamp is in the past) checks.	2017-07-13 12:23:25 +01:00
Christopher Haster	0bad622a16	restructure - Moved targets out to top level ... hal/targets -> targets hal/targets.json -> targets/targets.json	2016-09-30 19:18:09 -05:00