на главную | войти | регистрация | DMCA | контакты | справка | donate |      

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
А Б В Г Д Е Ж З И Й К Л М Н О П Р С Т У Ф Х Ц Ч Ш Щ Э Ю Я


моя полка | жанры | рекомендуем | рейтинг книг | рейтинг авторов | впечатления | новое | форум | сборники | читалки | авторам | добавить



1. A data structure that overlays the memory-mapped control and status registers of the device

The first step in the driver development process is to create a C-style struct that looks just like the memory-mapped registers of your device. This usually involves studying the data book for the peripheral and creating a table of the control and status registers and their offsets. Then, beginning with the register at the lowest offset, start filling out the struct . (If one or more locations are unused or reserved, be sure to place dummy variables there to fill in the additional space.)

An example of such a data structure is shown below. This structure describes the registers in one of the on-chip timer/counter units within the 80188EB processor. The device has three registers, arranged as shown in the TimerCounter data structure below. each register is 16 bits wide and should be treated as an unsigned integer, although one of them, the control register, is actually a collection of individually significant bits.

struct TimerCounter {

 unsigned short count; // Current Count, offset 0x00

 unsigned short maxCountA; // Maximum Count, offset 0x02

 unsigned short _reserved; // Unused Space, offset 0x04

 unsigned short control; // Control Bits, offset 0x06

};

To make the bits within the control register easier to read and write individually, we might also define the following bitmasks:

#define TIMER_ENABLE    0xC000          // Enable the timer.

#define TIMER_DISABLE   0x4000          // Disable the timer.

#define TIMER_INTERRUPT 0x2000          // Enable timer interrupts.

#define TIMER_MAXCOUNT  0x0020          // Timer complete?

#define TIMER_PERIODIC  0x0001          // Periodic timer?


7.2 The Device Driver Philosophy | Programming Embedded Systems in C and C++ | 2. A set of variables to track the current state of the hardware and device driver