From 9290bdde588c9c4f0db3cfc3f1e690683c281335 Mon Sep 17 00:00:00 2001 From: Sonya Vasquez Date: Fri, 21 Jun 2024 12:38:20 -0700 Subject: [PATCH] fix harware_alarm_irq_number typo (#1619) --- src/rp2_common/hardware_timer/timer.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/rp2_common/hardware_timer/timer.c b/src/rp2_common/hardware_timer/timer.c index a2bfe89c..836b47ca 100644 --- a/src/rp2_common/hardware_timer/timer.c +++ b/src/rp2_common/hardware_timer/timer.c @@ -106,7 +106,7 @@ void busy_wait_until(absolute_time_t t) { } /// \end::busy_wait[] -static inline uint harware_alarm_irq_number(uint alarm_num) { +static inline uint hardware_alarm_irq_number(uint alarm_num) { return TIMER_IRQ_0 + alarm_num; } @@ -150,7 +150,7 @@ void hardware_alarm_set_callback(uint alarm_num, hardware_alarm_callback_t callb // note this should probably be subsumed by irq_set_exclusive_handler anyway, since that // should disallow IRQ handlers on both cores check_hardware_alarm_num_param(alarm_num); - uint irq_num = harware_alarm_irq_number(alarm_num); + uint irq_num = hardware_alarm_irq_number(alarm_num); spin_lock_t *lock = spin_lock_instance(PICO_SPINLOCK_ID_TIMER); uint32_t save = spin_lock_blocking(lock); if (callback) { @@ -208,7 +208,7 @@ bool hardware_alarm_set_target(uint alarm_num, absolute_time_t target) { timer_hw->intr = 1u << alarm_num; // ... including anything pending on the processor - perhaps unnecessary, but // our timer flag says we aren't expecting anything. - irq_clear(harware_alarm_irq_number(alarm_num)); + irq_clear(hardware_alarm_irq_number(alarm_num)); // and clear our flag so that if the IRQ handler is already active (because it is on // the other core) it will also skip doing anything timer_callbacks_pending = old_timer_callbacks_pending; @@ -238,4 +238,4 @@ void hardware_alarm_force_irq(uint alarm_num) { timer_callbacks_pending |= (uint8_t)(1u << alarm_num); spin_unlock(lock, save); hw_set_bits(&timer_hw->intf, 1u << alarm_num); -} \ No newline at end of file +}