note naming convention deviation in xous-ticktimer

all other functions have a .init() routine that handles interrupt
binding.

ticktimer rolls that into a routine that also resets the time
of the ticktimer. A comment is added for maintaner sanity down
the road.
This commit is contained in:
bunnie 2023-07-16 17:37:46 +08:00
parent 95239eb05f
commit 11155df21c
2 changed files with 2 additions and 2 deletions

View file

@ -47,7 +47,7 @@ fn main() -> ! {
// Create a new ticktimer object
let mut ticktimer = XousTickTimer::new(ticktimer_client);
ticktimer.reset(); // make sure the time starts from zero
ticktimer.reset(); // make sure the time starts from zero; also maps interrupts (note HAL convention deviation, this combines .init() into a single call).
// register a suspend/resume listener
#[cfg(not(target_arch = "arm"))]

View file

@ -101,7 +101,7 @@ impl XousTickTimer {
pub fn clear_last_response(&mut self) {
self.last_response = None;
}
/// This combines the functions normally found in .init() into the ticktimer reset routine.
pub fn reset(&mut self) {
if ! self.initialized {
xous::claim_interrupt(