The ISP1563 is a Peripheral Component Interconnect (PCI)-based, single-chip Universal
Serial Bus (USB) Host Controller. It integrates two Original USB Open Host Controller
Interface (OHCI) cores, one Hi-Speed USB Enhanced Host Controller Interface (EHCI)
core, and four transceivers that are compliant with Hi-Speed USB and Original USB. The
functional parts of the ISP1563 are fully compliant with
Rev. 2.0,Open Host Controller Interface Specification for USB Rev. 1.0a,Enhanced Host
Controller Interface Specification for Universal Serial Bus Rev. 1.0,PCI Local Bus
Specification Rev. 2.2
The integrated high performance USB transceivers allow the ISP1563 to handle all
Hi-Speed USB transfer speed modes: high-speed (480 Mbit/s), full-speed (12 Mbit/s) and
low-speed (1.5 Mbit/s). The ISP1563 provides four downstream ports, allowing
simultaneous connection of USB devices at different speeds.
Universal Serial Bus Specification
, and
PCI Bus Power Management Interface Specification Rev. 1.1
.
The ISP1563 provides downstream port status indicators, green and amber LEDs, to
allow user-rich messages of the Root Hub downstream ports status, without requiring
detailed port information in the internal registers.
The ISP1563 is fully compatible with various operating system drivers, such as Microsoft
Windows standard OHCI and EHCI drivers that are present in Windows XP,
Windows 2000 and Red Hat Linux.
The ISP1563 directly interfaces to any 32-bit, 33 MHz PCI bus. Its PCI pins can source
3.3 V. The PCI interface fully complies with
The ISP1563 is ideally suited for use in Hi-Speed USB host-enabled motherboards,
Hi-Speed USB host PCI add-on card applications, mobile applications, and embedded
solutions.
To facilitate motherboard development, the ISP1563 can use the available 48 MHz clock
signal to reduce the total cost of a solution. To reduce Electro-Magnetic Interference
(EMI), however, it is recommended that the 12 MHz crystal is used in PCI add-on card
designs.
PCI Local Bus Specification Rev. 2.2
.
Philips Semiconductors
2.Features
ISP1563
HS USB PCI Host Controller
■ Complies with
■ Supports data transfer at high-speed (480 Mbit/s), full-speed (12 Mbit/s) and
low-speed (1.5 Mbit/s)
■ Two Original USB OHCI cores comply with
Universal Serial Bus Specification Rev. 2.0
Open Host Controller Interface
Specification for USB Rev. 1.0a
■ One Hi-Speed USB EHCI core complies with
Enhanced Host Controller Interface
Specification for Universal Serial Bus Rev. 1.0
■ Supports PCI 32-bit, 33 MHz interface compliant with
Rev. 2.2
standard
■ Compliant with
hosts (EHCI and OHCI), and supports all power states: D0, D1, D2, D3
■ Four downstream ports with support for downstream port indicator LEDs: amber and
green
■ Configurable two or four port root hubs
■ CLKRUN support for mobile applications, such as internal notebook design
■ Configurable subsystem ID and subsystem Vendor ID through external EEPROM
■ Digital andanalogpower separation forbetter EMI and Electro-Static Discharge (ESD)
protection
■ Supports hot Plug and Play and remote wake-up of peripherals
■ Supports individual power switching and individual overcurrent protection for
downstream ports
■ Supports partial dynamic port-routing capability for downstream ports that allows
sharing of the same physical downstream ports between the Original USB Host
Controller and the Hi-Speed USB Host Controller
■ Supports legacy PS/2 keyboard and mouse
■ Uses 12 MHz crystal oscillator to reduce system cost and EMI emissions
■ Supports dual power supply: PCI V
■ Operates at +3.3 V power supply input
■ Low power consumption
■ Full industrial operating temperature range from −40 °Cto+85°C
■ Full-scan design with high fault coverage (93 % to 95 %) ensures high quality
■ Available in LQFP128 package.
, with support for D3
PCI Bus Power Management Interface Specification Rev. 1.1
83-3.3 V supply voltage; used to power pads; add a 100 nF decoupling
Symbol
REG1V870-1.8 V regulator output voltage; only for voltage conditioning; cannot
AD[8]71I/Obit 8 of multiplexed PCI address and data
C/BE#[0]72I/Obyte 0 of multiplexed PCI bus command and byte enable
GNDA73-analog ground
AD[7]74I/Obit 7 of multiplexed PCI address and data
AD[6]75I/Obit 6 of multiplexed PCI address and data
GNDD76-digital ground
AD[5]77I/Obit 5 of multiplexed PCI address and data
AD[4]78I/Obit 4 of multiplexed PCI address and data
AD[3]79I/Obit 3 of multiplexed PCI address and data
AD[2]80I/Obit 2 of multiplexed PCI address and data
AD[1]81I/Obit 1 of multiplexed PCI address and data
AD[0]82I/Obit 0 of multiplexed PCI address and data
V
GNDA84-analog ground
AUX1V885-1.8 V auxiliary output voltage; only forvoltageconditioning; cannot be
XTAL186AIcrystal oscillator input; this can also be a 12 MHz or 48 MHz clock
XTAL287AOcrystal oscillator output (12 MHz); leave open when clock is used
GNDD88-digital ground
AMB389I/Oamber LED indicator output for the USB downstream port 3; the LED
GRN390Ogreen LED indicator output for the USB downstream port 3; the LED
…continued
be used to supply power to external components; add a 100 nF
decoupling capacitor
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
PCI pad; 3.3 V signaling
capacitor
used to supply power to external components; add a 100 nF
decoupling capacitor
input
is off by default and can be programmed to enable it to blink; input as
port indicator enable during reset; by default, pull up is enabled; if no
LEDs are used, then connect this pin to ground, that is, no port
indicator support
3.3 V bidirectional pad; three-state output; 3 ns slew-rate control;
input; CMOS; open-drain
is off by default and can be programmed to enable it to blink
AMB291Oamber LED indicator output for the USB downstream port 2; the LED
GRN292Ogreen LED indicator output for the USB downstream port 2; the LED
AMB193Oamber LED indicator output for the USB downstream port 1; the LED
GRN194Ogreen LED indicator output for the USB downstream port 1; the LED
V
OC1_N96Iovercurrent sense input for the USB downstream port 1 (digital)
PWE1_N97Opower enable for the USB downstream port 1
GNDA98-analog ground
RREF99AI/Oanalog connection for the external resistor (12 kΩ±1%)
GNDA100-analog ground
DM1101 AI/OD−; analog connection for the USB downstream port 1; leave this pin
GNDA102-analog ground
DP1103 AI/OD+; analog connection for the USB downstream port 1; leave this pin
V
OC2_N105Iovercurrent sense input for the USB downstream port 2 (digital)
PWE2_N106 Opower enable for the USB downstream port 2
GNDA107-analog ground
DM2108 AI/OD−; analog connection for the USB downstream port 2; leave this pin
GNDA109-analog ground
DP2110 AI/OD+; analog connection for the USB downstream port 2; leave this pin
V
OC3_N112Iovercurrent sense input for the USB downstream port 3 (digital)
PWE3_N113 Opower enable for the USB downstream port 3
OC4_N114Iovercurrent sense input for the USB downstream port 4 (digital)
[1]
CC(I/O)_AUX
DDA_AUX
DDA_AUX
PinType Description
95-3.3 V auxiliary supply voltage; used to power pads; add a 100 nF
104 -auxiliary analog supply voltage; add a 100 nF decoupling capacitor
111 -auxiliary analog supply voltage; add a 100 nF decoupling capacitor
…continued
is off by default and can be programmed to enable it to blink
PWE4_N115 Opower enable for the USB downstream port 4
3.3 V output pad; 3 ns slew rate control; CMOS; open-drain
GNDA116-analog ground
DM3117 AI/OD−; analog connection for the USB downstream port 3; leave this pin
open when not in use
GNDA118-analog ground
DP3119 AI/OD+; analog connection for the USB downstream port 3; leave this pin
open when not in use
V
DDA_AUX
120 -auxiliary analog supply voltage; add a 100 nF decoupling capacitor
SEL48M121Iselection between 12 MHz crystal and 48 MHz oscillator:
• LOW: 12 MHz crystal is used
• HIGH: 48 MHz clock is used.
3.3 V input pad; push-pull; CMOS
2
SCL122 I/OI
C-bus clock; pull-up to 3.3 V through a 10 kΩ resistor
I2C-bus pad; clock signal
2
SDA123I/OI
C-bus data; pull-up to 3.3 V through a 10 kΩ resistor
I2C-bus pad; data signal
GNDA124-analog ground
DM4125 AI/OD−; analog connection for the USB downstream port 4; leave this pin
open when not in use
GNDA126-analog ground
DP4127 AI/OD+; analog connection for the USB downstream port 4; leave this pin
open when not in use
V
DDA_AUX
128 -auxiliary analog supply voltage; add a 100 nF decoupling capacitor
[3]
[3]
[1] Symbol names ending with ‘#’, for example, NAME#, represent active LOW signals for PCI pins. Symbol
names ending with underscore N, for example, NAME_N, represent active LOW signals for USB pins.
[2] If legacy support is not used, connect this pin to ground.
[3] Connect to ground if I2C-bus is not used.
An OHCI Host Controller transfers data to devices at the Original USB defined bit rate of
12 Mbit/s or 1.5 Mbit/s.
7.2 EHCI Host Controller
The EHCI Host Controller transfers data to a Hi-Speed USB compliant device at the
Hi-Speed USB defined bit rate of 480 Mbit/s. When the EHCI Host Controller has the
ownership of a port, the OHCI Host Controllers are not allowed to modify the port register.
All additional port bit definitions required for the Enhanced Host Controller are not visible
to the OHCI Host Controller.
7.3 Dynamic port-routing logic
The port-routing feature allows sharing of the same physical downstream ports between
the Original USB Host Controller and the Hi-Speed USB Host Controller. This requirement
of the
Enhanced Host Controller Interface Specification for Universal Serial Bus Rev. 1.0
provides four downstream ports, and these ports are multiplexed with the ports of the two
OHCIs. The first and third downstream ports are always connected to the first OHCI, and
the second and fourth downstream ports are always connected to the second OHCI.
ISP1563
HS USB PCI Host Controller
The EHCI is responsible for the port-routing switching mechanism. Two register bits are
used for ownership switching. During power-on and system reset, the default ownership of
all downstream ports is the OHCI. The Enhanced Host Controller Driver (HCD) controls
the ownership during normal functionality.
7.4 Hi-Speed USB analog transceivers
The Hi-Speed USB analog transceivers directly interface to the USB cables through
integrated termination resistors. These transceivers can transmit and receive serial data
at all data rates: high-speed (480 Mbit/s), full-speed (12 Mbit/s) and low-speed
(1.5 Mbit/s).
7.5 LED indicators for downstream ports
The system designer can program two optional port indicators, a green LED and an
amber LED, to indicate the status of the Host Controller. These port indicators are
implemented according to the USB specification.
All LED indicators are open-drain output.
7.6 Power management
The ISP1563 provides an advanced power management capability interface that is
compliant with
controlled and managed by the interaction between drivers and PCI registers.
PCI Bus Power Management Interface Specification Rev. 1.1
. Power is
For a detailed description on power management, see Section 10.
The ISP1563 provides legacy support for a USB keyboard and mouse. This means that
the keyboard and mouse should be able to work even before the Operating System (OS)
boot-up, with the necessary support in the Basic Input Output System (BIOS).
Section 11.2 provides a detailed description on the legacy support in the ISP1563.
7.8 Phase-Locked Loop (PLL)
A 12 MHz-to-30 MHz and 48 MHz clock multiplier PLL is integrated on-chip. This allows
the use of a low-cost 12 MHz crystal, which also minimizes EMI. No external components
are required for the PLL to operate.
7.9 Power-On Reset (POR)
ISP1563
HS USB PCI Host Controller
Figure 3 shows a possible curve of V
start with 1. At t1, the detector passes through the trip level. Another delay will be added
before POR drops to 0 to ensure that the length of the generated detector pulse, POR, is
large enough to reset asynchronous flip-flops. If the dip is too short (t4 to t5 < 11 µs),
POR will not react and will stay LOW.
t0t1
V
Fig 3. Power-on reset.
is typically 1.2 V.
POR(trip)
7.10 Power supply
Figure 4 shows the ISP1563 power supply connection.
with dips at t2 to t3 and t4 to t5. At t0, POR will
is not present on PCI, the pin should be connected to PCI 3.3 V.
aux(3V3)
004aaa666
100 nF
Fig 4. Power supply connection.
8.1 PCI interface
The PCI interface has three functions. The first function (#0) and the second function (#1)
are for the OHCI Host Controllers, and the third function (#2) is for the EHCI Host
Controller. All functions support both master and target accesses, and share the same
PCI interrupt signal INTA#. These functions provide memory-mapped, addressable
operational registers as required in
Rev. 1.0a
Rev. 1.0
and
Enhanced Host Controller Interface Specification for Universal Serial Bus
.
Open Host Controller Interface Specification for USB
Additionally, function #0 provides legacy keyboard and mouse support to comply with
Open Host Controller Interface Specification for USB Rev. 1.0a
Each function has its own configuration space. The PCI enumerator should allocate the
memory address space for each of these functions. Power management is implemented
in each PCI function and all power states are provided. This allows the system to achieve
low power consumption by switching off the functions that are not required.
8.1.1 PCI configuration space
ISP1563
HS USB PCI Host Controller
.
PCI Local Bus Specification Rev. 2.2
ISP1563 provides its own PCI configuration registers, which can vary in size. In addition to
the basic PCI configuration header registers, these functions implement capability
registers to support power management.
The registers of each of these functions are accessed by the respective driver.Section 8.2
provides a detailed description of the various PCI configuration registers.
8.1.2 PCI initiator and target
A PCI initiator initiates PCI transactions to the PCI bus. A PCI target responds to PCI
transactions as a slave. In the case of the ISP1563, the two Open Host Controllers and
the Enhanced Host Controller function as both initiators or targets of PCI transactions
issued by the host CPU.
All USB Host Controllers havetheir own operational registers that can be accessed by the
system driver software. Drivers use these registers to configure the Host Controller
hardware system, issue commands to it, and monitor the status of the current hardware
operation. The Host Controller plays the role of a PCI target. All operational registers of
the Host Controllers are the PCI transaction targets of the CPU.
Normal USB transfers require the Host Controller to access system memory fields, which
are allocated by USB HCDs and PCI drivers. The Host Controller hardware interacts with
the HCD by accessing these buffers. The Host Controller works as an initiator in this case,
and becomes a PCI master.
requires that each of the three PCI functions of the
8.2 PCI configuration registers
The OHCI USB Host Controllers and the EHCI USB Host Controller contain two sets of
software-accessible hardware registers: PCI configuration registers and memory-mapped
Host Controller registers.
A set of configuration registers is implemented for each of the three PCI functions of the
ISP1563, see Table 3.
Remark: In addition to the normal PCI header, from offset index 00h to 3Fh,
implementation-specific registers are defined to support power management and
function-specific features.
[1] Reset values that are highlighted, for example, 0, indicate read and write accesses; and reset values that are not highlighted, for
example, 0, indicate read-only.
[2] XX is 1Fh for four ports and 07h for two ports.
[3] See Section 8.2.3.4.
The HCD does not usually interact with the PCI configuration space. The configuration
space is used only by the PCI enumerator to identify the USB Host Controller and assign
appropriate system resources by reading the Vendor ID (VID) and the Device ID (DID).
8.2.1 PCI configuration header registers
The Enhanced Host Controller implements the normal PCI header register values, except
the values for the memory-mapping base address register, serial bus number and Device
ID.
This read-only register identifies the manufacturer of the device. PCI Special Interest
Group (PCI-SIG) assigns valid vendor identifiers to ensure the uniqueness of the
identifier. The bit description is shown in Table 4.
Table 4:VID - Vendor ID register (address 00h) bit description
Legend: * reset value
BitSymbolAccess ValueDescription
15 to 0VID[15:0]R1131h*Vendor ID: This read-only register value is assigned
8.2.1.2 Device ID register
This is a 2 B read-only register that identifies a particular device. The identifier is allocated
by Philips Semiconductors. Table 5 shows the bit description of the register.
Table 5:DID - Device ID register (address 02h) bit description
Legend: * reset value
BitSymbolAccess ValueDescription
15 to 0DID[15:0]R156Xh*
ISP1563
HS USB PCI Host Controller
to Philips Semiconductors by PCI-SIG as 1131h.
[1]
Device ID: This register value is defined by Philips
Semiconductors to identify the USB Host Controller
IC product.
[1] X is 1h for OHCI1 and OHCI2; X is 2h for EHCI.
8.2.1.3 Command register
This is a 2 B register that provides coarse control over the ability of a device to generate
and respond to PCI cycles. The bit allocation of the Command register is given in Table 6.
When logic 0 is written to this register, the device is logically disconnected from the PCI
bus for all accesses, except configuration accesses. All devices are required to support
this base level of functionality. Individual bits in the Command register may or may not
support this base level of functionality.
Table 6:Command register (address 04h) bit allocation
Table 7:Command register (address 04h) bit description
BitSymbolDescription
15 to 10reserved9FBBEFast Back-to-Back Enable: This bit controls whether a master can do
8SERRESERR# Enable: This bit is an enable bit forthe SERR# driver. All devices
7SCTRLStepping Control: This bit controls whether a device does address and
6PERParity Error Response: This bit controls the response of a device to
5VGAPSVGA Palette Snoop: This bit controls how Video Graphics Array (VGA)
4MWIEMemory Write and Invalidate Enable: This is an enable bit forusing the
3SC Special Cycles: Controls the action of a device on Special Cycle
ISP1563
HS USB PCI Host Controller
fast back-to-back transactions to various devices. The initialization
software must set this bit if all targets are fast back-to-back capable.
0 — Fast back-to-back transactions are only allowed to the same agent
(value after RST#)
1 — The master is allowed to generate fast back-to-back transactions to
different agents.
that have an SERR# pin must implement this bit. Address parity errors
are reported only if this bit and the PER bit are logic 1.
0 — Disable the SERR# driver
1 — Enable the SERR# driver.
data stepping. Devices that neverdo stepping must clear this bit. Devices
that always do stepping must set this bit. Devices that can do either,must
make this bit read and write, and initialize it to logic 1 after RST#.
parity errors. When the bit is set, the device must take its normal action
when a parity error is detected. When the bit is logic 0, the device sets
DPE (bit 15 in the Status register) when an error is detected, but does
not assert PERR# and continues normal operation. The state of this bit
after RST# is logic 0. Devices that check parity must implement this bit.
Devices are required to generate parity, even if parity checking is
disabled.
compatible and graphics devices handle accesses to VGA palette
registers.
0 — The device should treat palette write accesses like all other
accesses.
1 — Palette snooping is enabled, that is, the device does not respond to
palette register writes and snoops data.
VGA compatible devices should implement this bit.
Memory Write and Invalidate command.
0 — Memory Writes must be used instead. State after RST# is logic 0.
1 — Masters may generate the command.
This bit must be implemented by master devices that can generate the
Memory Write and Invalidate command.
operations.
0 — Causes the device to ignore all Special Cycle operations. State after
RST# is logic 0.
1 — Allows the device to monitor Special Cycle operations.
Table 9:Status register (address 06h) bit description
BitSymbolDescription
12RTAReceived Target Abort: This bit must be set by a master device whenever its
transaction is terminated with Target-Abort. All master devices must
implement this bit.
11STASignaled Target Abort: This bit must be set by a target device whenever it
terminates a transaction with Target-Abort. Devices that never signal
Target-Abort do not need to implement this bit.
10 to 9 DEVSELT
[1:0]
8MDPEMaster Data Parity Error: This bit is implemented by bus masters. It is set
DEVSEL Timing: These bits encode the timing of DEVSEL#. There are three
allowable timing to assert DEVSEL#:
00b — Fast
01b — Medium
10b — Slow
11b — Reserved.
These bits are read-only and must indicate the slowest time that a device
asserts DEVSEL# for any bus command, except Configuration Read and
Configuration Write.
when the following three conditions are met:
…continued
• The bus agent asserted PERR# itself, on a read; or observed PERR#
asserted, on a write.
• The agent setting the bit acted as the bus master for the operation in
which error occurred.
• PER (bit 6 in the Command register) is set.
7FBBCFast Back-to-Back Capable: This read-only bit indicates whether the target
is capable of accepting fast back-to-back transactions when the transactions
are not to the same agent. This bit can be set to logic 1, if the device can
accept these transactions; and must be set to logic 0 otherwise.
6reserved566MC66 MHz Capable: This read-only bit indicates whether this device is capable
of running at 66 MHz.
0 — 33 MHz
1 — 66 MHz.
4CL Capabilities List: This read-only bit indicates whether this device implements
the pointer for a new capabilities linked list at offset 34h.
0 — No new capabilities linked list is available
1 — The value read at offset 34h is a pointer in configuration space to a linked
list of new capabilities.
3 to 0reserved-
8.2.1.5 Revision ID register
This 1 B read-only register indicates a device-specific revision identifier. The value is
chosen by the vendor. This field is a vendor-defined extension of the Device ID. The
Revision ID register bit description is given in Table 10.
Table 10: REVID - Revision ID register (address 08h) bit description
Legend: * reset value
BitSymbolAccessValueDescription
7 to 0 REVID[7:0]R11h*Revision ID: This byte specifies the design revision
Class Code is a 24-bit read-only register used to identify the generic function of the
device, and in some cases, a specific register-level programming interface. Table 11
shows the bit allocation of the register.
The Class Code register is divided into three byte-size fields. The upper byte is a base
class code that broadly classifies the type of function the device performs. The middle
byte is a sub-class code that identifies more specifically the function of the device. The
lower byte identifies a specific register-level programming interface, if any, so that
device-independent software can interact with the device.
Table 11: Class Code register (address 09h) bit allocation
[1] X is 1h for OHCI1 and OHCI2; X is 2h for EHCI.
[1]
Table 12: Class Code register (address 09h) bit description
BitSymbolDescription
23 to 16BCC[7:0]BaseClass Code: 0Ch is the base class code assigned to this byte.It
15 to 8SCC[7:0]Sub-Class Code: 03h is the sub-class code assigned to this byte. It
7 to 0RLPI[7:0]Register-Level Programming Interface: 10h is the programming
8.2.1.7 CacheLine Size register
The CacheLine Size register is a read and write single-byte register that specifies the
system CacheLine size in units of DWords. This register must be implemented by master
devices that can generate the Memory Write and Invalidate command. The value in this
register is also used by master devices to determine whether to use Read, Read Line or
Read Multiple commands to access the memory.
Slave devices that want to allow memory bursting using a CacheLine-wrap addressing
mode must implement this register to know when a burst sequence wraps to the
beginning of the CacheLine.
implies a serial bus controller.
implies the USB Host Controller.
interface code assigned to OHCI, which is USB 1.1 specification
compliant. 20h is the programming interface code assigned to EHCI,
which is USB 2.0 specification compliant.
BitSymbolAccessValueDescription
7 to 0 CLS[7:0]R/W00h*CacheLine Size: This byte identifies the system
8.2.1.8 Latency Timer register
This register specifies, in units of PCI bus clocks, the value of the Latency Timer for the
PCI bus master. Table 14 shows the bit description of the Latency Timer register.
BitSymbolAccessValueDescription
7 to 0 LT[7:0]R/W00h*Latency Timer: This byte identifies the latency timer.
8.2.1.9 Header Type register
The Header Type register identifies the layoutof the second part of the predefined header;
beginning at byte 10h in configuration space. It also identifies whether the devicecontains
multiple functions. For bit allocation, see Table 15.
ISP1563
HS USB PCI Host Controller
CacheLine size.
Table 15: Header Type register (address 0Eh) bit allocation
Table 16: Header Type register (address 0Eh) bit description
BitSymbolDescription
7MFDMulti-Function Device: This bit identifies a multifunction device.
0 — The device has single function.
1 — The device has multiple functions.
6 to 0HT[6:0]Header Type: These bits identify the layout of the part of the
predefined header, beginning at byte 10h in configuration space.
8.2.1.10 Base Address register 0
Power-up software must build a consistent address map beforebooting the machine to an
operating system. This means it must determine how much memory is in the system, and
how much address space the I/O controllers in the system require. After determining this
information, power-up software can map the I/O controllers into reasonable locations and
proceed with system boot. To do this mapping in a device-independent manner, the base
registers for this mapping are placed in the predefined header portion of configuration
space.
Bit 0 in all Base Address registers is read-only and used to determine whether the register
maps into memory or I/O space. Base Address registers that map to memory space must
return logic 0 in bit 0. Base Address registers that map to I/O space must return logic 1 in
bit 0.
The bit description of the BAR 0 register is given in Table 17.
Table 17: BAR 0 - Base Address register 0 (address 10h) bit description
Legend: * reset value
BitSymbolAccessValueDescription
31 to 0BAR 0[31:0] R/W0000
8.2.1.11 Subsystem Vendor ID register
The Subsystem Vendor ID register is used to uniquely identify the expansion board or
subsystem where the PCI deviceresides. This register allows expansion board vendors to
distinguish their boards, even though the boards may have the same Vendor ID and
Device ID.
Subsystem Vendor IDs are assigned by PCI-SIG to maintain uniqueness. The bit
description of the Subsystem Vendor ID register is given in Table 18.
0000h*
ISP1563
HS USB PCI Host Controller
Base Address to Memory-Mapped Host
Controller Register Space: The memory size
required by OHCI and EHCI are 4 kB and 256 B,
respectively. Therefore, BAR 0[31:12] is assigned to
the two OHCI ports, and BAR 0[31:8] is assigned to
the EHCI port.
Table 18: SVID - Subsystem Vendor ID register (address 2Ch) bit description
Legend: * reset value
BitSymbolAccessValueDescription
15 to 0 SVID[15:0]R1131h*Subsystem Vendor ID: 1131h is the subsystem
8.2.1.12 Subsystem ID register
Subsystem ID values are vendor specific. The bit description of the Subsystem ID register
is given in Table 19.
Table 19: SID - Subsystem ID register (address 2Eh) bit description
Legend: * reset value
BitSymbolAccessValueDescription
15 to 0 SID[15:0]R156Xh*
[1] X is 1h for OHCI1 and OHCI2; X is 2h for EHCI.
8.2.1.13 Capabilities Pointer register
This register is used to point to a linked list of new capabilities implemented by the device.
This register is only valid if CL (bit 4 in the Status register) is set. If implemented, bit 1 and
bit 0 are reserved and should be set to 00b. Software should mask these bits off before
using this register as a pointer in configuration space to the first entry of a linked list of
new capabilities. The bit description of the register is given in Table 20.
Vendor ID assigned to Philips Semiconductors.
[1]
Subsystem ID: For the ISP1563, Philips
Semiconductors has defined OHCI functions as
1561h, and the EHCI function as 1562h.
BitSymbolAccessValueDescription
7 to 0 CP[7:0]RDCh*Capabilities Pointer: EHCI efficiently manages power
8.2.1.14 Interrupt Line register
This is a 1 B register used to communicate interrupt line routing information. This register
must be implemented by any device or device function that uses an interrupt pin. The
interrupt allocation is done by the BIOS. The Power On Self Test (POST) software needs
to write the routing information to this register because it initializes and configures the
system. The value in this register specifies which input of the system interrupt controller(s)
the interrupt pin of the device is connected. This value is used by device drivers and
operating systems to determine priority and vector information. Values in this register are
system architecture specific. The bit description of the register is given in Table 21.
Table 21: IL - Interrupt Line register (address 3Ch) bit description
Legend: * reset value
BitSymbolAccessValueDescription
7 to 0 IL[7:0]R/W00h*Interrupt Line: Indicates which IRQ is used to report
ISP1563
HS USB PCI Host Controller
using this register. This Power Management register is
allocated at offset DCh. Only one Host Controller is
needed to manage power in the ISP1563.
interrupt from the ISP1563.
8.2.1.15 Interrupt Pin register
This 1 B register is use to specify which interrupt pin the device or device function uses.
A value of 1h corresponds to INTA#, 2h corresponds to INTB#, 3h corresponds to INTC#,
and 4h corresponds to INTD#. Devices or functions that do not use interrupt pin must set
this register to logic 0. The bit description is given in Table 22.
Table 22: IP - Interrupt Pin register (address 3Dh) bit description
Legend: * reset value
BitSymbolAccessValueDescription
7 to 0 IP[7:0]R01h*Interrupt Pin: INTA# is the default interrupt pin used
8.2.1.16 Min_Gnt and Max_Lat registers
The Minimum Grant (Min_Gnt) and Maximum Latency (Max_Lat) registers are used to
specify the desired settings of the device for latency timer values. For both registers, the
value specifies a period of time in units of 250 ns. Logic 0 indicates that the device has no
major requirements for setting latency timers. The Min_Gnt register bit description is given
in Table 23.
Table 23: Min_Gnt - Minimum Grant register (address 3Eh) bit description
Legend: * reset value
BitSymbolAccessValueDescription
7 to 0 MIN_GNT
[7:0]
R0Xh*
by the ISP1563.
[1]
Min_Gnt: It is used to specify how long a burst period
the device needs, assuming a clock rate of 33MHz.
[1] X is 1h for OHCI1 and OHCI2; X is 2h for EHCI.
The Max_Lat register bit description is given in Table 24.
Table 24: Max_Lat - Maximum Latency register (address 3Fh) bit description
Legend: * reset value
BitSymbolAccess ValueDescription
7 to 0 MAX_LAT[7:0]RXXh*
[1] XX is 2Ah for OHCI1 and OHCI2; XX is 10h for EHCI.
8.2.1.17 TRDY Timeout register
This is a read and write register at address 40h. The default and recommended value is
00h; TRDY Timeout disabled. This value can, however, be modified. It is an
implementation-specific register, and not a standard PCI configuration register.
The TRDY timer is 13 bits. The lower 5 bits are fixed as logic 0 and the upper 8 bits are
determined by the TRDY Timeout register value. The time-out is calculated by multiplying
the 13-bit timer with the PCI CLK cycle time.
This register determines the maximum TRDY delay without asserting the UE
(Unrecoverable Error) bit. If TRDY is longer than the delay determined by this register
value, then the UE bit will be set.
ISP1563
HS USB PCI Host Controller
[1]
Max_Lat: It is used to specify how often the device
needs to gain access to the PCI bus.
8.2.1.18 Retry Timeout register
The default value of this read and write register is 80h, and is located at address 41h. This
value can, however, be modified. Programming this register as 00h means that retry
time-out is disabled. This is an implementation-specific register, and not a standard PCI
configuration register.
The time-out is determined by multiplying the register value with the PCI CLK cycle time.
This register determines the maximumnumber of PCI retires before the UE bit is set. If the
number of retries is longer than the delay determined by this register value, then the UE
bit will be set.
In addition to the PCI configuration header registers, EHCI needs some additional PCI
configuration space registers to indicate the serial bus release number, downstream port
wake-up event capability, and adjust the USB bus frame length for Start-of-Frame (SOF).
The EHCI-specific PCI registers are given in Table 25.
Table 25: EHCI-specific PCI registers
OffsetRegister
60hSerial Bus Release Number (SBRN)
61hFrame Length Adjustment (FLADJ)
62h to 63hPort Wake Capability (PORTWAKECAP)
8.2.2.1 SBRN register
The Serial Bus Release Number (SBRN) register is a 1 B register, and the bit description
is given in Table 26. This register contains the release number of the USB specification
with which this USB Host Controller module is compliant.
Table 26: SBRN - Serial Bus Release Number register (address 60h) bit description
Legend: * reset value
BitSymbolAccessValueDescription
7 to 0SBRN[7:0]R20h*Serial Bus Specification Release Number: This
register value is to identify Serial Bus Specification
Rev. 2.0. All other combinations are reserved.
8.2.2.2 FLADJ register
This feature is used to adjust any offset from the clock source that generates the clock that
drives the SOF counter. When a new value is written to these six bits, the length of the
frame is adjusted. The bit allocation of the Frame Length Adjustment (FLADJ) register is
given in Table 27.
7 to 6reserved5 to 0FLADJ[5:0]Frame Length Timing Value: Each decimal value changeto this register
corresponds to 16 high-speed bit times. The SOF cycle time (number of
SOF counter clock periods to generate a SOF micro frame length) is
equal to 59488 + valuein this field. The defaultvalue is decimal 32 (20h),
which gives a SOF cycle time of 60000.
FLADJ valueSOF cycle time (480 MHz)
0 (00h)59488
1 (01h)59504
2 (02h)59520
::
31 (1Fh)59984
32 (20h)60000
::
62 (3Eh)60480
63 (3Fh)60496
8.2.2.3 PORTWAKECAP register
Port Wake Capability (PORTWAKECAP) is a 2 B register used to establish a policy about
which ports are for wake events; see Table 29. Bit positions 15 to 1 in the mask
correspond to a physical port implemented on the current EHCI controller. Logic 1 in a bit
position indicates that a device connected below the port can be enabled as a wake-up
device and the port may be enabled for disconnect or connect, or overcurrent events as
wake-up events. This is an information only mask register. The bits in this register do not
affect the actual operation of the EHCI Host Controller. The system-specific policy can be
established by BIOS initializing this register to a system-specific value. The system
software uses the information in this register when enabling devices and ports for remote
wake-up.
Table 29: PORTWAKECAP - Port Wake Capability register (address 62h) bit description
Legend: * reset value
BitSymbolAccess ValueDescription
15 to 0PORTWAKECAP[15:0]R/W001Fh*Port Wake-Up Capability Mask: EHCI
8.2.3 Power management registers
Table 30: Power Management registers
OffsetRegister
Value read from address 34h+ 0hCapability Identifier (Cap_ID)
Value read from address 34h+ 1hNext Item Pointer (Next_Item_Ptr)
Value read from address 34h+ 2hPower Management Capabilities (PMC)
Value read from address 34h+ 4hPower Management Control/Status (PMCSR)
Value read from address 34h+ 6hPower Management Control/Status PCI-to-PCI Bridge
Value read from address 34h+ 7hData
ISP1563
HS USB PCI Host Controller
does not implement this feature.
Support Extensions (PMCSR_BSE)
8.2.3.1 Cap_ID register
The Capability Identifier (Cap_ID) register when read by the system software as 01h
indicates that the data structure currently being pointed to is the PCI Power Management
data structure. Each function of a PCI device may have only one item in its capability list
with Cap_ID set to 01h. The bit description of the register is given in Table 31.
Table 31: Cap_ID - Capability Identifier register bit description
Address: Value read from address 34h+ 0h
Legend: * reset value
BitSymbolAccessValueDescription
7 to 0 CAP_ID[7:0]R01h*ID: This field when 01h identifies the linked list item
8.2.3.2 Next_Item_Ptr register
The Next Item Pointer (Next_Item_Ptr) register describes the location of the next item in
the function’s capability list. The value given is an offset into the function’s PCI
configuration space. If the function does not implement any other capabilities defined by
the PCI-SIG for inclusion in the capabilities list, or if power management is the last item in
the list, then this register must be set to 00h. See Table 32.
Table 32: Next_Item_Ptr - Next Item Pointer register bit description
Address: Value read from address 34h+ 1h
Legend: * reset value
BitSymbolAccess ValueDescription
7 to 0 NEXT_ITEM_
PTR[7:0]
R00h*Next Item Pointer: This field provides an offset into
as being PCI Power Management registers.
the function’s PCI configuration space pointing to the
location of the nextitem in the function’scapability list.
If there are no additional items in the Capabilities List,
this register is set to 00h.
The Power Management Capabilities (PMC) register is a 2 B register, and the bit
allocation is given in Table 33. This register provides information on the capabilities of the
function related to power management.
Table 33: PMC - Power Management Capabilities register bit allocation
Table 34: PMC - Power Management Capabilities register bit description
Address: Value read from address 34h+ 2h
BitSymbolDescription
15 to 11PME_S[4:0] PME_Support: These bits indicate the power states in which the
function may assert PME#. Logic 0 for any bit indicates that the function
is not capable of asserting the PME# signal while in that power state.
PME_S[0] — PME# can be asserted from D0
PME_S[1] — PME# can be asserted from D1
PME_S[2] — PME# can be asserted from D2
PME_S[3] — PME# can be asserted from D3
PME_S[4] — PME# can be asserted from D3
10D2_SD2_Support: If this bit is logic 1, this function supports the D2 Power
Management State. Functions that do not support D2 must always return
logic 0 for this bit.
9D1_SD1_Support: If this bit is logic 1, this function supports the D1 Power
Management State. Functions that do not support D1 must always return
logic 0 for this bit.
Table 34: PMC - Power Management Capabilities register bit description
…continued
Address: Value read from address 34h+ 2h
BitSymbolDescription
8 to 6AUX_C[2:0]Auxiliary_Current: This three-bit field reports the V
current requirements for the PCI function.
If the Data register is implemented by this function:
aux(3V3)
auxiliary
• A read from this field needs to return a value of 000b.
• The Data register takes precedence over this field for V
current requirement reporting.
If the PME# generation from D3
(PMC[15] = 0), this field must return a value of 000b when read.
For functions that support PME# from D3
Data register, the bit assignments corresponding to the maximum current
required for V
111b — 375 mA
110b — 320 mA
101b — 270 mA
100b — 220 mA
011b — 160 mA
010b — 100 mA
001b — 55 mA
000b — 0 (self powered).
5DSIDevice Specific Initialization: This bit indicates whether special
initialization of this function is required, beyond the standard PCI
configuration header, before the generic class devicedriver is able to use
it.
This bit is not used by some operating systems. For example, Microsoft
Windows and Windows NT do not use this bit to determine whether to
use D3. Instead, it is determined using the capabilities of the driver.
Logic 1 indicates that the function requires a device-specific initialization
sequence, following transition to D0 un-initialized state.
4reserved3PMIPME Clock:
0 — Indicates that no PCI clock is required for the function to generate
PME#.
1 — Indicates that the function relies on the presence of the PCI clock for
the PME# operation.
Functions that do not support the PME# generation in any state must
return logic 0 for this field.
2 to 0VER[2:0]Version: A value of 010b indicates that this function complies with
aux(3V3)
are:
Power Management Interface Specification Rev. 1.1
is not supported by the function
cold
and do not implement the
cold
.
aux(3V3)
PCI
The logic level of the AMB4 pin at power-on determines the default value of the PMC
registers. If this pin is pulled up to 3.3 V, the ISP1563 will report that it supports PME
generation in D3
down, the ISP1563 will report that it does not support PME generation in D3
(bit 15 (PME_S4) will be set to 1). If this pin is left open or is pulled
The Power Management Control/Status (PMCSR) register is a 2 B register used to
manage the Power Management State of the PCI function, as well as to allow and monitor
Power Management Events (PMEs). The bit allocation of the register is given in Table 35.
Table 35: PMCSR - Power Management Control/Status register bit allocation
[1] Sticky bit, if the function supports PME# from D3
function does not support PME# from D3
[2] The reserved bits should always be written with the reset value.
cold
, then X is indeterminate at the time of initial operating system boot; X is 0 if the
cold
.
Table 36: PMCSR - Power Management Control/Status register bit description
Address: Value read from address 34h+ 4h
BitSymbolDescription
15PMESPME Status: This bit is set when the function normally assert the PME#
signal independent of the state of the PMEE bit. Writing logic 1 to this bit
clears it and causes the function to stop asserting PME#, if enabled. Writing
logic 0 has no effect. This bit defaults to logic 0, if the function does not
support the PME# generation from D3
generation from D3
the operating system each time the operating system is initially loaded.
14 to 13 DS[1:0]Data Scale: This two-bit read-only field indicates the scaling factor when
interpreting the valueof the Data register.The value and meaning of this field
vary, depending on which data valueis selected by the D_S field. This field is
a required component of the Data register (offset 7) and must be
implemented, if the Data register is implemented. If the Data register is not
implemented, this field must return 00b when PMCSR is read.
12 to 9D_S[3:0]Data_Select: This four-bit field selects the data that is reported through the
Data register and the D_S field. This field is a required component of the
Data register (offset 7) and must be implemented, if the Data register is
implemented. If the Data register is not implemented, this field must return
00b when PMCSR is read.
. If the function supports the PME#
, then this bit is sticky and must be explicitly cleared by