Functions
static unsigned int	arch_irq_lock (void)

static void	arch_irq_unlock (unsigned int key)

static bool	arch_irq_unlocked (unsigned int key)

void	arch_irq_disable (unsigned int irq)

void	arch_irq_enable (unsigned int irq)

int	arch_irq_is_enabled (unsigned int irq)

int	arch_irq_connect_dynamic (unsigned int irq, unsigned int priority, void(routine)(const void parameter), const void *parameter, uint32_t flags)

unsigned int	arch_irq_allocate (void)
	Arch-specific hook for allocating IRQs. More...

void	arch_irq_set_used (unsigned int irq)
	Arch-specific hook for declaring an IRQ being used. More...

bool	arch_irq_is_used (unsigned int irq)
	Arch-specific hook for checking if an IRQ is being used already. More...

static bool	arch_is_in_isr (void)

Detailed Description

Function Documentation

◆ arch_irq_allocate()

unsigned int arch_irq_allocate ( void )

#include <include/zephyr/sys/arch_interface.h>

Arch-specific hook for allocating IRQs.

Note: disable/enable IRQ relevantly inside the implementation of such function to avoid concurrency issues. Also, an allocated IRQ is assumed to be used thus a following

See also: arch_irq_is_used() should return true.

Returns: The newly allocated IRQ or UINT_MAX on error.

◆ arch_irq_connect_dynamic()

int arch_irq_connect_dynamic	(	unsigned int	irq,
		unsigned int	priority,
		void()(const void parameter)	routine,
		const void *	parameter,
		uint32_t	flags
	)

#include <include/zephyr/sys/arch_interface.h>

Arch-specific hook to install a dynamic interrupt.

Parameters

irq	IRQ line number
priority	Interrupt priority
routine	Interrupt service routine
parameter	ISR parameter
flags	Arch-specific IRQ configuration flag

Returns: The vector assigned to this interrupt

◆ arch_irq_disable()

void arch_irq_disable ( unsigned int irq )

#include <include/zephyr/sys/arch_interface.h>

Disable the specified interrupt line

Note: : The behavior of interrupts that arrive after this call returns and before the corresponding call to arch_irq_enable() is undefined. The hardware is not required to latch and deliver such an interrupt, though on some architectures that may work. Other architectures will simply lose such an interrupt and never deliver it. Many drivers and subsystems are not tolerant of such dropped interrupts and it is the job of the application layer to ensure that behavior remains correct.