Datasheet

1394 OHCI Memory-Mapped Register Space
156
March 5 2007 − June 2011SCPS154C
8.37 Physical Request Filter High Register
The physical request filter high set/clear register enables physical receive requests on a per-node basis, and
handles the upper node IDs. When a packet is destined for the physical request context, and the node ID has
been compared against the ARRQ registers, then the comparison is done again with this register. If the bit
corresponding to the node ID is not set to 1b in this register, then the request is handled by the ARRQ context
instead of the physical request context. The node ID comparison is done if the source node is on the same
bus as the controller. Nonlocal bus-sourced packets are not acknowledged unless bit 31 in this register is set
to 1b. See Table 8−29 for a complete description of the register contents.
OHCI register offset: 110h set register
114h clear register
Register type: Read/Set/Clear
Default value: 0000 0000h
BIT NUMBER 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
RESET STATE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
BIT NUMBER 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
RESET STATE 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Table 8−29. Physical Request Filter High Register Description
BIT FIELD NAME TYPE DESCRIPTION
31 physReqAllBusses RSC If bit 31 is set to 1b, then all asynchronous requests received by the controller from nonlocal bus
nodes are accepted. Bit 31 is not cleared by a PRST
.
30 physReqResource62 RSC If bit 30 is set to 1b for local bus node number 62, then physical requests received by the
controller from that node are handled through the physical request context.
29 physReqResource61 RSC If bit 29 is set to 1b for local bus node number 61, then physical requests received by the
controller from that node are handled through the physical request context.
28 physReqResource60 RSC If bit 28 is set to 1b for local bus node number 60, then physical requests received by the
controller from that node are handled through the physical request context.
27 physReqResource59 RSC If bit 27 is set to 1b for local bus node number 59, then physical requests received by the
controller from that node are handled through the physical request context.
26 physReqResource58 RSC If bit 26 is set to 1b for local bus node number 58, then physical requests received by the
controller from that node are handled through the physical request context.
25 physReqResource57 RSC If bit 25 is set to 1b for local bus node number 57, then physical requests received by the
controller from that node are handled through the physical request context.
24 physReqResource56 RSC If bit 24 is set to 1b for local bus node number 56, then physical requests received by the
controller from that node are handled through the physical request context.
23 physReqResource55 RSC If bit 23 is set to 1b for local bus node number 55, then physical requests received by the
controller from that node are handled through the physical request context.
22 physReqResource54 RSC If bit 22 is set to 1b for local bus node number 54, then physical requests received by the
controller from that node are handled through the physical request context.
21 physReqResource53 RSC If bit 21 is set to 1b for local bus node number 53, then physical requests received by the
controller from that node are handled through the physical request context.
20 physReqResource52 RSC If bit 20 is set to 1b for local bus node number 52, then physical requests received by the
controller from that node are handled through the physical request context.
19 physReqResource51 RSC If bit 19 is set to 1b for local bus node number 51, then physical requests received by the
controller from that node are handled through the physical request context.
18 physReqResource50 RSC If bit 18 is set to 1b for local bus node number 50, then physical requests received by the
controller from that node are handled through the physical request context.
17 physReqResource49 RSC If bit 17 is set to 1b for local bus node number 49, then physical requests received by the
controller from that node are handled through the physical request context.
Not Recommended for New Designs