From b20dc8e4d4dc930a6061bb1bae2c38b6777a6e76 Mon Sep 17 00:00:00 2001 From: Rohit Grover Date: Mon, 16 Mar 2015 12:55:10 +0000 Subject: [PATCH] another trivial change to a comment; fixed a typo. --- .../targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/us_ticker.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libraries/mbed/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/us_ticker.c b/libraries/mbed/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/us_ticker.c index fdd634c540..dabb162e1b 100644 --- a/libraries/mbed/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/us_ticker.c +++ b/libraries/mbed/targets/hal/TARGET_NORDIC/TARGET_MCU_NRF51822/us_ticker.c @@ -204,8 +204,8 @@ void us_ticker_set_interrupt(timestamp_t timestamp) /* * The argument to this function is a 32-bit microsecond timestamp for when * a callback should be invoked. On the nRF51, we use an RTC timer running - * at 32kHz to implement a low-power us-ticker. This brings with a problem - * that's rooted in the fact that 1000000 is not a multiple of 32768. + * at 32kHz to implement a low-power us-ticker. This results in a problem + * based on the fact that 1000000 is not a multiple of 32768. * * Going from a micro-second based timestamp to a 32kHz based RTC-time is a * linear mapping; but this mapping doesn't preserve wraparounds--i.e. when