Concurrent Technologies RCIM, Руководство пользователя

Страница: 43 / 102

Functional Description
3-11
DI
0
and on OUT
3
. It is possible to configure another signal processing
module (say RTC
0
) to drive the interrupts on DI
0
and OUT
3
at the same
time. In this case, the signal that drives the line will be the one with the
strongest amplifier. It is up to the administrator to avoid this condition.
•
You determine which direction a distributed interrupt takes. This means
that on a system where a distributed device resides, it may generate two
interrupts: its local device interrupt (ETI, PIG or RTC) and the distributed
interrupt. There is a separate interrupt vector for each.
It may be desirable to receive both interrupts, but generally only one is
sufficient. By disarming the distributed interrupt, one can prevent that
interrupt from being generated on the local system. By default, a
distributed interrupt is in a disarmed state.
Obtaining RCIM Values
1
There are several methods available for displaying or obtaining RCIM values:
/proc/driver/rcim:
N filesystem (where N starts from zero):
The following files in this filesystem can be viewed (read only unless noted
otherwise):
config
– the RCIM configuration in a form suitable to cut and paste (read/write)
interrupts
– a count of all ETI, DI and RTC interrupts per CPU and in total
status
– miscellaneous RCIM board status and time synchronization
rawregs
– named hex display of all readable RCIM board registers
rtc
– status of the RTCs (run status, count values, etc.)
eti
– status of the ETIs (armed, enabled, etc.)
di
– status of the DI lines (armed, enabled, etc.)
ioctl(2)
system call:
Information about a specific interrupt type can be retrieved by specifying the
appropriate operation with the appropriate device file
mmap
’d into the address
space of the program; for example, ETI_INFO with
/dev/rcim:0/eti1
. Refer
to the
rcim_eti(4)
,
rcim_rtc(4)
and
rcim_distrib_intr(4)
man
pages.
The
RCIM_GET_INFO
operation with the
/dev/rcim:0/rcim
device file
mmap
’d
provides the same information as
/proc/driver/rcim:0/config
.
The
RCIM_GET_ADDR
operation with the
/dev/rcim:0/rcim
device file
mmap
’d provides the virtual and physical address of the RCIM control registers.
The header file
/usr/include/rcim.h
describes the layout of the
information returned by
RCIM_GET_INFO
and
RCIM_GET_ADDR
. Refer to the
rcim(4)
man page.
mmap(2)
system call:
mmap
can be used to map in some or all of the device registers of the RCIM board.
The register layout is in
/usr/include/linux/rcim_ctl.h
and in
Appendix B in this guide.