Scribd
Upload
213 views

Device Drivers For Interrupt Handling: 19.1 Definition

This document discusses device drivers for interrupt handling. It defines interrupts as signals triggered by events that cause the processor to stop executing the current instructions and handle the interrupt. Device drivers for interrupt handling implement functions like startup, shutdown, enabling, disabling, and handling interrupts. There are three main types of interrupts: software interrupts triggered by instructions, internal hardware interrupts from processor errors, and external hardware interrupts from other hardware. Interrupts can be level-triggered, occurring when the interrupt signal is at a certain level, or edge-triggered, occurring on a change in the interrupt signal. Interrupt priorities are managed with higher priority interrupts handled before lower ones. Context switching involves saving the current program context and loading the interrupt service routine context when

Uploaded by

Soundarya Svs
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
213 views

Device Drivers For Interrupt Handling: 19.1 Definition

This document discusses device drivers for interrupt handling. It defines interrupts as signals triggered by events that cause the processor to stop executing the current instructions and handle the interrupt. Device drivers for interrupt handling implement functions like startup, shutdown, enabling, disabling, and handling interrupts. There are three main types of interrupts: software interrupts triggered by instructions, internal hardware interrupts from processor errors, and external hardware interrupts from other hardware. Interrupts can be level-triggered, occurring when the interrupt signal is at a certain level, or edge-triggered, occurring on a change in the interrupt signal. Interrupt priorities are managed with higher priority interrupts handled before lower ones. Context switching involves saving the current program context and loading the interrupt service routine context when

Uploaded by

Soundarya Svs
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

CHAPTER 19

Device Drivers for interrupt Handling


19.1 Definition: Interrupts are signals triggered by some event during the execution of
an instruction stream by the

master processer.

Interrupts can initiated by


(i). Asynchronously: For external hardware devices , resets, power failures...etc.
(ii).Synchronously: For instruction related activates such as system calls or
illegal instructions.
These signals cause the master processer to stop executing the current instruction stream
and start the process of handling the interrupt.
The software that handles interrupts on the master processor and manages interrupt
hardware mechanisms consists of the device drivers for interrupt handling.

Interrupt handling startup: Initialization of the interrupt hardware


(interrupt controller activating interrupts...etc) upon Power on or reset.

Interrupt handling shutdown: Configuring interrupt hardware (interrupt


controller, deactivating interrupts, etc...) into power off state.

Interrupt handling disable: allowing other software to disable active


interrupts on-the-fly( not allowed for non-mask able interrupts(NMIs),which
are interrupts that can be disabled).

Interrupt handling enable: allowing other software to enable inactive


interrupts on-the-fly.

Interrupt handler service: the interrupt handling code itself, which is


executed after the interruption of the main execution stream.

The functions are start up, shutdown, disable, and service functions are
implemented in software usually depends on following criteria:

The types ,numbers, and priority levels of interrupts available

How interrupts are triggered.

The interrupts policies of components within system that trigger


interrupts and the services provided the master CPU processing the
interrupts.

There are three main types of interrupts


(i) Software interrupts
(ii) Internal hard ware interrupts
(iii) external hard ware interrupts

Software interrupts: these interrupts are explicitly triggered internally by some


instruction with in the current

instruction stream being executed by the master

processer.

Internal hard ware interrupts:


these are initiated by some instruction by an event that is a result of a problem
with the current instruction stream being executed by the master processer
because of the features of the hard ware. Such as illegal math operations and
invalid instructions. Interrupts that are raised by some internal event to the master
processer these are also called as exceptions or traps. Exceptions are internally
generated hardware interrupts triggered by errors that are detected by the master
processer during software execution, such as invalid data or a divide by the zero.

External hardware interrupts:


These interrupts are initiated by hardware other than the master CPU. Interrupts
that are raised by external events, the master processer is either wired via an
input pins called an Interrupt Request Level l(IRQ).

