VT6307 datasheet(40/54 Pages) VIA

40 / 54 page

VT6307 PCI 1394a Host Controller

Revision 1.2 October 1, 2002

-34-

Technologies, Inc.

We Connect

Isochronous Transmit Context Registers

Offset 200 (Set), 204 (Clr) – Isoch Xmit Context 0 ........ RW

Offset 210 (Set), 214 (Clr) – Isoch Xmit Context 1 ........ RW

Offset 220 (Set), 224 (Clr) – Isoch Xmit Context 2 ........ RW

Offset 230 (Set), 234 (Clr) – Isoch Xmit Context 3 ........ RW

Offset 240 (Set), 244 (Clr) – Isoch Xmit Context 4 ........ RW

Offset 250 (Set), 254 (Clr) – Isoch Xmit Context 5 ........ RW

Offset 260 (Set), 264 (Clr) – Isoch Xmit Context 6 ........ RW

Offset 270 (Set), 274 (Clr) – Isoch Xmit Context 7 ........ RW

These

registers

are

the

Context

Control registers for

isochronous Transmit Contexts 0-7. Each context consists of

two registers:

a Command Pointer and a Context Control

controller where the context program begins.

The Context

Control register controls the context’s behavior and indicates

current status. The bit layout for the Context Control registers

is given below:

31-30 Reserved

........................................ always reads 0

Cycle Match Enable

In general, when set to one the context will begin

running only when the 13-bit “Cycle Match” field

matches the 13-bit “Cycle Count” in the Cycle Start

packet. The effects of this bit however are impacted

by the values of other bits in this register. Once the

context

becomes

active,

this

bit

cleared

automatically by the chip.

28-16 Cycle Match

Contains a 13-bit value corresponding to the 13-bit

“Cycle Count” field. If the “Cycle Match Enable” bit

is set, this ITDMA context will become enabled for

transmits when the bus cycle time “Cycle Count”

value equals the value in this field.

Run

This bit is set and cleared by software to enable

descriptor processing for a context.

The chip will

clear this bit automatically on a hardware or software

reset. Before software sets this bit, the active bit must

be clear and the Command Pointer register for the

context must contain a valid descriptor block address

and a Z value that is appropriate for the descriptor

block address.

Software may stop the chip from further processing of

a context by clearing this bit. When cleared, the chip

will stop processing of the context in a manner that

will not impact the operation of any other context or

DMA controller.

This may require a significant

amount of time. If software clears a run bit while the

chip is processing a packet for the context, it will

continue to receive or transmit the packet and update

the descriptor status.

It will then stop at the

conclusion of that packet.

Clearing the bit may have other side effects that are

DMA controller dependent. This is described in the

sections that cover each of the DMA controllers.

14-13 Reserved

........................................ always reads 0

Wake

..............................................default = 0

When software adds to a list of descriptors for a

context, the chip may have already read the descriptor

that was at the end of the list before it was updated.

This bit provides a semaphore to indicate that the list

may have changed.

If the chip had fetched a descriptor and the indicated

branch address had a Z value of zero, it will reread

the pointer value when the wake bit is set. If, on the

reread, the Z value is still zero, then the end of the list

has been reached and the chip will clear the active bit.

If, however, the Z value is now non-zero, the chip

will continue processing. If the wake bit is set while

the chip is active and has a Z value of non-zero, it

takes no special action.

The chip will clear this bit before it reads or rereads a

descriptor. The wake bit should not be set while the

run bit is zero.

Dead

..............................................default = 0

This bit is set by the chip to indicate a fatal error in

processing a descriptor. When set, the active bit is

cleared. This bit is cleared when software clears the

run bit or on a hardware or software reset.

Active

..............................................default = 0

This bit is set by the chip when software sets the run

bit or sets the wake bit while the run bit is set. The

chip will clear this bit:

when a branch is indicated by a descriptor but

the Z value of the branch address is 0

when software clears the run bit and the chip

has reached a safe stopping point

while the dead bit is set

after a hardware or software reset

When this bit is cleared and the run bit is clear, the

chip will set the Interrupt Event bit for the context.

9-5

Reserved

........................................always reads 0

4-0

Ack / Err Code ..........................................default = 0

Following an “Output Last” command, the received

“Ack Code” or “Event Error Code” is indicated in

this field.

Possible values are:

“Ack Complete”,

“Ack Pending”, Ack Busy X”, “Ack Data Error”,

“Ack Type Error”, “Event Tcode Error”, “Event

Missing Ack”, “Event Underrun”, “Event Descriptor

Read”, “Event Data Read”, “Event Timeout”, “Event

Flushed”, and “Event Unknown” (see “Table 6.

Packet Event Codes” on the previous page for

descriptions and values for these codes).

Offset 20C – Isoch Xmit Context 0 Command Ptr ......... RW

Offset 21C – Isoch Xmit Context 1 Command Ptr ......... RW

Offset 22C – Isoch Xmit Context 2 Command Ptr ......... RW

Offset 23C – Isoch Xmit Context 3 Command Ptr ......... RW

Offset 24C – Isoch Xmit Context 4 Command Ptr ......... RW

Offset 25C – Isoch Xmit Context 5 Command Ptr ......... RW

Offset 26C – Isoch Xmit Context 6 Command Ptr ......... RW

Offset 27C – Isoch Xmit Context 7 Command Ptr ......... RW

VT6307 датащи(PDF) 40 Page - VIA Technologies, Inc.

VT6307 датащи(HTML) 40 Page - VIA Technologies, Inc.

Html Pages

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

датащи скачать

ссылки URL