summaryrefslogtreecommitdiff
path: root/usrp/doc/traffic-cop-dma
blob: 0b3c3507e8efe618c0a68a631ca9a8779e987f1f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
Matt,

Here's my idea on the interface to the traffic cop.  Basically I'm
thinking about treating it as 4 separate DMA channels, one for each of
the four possible "flows".  In the interest of simplicity, I think we can
assign buffers 0,1 to channel 0;  2,3 to channel 1, etc...

port assignments
-----------------
  0   SERDES
  1   DSP pipeline
  2   Gigabit ethernet MAC
  3   RAM


registers
---------

  MBZ == Must Be Zero

     3                   2                   1
   1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 


TC_DMA_SRC_{0,3} [WR] ("traffic cop DMA source, channel N")

  (The {0,3} notation means there are four of these registers,
   one for each channel, named TC_DMA_SRC_0, TC_DMA_SRC_1,
   TC_DMA_SRC_2, TC_DMA_3.)

  Specifies where the writing port adapter writes info the buffer, and
  the maximum number of lines to write.

       5             9                  9                9  
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |0|  src  |      start      |     end (max)   |       step      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  src:   source port number.  E.g., 2 = ethernet MAC (the buffer writer)
  start: starting line number for transfer (32-bit lines)
  end:   index of last line to write.  I.e., start = 0, end = 0, xfers 1 line.
  step:  normally 1.


TC_DMA_DST_{0,3} [WR]

  Specifies the range of lines that the reading port adapter accesses.
  The number of lines to be transferred is controlled by the source.

       5             9                  9                9  
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |0|  dst  |      start      |    end (max)    |       step      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  dst:   destination port number.  E.g., 1 = DSP pipeline (the buffer reader)
  start: starting line number tranfer (32-bit lines)
  end:   Must be zero, unless a TC_DMA_CMD_SEND_0 or TC_DMA_CMD_SEND_1
         cmd is written to TC_DMA_CTRL_{0,3} in which case this
         specifies the index of the last line to send to the destination.
  step:  normally 1.


TC_DMA_CTRL_{0,3} [WR]

                            27                           1    4
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                         MBZ                         |A|  cmd  |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


  A:    Set if "Host Approval" is required before beginning xfer to dst.
        Used to allow processor to inspect packet for s/w dispatch.  If set,
	traffic cop sets PENDING_APPROVAL bit (and causes interrupt?) after the
	2nd line has been written into the buffer.   Reader is held off
	until hosts APPROVES or DROPS the buffer.


  cmd:  command

    TC_DMA_CMD_RESET	     0  // abort active tranfers now; reset to idle state
    TC_DMA_CMD_START	     1  // begin transfers according
    TC_DMA_CMD_STOP	     2  // stop transfers at completion of current buffer
    TC_DMA_CMD_APPROVE_0     3  // host approves xfer on even buffer, continue
    TC_DMA_CMD_APPROVE_1     4  // host approves xfer on odd buffer, continue
    TC_DMA_CMD_DROP_0	     5  // host naks xfer on even buffer, drop buffer and continue
    TC_DMA_CMD_DROP_1	     6  // host naks xfer on even buffer, drop buffer and continue
    TC_DMA_CMD_SEND_0	     7  // copy buffer 0 to destination (processor init'd buffer)
    TC_DMA_CMD_SEND_1	     8  // copy buffer 1 to destination (processor init'd buffer)


TC_DMA_STATUS_{0,3} [RD]

           10                  10
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |    nwritten even  |   nwritten odd    |     state?    | flags |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  nwritten even:  number of lines written into even buffer
  nwritten odd:   number of lines written into odd buffer

  flag bits:

    bmTCDS_PENDING_APPROVAL_0	(1 << 0)   // pending host approval on even buffer
    bmTCDS_PENDING_APPROVAL_1	(1 << 1)   // pending host approval on odd buffer
    bmTCDS_WRITE_DONE_0	        (1 << 2)   // the even buffer write is complete
    bmTCDS_WRITE_DONE_1	        (1 << 3)   // the odd buffer write is complete

I think the combination of the "host approval" and WRITE_DONE bits
will allow us to handle the cases where the host looks and doesn't
care, and the case where the host looks, cares, and needs to wait
until it sees the whole packet.

WRITE_DONE_* should be cleared when the corresponding buffer is
selected to be written into (e.g., when swapping buffers, and at init)
prior to writing the first line.  WRITE_DONE_* is set when the
requested number of lines have been written into the buffer.



I also want a "global status register" that pulls the N flag bits
from each of the 4 status registers into a single word.  This should
allow me to read a single word to figure out what to do.


TC_DMA_STATUS_GLOBAL [RD]

  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |     flags3    |     flags2    |     flags1    |     flags0    |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



// some kind of registers to enable and ack interrupts

TC_DMA_INTR_EN  [WR]	  // enable particular interrupts
TC_DMA_INTR_CLR [WR]	  // clear particular pending interrupts