Interrupts are triggered in two ways


1. Level Triggered Interrupts:

This is initiated when its IRQ signal is at a certain level (high or low). These
interrupts are processed when the CPU finds a request for a level triggered when
sampling its IRQ line. Such as at the end of processing each instruction.

2. Edge Triggered Interrupts:


These are triggered when a change occurs on the IRQ line (low to high) once
these interrupts latch into the
CPU until processed.

Drawbacks of level and edge triggered interrupts is shown below.


Level triggered interrupt:

triggered,

If the request is being processed and has not been disabled before the next sampling
period, the CPU will try to service the same interrupt again. On the flip side, if the level
triggered interrupt were triggered and then disabled before the CPUs sample period, the
CPU would never note its existence and would therefore never process it.
Edge triggered interrupt:
Edge triggered interrupts could have problems if they share the same IRQ line, if they
triggered in the same manner at about the same time.
Because of these drawbacks a Level triggered interrupts are generally recommended for
interrupts that share IRQ line. Edge triggered interrupts are typically recommended for
interrupts signals that are very short or very long.
At the point of an IRQ of a master processor receives a signal that an interrupt has been
raised, the interrupt is processed by the interrupt handling mechanisms within the
system. These mechanisms are made up of combination of both hardware and software
components.

Fig: Edge- triggered interrupted drawbacks


In terms of hardware, an interrupt controller can be integrated onto a board or
within a processor, to mediate interrupt transactions in conjunction with software.
The interrupt request lines are connected directly to the master processor, and
interrupt transactions are controlled via software and some internal circuitry, such as
registers and \or counters. Interrupts acknowledgment (IACK) is typically handled by the
master processor when an external device triggers an interrupt. With respect to the
external device triggering an interrupt, the interrupts scheme depends on whether that
device can provide an interrupt vector.

19.2 Interrupts Priorities:


There are potentially multiple components on an embedded board that may need
to interrupt requests. Interrupt priorities manages all of the different types of interrupts is
priority-based. That is interrupts starting at level 1 are the highest priority within the
system incrementally from there (2,3,4....).Lowest priority interrupts called as masked,
meaning they are not allowed to trigger when the system is handling a higher priority
interrupt. The interrupt with the highest priority is usually called an NMI.
Several priority schemes are implemented in the various architectures. These models are

Equal single level: Where the latest interrupt to be triggered gets the
CPU.

Static multilevel: where priorities are assigned by a priority encoder and


the interrupt with the highest priority gets the CPU.

Dynamic multilevel: Where priority encoder assigns priorities and the


priorities are reassigned when new interrupt is triggered.

19.3 Context Switching:


It is defined as after the hardware mechanisms have determined which interrupt
to handle and have acknowledged the interrupt, the current instruction stream is halted
and a context switch is performed. The master processer switches from executing the
current instruction stream to another set of instructions. This ternate set of instructions
being executed as the result of an interrupt is the ISR or interrupt handler.
The steps involved in an interrupt in a context switch include stopping the current
programs execution of instructions, saving the context information onto a stack, either
dedicated or shared with other system software, and perhaps the disabling of other
interrupts .after the master processer finishes executing the ISR, it context switches back
to the original instruction stream that had been interrupted, using the context information
guide.

19.4 Interrupt handling and Performance:

The performance of an embedded design is effected by the latencies (delays)


involved with the interrupt-handling scheme. The interrupt latency is essentially the time
from when an interrupt is triggered until its ISR starts executing.
The master CPU, under circumstances, accounts for a lot of overhead for the time
it takes to process the interrupt request and acknowledge the interrupt, obtaining an
interrupt vector and context switching to the ISR.
In the case when a lower priority interrupt is triggered during the processing of a
highest priority interrupt , or a higher priority interrupt is triggered during the processing
of a lower priority interrupt, the interrupt latency for the original lower priority interrupt
increases to include the time in which the higher priority interrupt is handled .

You might also like