US 5,944,807 AGrant
Compact ISA-bus Interface
Issue Date:1999-08-31
•18 Claims
•9 Drawing Sheets
Abstract
An I/O interface, compatible with industry standards, for interfacing a host to a peripheral device. The interface includes a clock signal, a bus, an address latch enable signal, a peripheral device ready signal, a command signal, a device selected backoff signal, and a reset signal, resulting in an I/O interface capable of ISA-compatible operation with only 22 pins. Address, data, command, interrupt request, and DMA request information are communicated between the host and the peripheral device via a single bus by multiplexing the information on the bus using phasing techniques.
Metadata
Assignee
- OPTi Inc.
Inventor
- Mark Williams
Application Information
Application Number:US 5959896
Filing Date:1996-02-06
Priority Date:1996-02-06
Art Unit:271
Classifications
IPC:
G06F 1300
Field of Search:
395710309;306;842;868;878;822129;126;22;48;58;2
Patent Drawings (9 sheets)
Description
Background of the Invention
1. Field of the Invention
The invention relates to IBM PC AT-compatible computer architectures, and more particularly to I/O interfaces for communicating with peripheral devices.
2. Description of Related Art
The IBM PC AT-computer architecture has become an industry standard architecture for personal computers. The typical IBM PC AT-compatible computer includes an I/O bus, sometimes referred to in these systems a s a n AT bus. Such a bus is used to interface communications between a host and a peripheral device, or communications between peripheral devices and host memory.
The most commonly used I/O bus is the industry standard architecture (ISA) bus. The ISA bus was adopted by several computer industry groups to create a standard to permit the development of compatible add-on cards in a reasonable and consistent fashion. The ISA bus includes 8 or 16 data lines in a data bus, address lines in an address bus distinct from the data bus, as well as distinct control and command lines.
The various signals on the ISA bus are well specified and well known in the industry. General information on the ISA bus can be found in Solari, "AT Bus Design" (San Diego, Annabooks, 1990), incorporated by reference herein. For present purposes, the following signals are important:
Recently, efforts have been made to develop other bus protocols for PC AT-compatible computers with the goals of reducing the size of PC AT-compatible computers as well as continued industry standardization. These efforts have included the development of the PCI local bus as well as the PCMCIA bus.
The PCI local bus has been developed to establish an industry standard for local bus architectures, particularly those interfacing with high bandwidth functions. The PCI local bus is described in detail in "PCI Local Bus Specification", Revision 2.0 (Hillsboro, Oreg., PCI Special Interest Group, 1993), incorporated by reference herein. The PCI local bus attempts to reduce the number of pins required for a local bus design by multiplexing address information and data information onto a single address-data bus. However, the PCI local bus still requires a minimum of 47 pins to provide adequate communication between a processor and local components, with its address-data bus comprising 32 of those pins and various command information comprising at least 4 pins. Further, because the PCI bus was designed primarily to support high-end peripherals, it is not as economical to manufacture low-end peripherals for the PCI-bus as it is for the older, slower, ISA-bus.
The PCMCIA bus has been developed to promote the interchangability of integrated circuit cards among a variety of computer types and products, including IBM PC-compatible systems. The PCMCIA bus is described in detail in Personal Computer Memory Card Int'l Assoc. (PCMCIA) "PC Card Standard", Revision 2.0 (Sunnyvale, Calif., 1991), incorporated by reference herein. The PCMCIA bus attempts to reduce the size of the I/O interface by miniaturizing the connector. However, PCMCIA does little toward actually reducing the number of pins required to utilize its bus over ISA. The PCMCIA connector requires 68 pins, including 26 pins for addressing functions and 16 separate pins for data.
Therefore, despite these attempts to develop other bus protocols, the ISA bus interface remains one of the most widely used and accepted I/O bus architectures. While it is important from an interfacing perspective to maintain the industry standards to maintain overall system compatibility for various add-on cards designed in compliance with industry standards, it is also desirable to reduce the pin counts on interface connectors, and thus reduce the size of PC AT-compatible computers and their add-on peripheral devices.
Summary of the Invention
The present invention, roughly described, is directed to an interface to be used between a host device and one or more peripheral devices. It is desirable to create an interface with a reduced pin count from that of the conventional ISA bus interface but that can co-exist with and not interfere with standard ISA operations.
To reduce the pin count on an interface connector, the interface according to the present invention, roughly described, eliminates the multiple and distinct buses which are conventionally required to support distinct functions, including addressing functions, data transfers, interrupt requests, DMA requests, and DMA acknowledge-type communications. Rather, an aspect of the present invention (hereafter referred to as "compact ISA" or "CISA") is the utilization of a single bus structure to transfer address, data, interrupt request, DMA request, and DMA acknowledge information. Using phasing techniques, the CISA interface multiplexes the different types of information onto the single bus. For instance, in one cycle, address information may be driven onto the bus for a time period, an "address phase," followed by data information in a "data phase". In another cycle, interrupt request information may be driven onto the bus during an interrupt request phase followed by DMA request information in a DMA request phase.
In addition to eliminating the extensive number of pins required to support multiple buses, CISA further eliminates other signals commonly used in ISA interface structures. For instance, CISA does not use distinct signal lines for carrying IORD#, IOWR#, MRD#, MWR#, SMEMR#, SMEMW#, SBHE#, SRDY#, AEN, IOCS16#, MEMCS16# and TC. Rather, in an embodiment of the invention, CISA combines some of these signals into a new signal (discussed below), or multiplexes some of these signals on the address-data bus along with address and data information.
Other aspects of the invention, roughly described, are the addition of two signals not present on the ISA bus interface. The first signal is a command indication signal(CMD#), which, in its simplest form, is the AND of the IORD#, IOWR#, MRD# and MWR# commands on the ISA bus interface. The second signal added is a device selected/AT bus backoff request, SEL#/ATB#, which indicates in one mode of operation that a peripheral device claims the current cycle and, in a second mode of operation, that the host should inhibit its bus operations. The SEL#/ATB# signal is also asserted asynchronously to restart the clock if the peripheral device is engaged in a stop clock, or low power, mode.
Thus, in one embodiment of the invention, the total requirement of connector pins required for the CISA interface is 22 pins, for a reduction of 58 pins over ISA.
Brief Description of the Drawings
The invention will be described with respect to particular embodiments thereof, and reference will be made to the drawings, in which:
FIG. 1 is a functional block diagram of an interface in accordance with the present invention;
FIG. 2a is a timing diagram showing the operation of the interface of FIG. 1 for performing a memory cycle with standard timing;
FIG. 2b is a chart showing bit definitions for bus 135 of FIG. 1 in a memory access cycle with either fast or standard timing;
FIG. 3 is a timing diagram showing the operation of the interface of FIG. 1 for performing a memory access cycle with fast timing;
FIG. 4a is a timing diagram showing the operation of the interface of FIG. 1 for performing an I/O access cycle;
FIG. 4b shows bit definitions for bus 135 of FIG. 1 during an I/O access cycle;
FIG. 5a is a timing diagram showing the operation of the interface of FIG. 1 for performing a DMA acknowledge cycle;
FIG. 5b shows bit definitions on bus 135 of FIG. 1, during a DMA acknowledge cycle;
FIG. 6a is a timing diagram showing the operation of the interface of FIG. 1 for performing a stop clock broadcast configuration cycle;
FIG. 6b shows bit definitions on bus 135 of FIG. 1 during a stop clock broadcast configuration cycle;
FIG. 7a is a timing diagram showing operation of the interface of FIG. 1 for performing an interrupt and DMA request drive-back cycle;
FIG. 7b shows bit definitions on bus 135 of FIG. 1 during an interrupt a DMA request drive-back cycle;
FIG. 8 is a functional block diagram of a shared speaker output line in accordance with the present invention;
FIG. 9a is a timing diagram showing initialization and synchronization for use of the shared speaker output line of FIG. 8 in accordance with the present invention; and
FIG. 9b is a timing diagram showing the utilization of the shared speaker output signal of FIG. 8 in accordance with the present invention.
Detailed Description
FIG. 1 is an overall block diagram of a complete system incorporating a CISA interface according to the invention. FIG. 1 shows a host side 105 and a device side 110 of an interface 175. On the host side 105 is host platform interface circuitry 115 coupled to CPU 120 via a CPU bus 125. Host platform interface circuitry 115 communicates address, data, interrupt request, and DMA request information to/from a peripheral device 130 via a bidirectional address-data bus, MAD15:0! 135 crossing the interface 175. In addition to the address-data bus 135 being coupled between the host platform interface circuitry 115 and the peripheral device 130, other signals, as described in Table 1 below, ALE 140, CMD# 145, IOCHRDY 150, SEL#/ATB# 155 and RST 160, are coupled between host platform interface circuitry 115 and peripheral device 130. A clock signal line CLK 163 is provided to host platform interface circuitry 115 by other circuitry (not shown). ATCLK 165 is driven by host platform interface circuitry 115, and is coupled to clock inputs of both host platform interface circuitry 115 and across the interface 175 to peripheral device 130. A dashed line 175 indicates the interface, which in the present embodiment comprises a 22 pin pinout. In other embodiments of the invention, dashed line 175 may indicate a 22-pin connector or a 40-pin cable in which the extra pins are grounded or unused. Also included is IRQ/DRQ generation circuitry 170, which is coupled to the address-data bus 135, CMD# 145 and SEL#/ATB# 160, and is further discussed below.
The complete CISA interface signal set is shown in Table 1 below. Note that some of the signals described in this specification are asserted high, whereas others are asserted low. As used herein, signals which are asserted low are given a `#` suffix in their names, whereas those asserted high (or for which an assertion polarity has no meaning) lack a `#` suffix.
In operation, the CISA interface typically operates in two different modes. In the first mode of operation, the CISA interface is able to perform memory access cycles, I/O access cycles, configuration cycles, or DMA acknowledge cycles. In the second mode of operation, the CISA interface is able to perform interrupt and DMA request drive-back cycles. Each of these modes will be discussed in turn.
Mode 1--Memory, I/O, Configuration, DMA Acknowledge Cycles
During mode-1 type cycles, address and data information are multiplexed onto the address-data bus, resulting in at least one address phase and at least one data phase. Often, an address will be composed of more than 16 bits (the width of the address data bus 135 shown in FIG. 1). In such instances, two address phases are used to convey a complete address followed by a data phase. The two address phases are sometimes referred to herein as two address "sub-phases" of a single address "phase." Were data information to be composed of more than 16 bits, multiple data sub-phases could also be utilized. However, the present embodiment uses two address sub-phases and one data phase for a total of three phases.
The low order three bits of the multiplexed address-data bus, MAD2:0!, are reserved in the first two phases (the address phases) of each mode-1 cycle to define the cycle and to provide several commands which are typically provided by signal lines separate from an address or data bus in other conventionally used I/O interfaces. Bit usage for these three bits of the MAD bus are shown in Table 2 below.
A. Memory Access Cycles.
A memory access cycle using ISA-compatible timing is shown in FIG. 2a, which is discussed with reference to FIG. 1. FIG. 2b is a table showing bit inf ormation for each MAD line in each of the three phases of the cycle. Host platform interface circuitry 115 gets address information from CPU 120 via bus 125, A23:0!, as well as cycle definition and command information (e.g., M/IO#, W/R#, SBHE#) from either CPU 120 or an ISA controller (not shown). In the first address phase, host platform interface circuitry 115 drives out A23:10! on MAD15:2!. Concurrently, host platform interface circuitry 115 drives out cycle definition information, including cycle type (I/D#=0) on MAD1!, and address space selection (M/IO#=1) on MAD0!, as shown in FIG. 2b. Peripheral device 130 then latches MAD15:0! (address and cycle information) on the rising edge of ATCLK and decodes the information.
In the second address phase, host platform interface circuitry 115 drives out the remaining address information, A9:0!, as well as remaining command information, ISA# (=0 for standard timing), SBHE#, and W/R# as shown in FIG. 2b. Note in FIG. 2b that when all bits on the MAD bus are not required to be used, unused bits retain whatever value they had in the previous phase. Host platform interface circuitry 115 asserts ALE. The peripheral device latches the address and command (e.g., cycle definition) information from MAD15:0! on the rising edge of ALE. If the cycle belongs to a CISA peripheral device, then peripheral device 130 asserts SEL#. Host platform interface circuitry 115, and any other CISA devices coupled to the interface, recognize the SEL# function of SEL#/ATB# by seeing ALE high on sampling SEL#/ATB# low on the rising edge of ATCLK. Host platform interface circuitry 115 then de-asserts ALE on the rising ATCLK edge.
During the data phase of a memory access cycle, for reads, host platform interface circuitry 115 tri-states its MAD15:0! outputs. For writes, host platform interface circuitry 115 drives write data onto MAD15:0!. For reads and writes, host platform interface circuitry 115 asserts CMD# synchronously with the rising edge of ATCLK. Host can also optionally inhibit its ISA MRD#/MWR# lines, preventing bus contention with ISA devices (i.e., only one device will then be able to return data). Peripheral device 130 can bring IOCHRDY low asynchronously after CMD# goes active to extend the cycle further. When peripheral device 130 is ready to end the cycle, it brings IOCHRDY high asynchronously to allow cycle completion. Host platform interface circuitry 115 will then de-assert CMD# on the next rising edge of ATCLK after the rising ATCLK edge on which it sampled IOCHRDY high. (As used herein, a signal which is said to shift to a different logic level "synchronously" with a particular edge of ATCLK, does so in response to such particular edge and does so sufficiently in advance of the next ATCLK edge of the same polarity to meet set-up and hold requirements.)
During memory access cycle operation, the CISA interface is also capable of fast timing, or "no-wait-state" operation. FIG. 3 depicts a CISA memory cycle with fast CISA timing. The address phases are identical to those of a memory cycle with standard timing except that ISA# (MAD2! in the second address phase) is driven to a logical high to indicate fast timing. The data phase of a fast memory cycle, however, utilizes different timing than a standard timing memory cycle. For reads, host platform interface circuitry 115 tri-states its MAD15:0! outputs, and for writes, host platform interface circuitry 115 drives write data onto MAD15:0!. Host platform interface circuitry 115 asserts CMD# synchronously with the rising edge of ATCLK. Host can also optionally inhibit its ISA MRD#/MWR# lines. Peripheral device 130 can bring IOCHRDY low asynchronously after CMD# goes active to extend the cycle further, and, in the present embodiment, must de-assert IOCHRDY immediately upon receiving CMD# if it desires to lengthen the cycle. When peripheral device 130 is ready to end the cycle, it brings IOCHRDY high synchronously with the falling edge of ATCLK to allow cycle completion. Host platform interface circuitry 115 will then de-assert CMD# on the same rising edge of ATCLK where it samples IOCHRDY high.
B. I/O Access Cycles.
A CISA I/O access cycle is shown in FIG. 4a. I/O cycle timing is identical to that for a memory cycle with standard timing. In an I/O cycle, however, I/D# (MAD1! in the first address phase) will be driven to a logical high and M/IO# (MAD0! in the first address phase) will be driven to a logical low, as shown in Table 2 and FIG. 4b. In addition, rather than inhibiting the ISA MRD#/MWR# signals, the host can optionally inhibit its ISA IOR#/IOW# lines to prevent two devices from simultaneously accessing the same address space.
Because I/O cycles cannot be made "no-wait-state" on the conventional ISA bus, they have also been defined on the CISA bus as "no-wait-state" by default to maintain compatibility with ISA devices. However, in an embodiment accessing a CISA peripheral device or other device capable of fast timing, I/O cycles are made "no-wait-state" in a manner similar to that done for fast memory cycles, i.e., driving MAD2! to a logical high to indicate fast timing.
C. DMA Cycles.
Two situations arise with respect to DMA operations. The first situation is a DMA transfer between an ISA DMA device and any memory device, including system DRAM, ISA memory, or CISA memory. The second situation is a DMA transfer between a CISA DMA (I/O) device and memory (CISA or non-CISA). Thus, the CISA host platform interface circuitry 115 must distinguish between the DMA channels on the ISA bus and those on the CISA bus, and does so according to whether it has latched DRQ active for a particular channel for a CISA drive-back cycle (described below).
In the first DMA situation, where a transfer occurs between an ISA DMA device and any memory device, the host platform interface circuitry 115 runs a standard CISA memory cycle (shown in FIGS. 3 and 2b) along with an ISA I/O cycle (not shown). If the memory device is a CISA memory device, the memory device responds with SEL# and the host must deassert ALE.
In the second DMA situation, where a transfer occurs between a CISA DMA (I/O) device and a memory, a DMA acknowledge cycle is initiated and is shown in FIG. 5a. Host platform interface circuitry 115 gets address information from CPU 120 via bus 125, A23:0!, as well as cycle definition and other command information (e.g., M/IO#, W/R#, SBHE#) from either CPU 120 or an ISA controller (not shown). In the first address phase, host platform interface circuitry 115 drives out A23:10! on MAD15:2!. Concurrently, host platform interface circuitry 115 drives out cycle definition information, I/D#=0 on MAD 1! and M/IO#=0 on MD 0!, as shown in FIG. 5b. CISA DMA device and CISA memory device (both considered peripheral devices and not shown separately) then latch MAD15:0! (address and cycle information) on the rising edge of ATCLK and decode the information.
In the second address phase, host platform interface circuitry 115 drives out remaining address information (A9:0!), channel information (DMX2:0!), TC (terminal count), and remaining command information (SBHE#, and W/R#), as shown in FIG. 5b. Note that SBHE# and W/R# reference the memory device and not the I/O device, which assumes the opposite sense of W/R# for its portion of the cycle. Host platform interface circuitry 115 asserts ALE. Because the host platform interface circuitry 115 has already determined that the cycle belongs to a CISA device, the host platform interface circuitry 115 does not need to see SEL# and the CISA DMA device does not assert SEL# for the I/O portion of the cycle, but does latch the address and command information from MAD15:0! on the rising edge of ATCLK. CISA memory device also latches address and command information, but the CISA memory device asserts SEL#. Were the CISA DMA (I/O) device to assert SEL#, contention would arise with the CISA memory device which must, in the present embodiment, respond with SEL# during the memory portion of the cycle. Host platform interface circuitry 115 then de-asserts ALE on the rising ATCLK edge.
During the data phase of the DMA acknowledge cycle, host platform interface circuitry 115 tri-states its MAD15:0! outputs for DMA writes (i.e., I/O read, memory write), and for DMA reads (i.e., I/O write, memory read), host platform interface circuitry 115 drives write data onto MAD15:0!. For reads and writes, host platform interface circuitry 115 asserts CMD# synchronously with the falling edge of ATCLK and must inhibit its ISA IOR#/IOW# lines. In the present embodiment, CISA DMA device may not extend a DMA acknowledge cycle with IOCHRDY, but CISA memory devices may de-assert IOCHRDY. Host platform interface circuitry 115 will de-assert CMD# synchronously with the rising edge of ATCLK.
D. Configuration Cycles.
One type of configuration cycle is a broadcast cycle, and one type of broadcast cycle is a stop clock cycle, which is shown in FIG. 6a. A stop clock cycle indicates that the host platform interface circuitry 115 will immediately put the CISA peripheral device 130 into a low-power mode in which peripheral device 130 will no longer receive clocks. Therefore, the peripheral device 130 must enter into a state in which it can asynchronously signal that it needs the clocks restarted, for instance, if it needed to generate an interrupt to the system.
Referring to FIGS. 6a and 6b, the host platform interface circuitry 115 initiates the stop clock cycle by driving out command and cycle information in phase 1 of the cycle. This command and cycle information includes BRD=1 to indicate a broadcast cycle, STP#=0 to indicate a stop cycle, CC2:0! which are clock count bits indicating how many rising clock edges the peripheral device 130 should expect after CMD# goes high before the clock is stopped, I/D#=1, and M/IO#=1. In the present embodiment, other bits on the MAD bus have been reserved. Peripheral device 130 then latches this information on the rising edge of ATCLK.
In the second phase, host platform interface circuitry drives out remaining command information, including ISA#=1 indicating fast timing (no-wait-state), SBHE#=0 to indicate 16 bits of data, and W/R#=1 because a stop clock cycle will always be a write cycle. Host platform interface circuitry 115 asserts ALE and peripheral device latches the remaining information. Peripheral device 130 does not assert SEL#, in the present embodiment.
Host platform interface circuitry asserts CMD# synchronously with the rising edge of ATCLK. Once host de-asserts CMD#, peripheral device 130 is internally in a stop-ready (STPRDY) state. After the number of clocks specified by CC2:0!, the host platform interface circuitry stops the clock, in one embodiment, in its high state. In an alternative embodiment, the host platform interface circuitry stops the clock in its low state. In FIG. 6a, CC2:0!=001, and the clock is brought high by host platform interface circuitry on the next rising ATCLK edge. Each additional count requires the host platform interface circuitry 115 to wait one more clock cycle before stopping the clock.
While in the STPRDY state, peripheral device 130 also counts clocks and it enters into a stop active (STPACTV) state on the specified clock edge (in FIG. 6a, after 001 clock edges). Once in the STPACTV state, SEL#/ATB# has a third meaning: Clock Run (CLKRUN#). Peripheral device 130 can assert CLKRUN# asynchronously at any time while in the STPACTV state to signal host platform interface circuitry to restart its clock, for instance if peripheral device 130 needs to assert an interrupt request to the host.
After CLKRUN# (SEL#/ATB#) has been asserted, on the next rising edge of ATCLK, peripheral device 130 deasserts CLKRUN# but does not drive it high. Peripheral device 130 has, at this point, left the STPRDY state, but still remains in the STPACTV state and still cannot initiate or respond to any cycles. On the next falling ATCLK edge, host platform interface circuitry 115 drives SEL#/ATB# high for half an ATCLK cycle, and on the next rising ATCLK edge, host platform interface circuitry 115 stops driving SEL#/ATB#. Peripheral device 130 leaves the STPACTV state and can generate or respond to cycles. Note in FIG. 6b that the MAD bus in the data phase of the stop clock cycle contains no useful data and is not latched.
Mode 2--Interrupt and DMA Request Drive Back Cycles.
In order to enter the second mode of operation, peripheral device 130 must sample SEL#/ATB# and CMD# high, and ALE low, on two consecutive edges of ATCLK. The peripheral device 130 will assert ATB# on a rising edge of ATCLK. At this point, in the present embodiment, the peripheral device 130 can only drive two types of information onto the bus: interrupt requests and DMA requests. Thus, rather than the three-phase multiplexing that occurred with the cycles previously discussed, this second mode of operation has two phases, an interrupt phase and a DMA request phase.
FIG. 7a illustrates the interrupt request and DMA request (IRQ and DRQ, respectively) drive-back cycles. Once it is determined that mode-2 operation is possible, peripheral device 130 may assert SEL#/ATB#. Note that during the previously discussed mode of operation (mode 1), the SEL#/ATB# signal indicated that the peripheral device 130 is claiming the current cycle on the bus. However, when ALE is low, assertion of the SEL#/ATB# signal by the peripheral device 130 acts to indicate that the host platform interface circuitry should "back off" from driving memory or I/O cycles on the bus.
If host platform interface circuitry 115 was starting a cycle, and was about to assert ALE on the next falling edge of ATCLK, once SEL#/ATB# is asserted with ALE low, the host platform interface circuitry 115, in the present embodiment, must abort the cycle and retry it later. Even if host platform interface circuitry 115 is busy and cannot respond to the drive-back request immediately, it inhibits initiation of all other I/O and DMA operations.
As soon as AT bus operations have been completed and bus 135 is available, host platform interface circuitry 115 drives MAD15:0! high for half an ATCLK cycle from a falling edge of ATCLK, then asserts CMD# after the next rising edge of ATCLK to acknowledge that device 130 can now drive IRQ information onto the bus. The host drives ATB# low at this time. Peripheral device 130 can now drive interrupt data onto bus 135 on the next falling edge of ATCLK, driving low only those lines with IRQ activity and not actively driving high the other lines. In this way, multiple CISA devices can drive the lines in parallel. To restore an IRQ line to its inactive state, the CISA device must initiate an IRQ driveback cycle but leave the MAD line corresponding to the inactive-going IRQ high. CISA devices must track IRQ driveback cycles initiated by other CISA devices in order to maintain an active state on any IRQ line they currently control. The IRQ generation circuitry 170, which may, in different embodiments, be external to the host platform interface circuitry 115 or built into it, uses the rising edge of ATCLK, qualified by ATB# and CMD# low, to latch IRQ information. The peripheral device 130 stops driving ATB# and the host platform interface circuitry 115 controls ATB# throughout the rest of the cycle.
As shown in FIGS. 7a and 7b, for DMA requests (DRQs), peripheral device 130 drives high any MAD15:0! lines it was driving low for one-half an ATCLK cycle, then tri-states the lines for half an ATCLK cycle. Peripheral device 130 drives DRQ information onto MAD7:0! and, at the same time, drives low the corresponding lines MAD15:8! to indicate which DRQ channels have a status change to be transferred. The host side DRQ generation circuitry 170, which may, in different embodiments, be external to the host platform interface circuitry 115 or built into it, samples ATB# and CMD# active on the next rising ATCLK edge after the edge on which IRQs were sampled, and latches the DRQ information on MAD7:0! for the channel selected. The host DRQ generation circuitry may, in different embodiments, OR the DRQs obtained with other system DRQs. The host de-asserts CMD# and ATB# on the next rising edge of the ATCLK cycle.
The desired DMA request line states are latched by host platform interface circuitry 115 and will remain in that state until cleared by another DRQ drive-back cycle. This scheme allows for both DMA single transfers and DMA block transfers. The peripheral device 130 asserts SEL#/ATB# immediately any time a DRQ line changes state (assuming the current cycle is finished). The host platform interface circuitry 115, in turn, immediately de-asserts all DRQ inputs to its DRQ generation circuitry 170, including DMA requests from ISA DMA devices, until the host platform interface circuitry 115 drives a DMA acknowledge cycle. By dynamically blocking ISA device DMA requests, any need to reassign DMA channels is eliminated.
ISA Compatibility
CISA performance is comparable with that of 16-bit ISA bus peripheral devices. It does not interfere with standard ISA operations and is compatible with ISA operations. For instance, CISA ATCLK signal 165 is compatible with the standard ISA BLCK signal; CISA ALE signal 140 is compatible with the standard ISA BALE signal; and CISA IOCHRDY signal 150 is compatible with standard ISA signal IOCHRDY. In addition, in its simplest form, CMD# 145 is the AND of the IORD#, IOWR#, MRD#, and MWR# commands on the ISA bus interface. However, compatibility for the present embodiment is based upon the following assumptions:
1. No ISA peripherals can drive the MAD bus between ISA cycles. They must stay tri-stated at this time.
2. ATCLK can be stopped only during a stop clock broadcast configuration cycle and must run at all other times.
3. No standard ISA masters on the bus are allowed access to CISA peripheral devices. Standard ISA masters are simply ignored by CISA devices since these masters cannot generate CMD# and so cannot run a CISA cycle.
4. No bus master capability is necessary on the part of the CISA peripheral device in the present embodiment. However, the presence of SEL#/ATB# and its "backoff" feature allows bus master capabilities in other embodiments.
5. On receipt of an ATB# request, the CISA host must immediately inhibit all system DRQ activity until the drive-back cycle is complete. Otherwise, unwanted DMA cycles could occur.
Shared Speaker Signal
In one embodiment of the present invention, an additional digital speaker output signal (SPKROUT) is provided. Unlike conventional schemes which generally require that the digital audio outputs from each device be tied together with XOR logic, the present invention allows the digital audio outputs of any number of devices to be combined and shared, as shown in FIG. 8. In addition SPKROUT 805 is shared among devices in the present invention without the use of open-collector outputs. Speaker data output is typically a signal driven in both the low-to-high and high-to-low directions, making an open-collector output on the speaker data output lines insufficient in that there is no guarantee that any particular speaker output line from a device will be left in a high or tri-stated condition. If one open-collector device leaves the speaker output signal low, no other open-collector device connected on the line could toggle the signal from low to high. In addition, open-collector outputs tend to consume excessive power.
Referring to FIG. 8, SPKROUT 805 is coupled between peripheral device 830, peripheral device 831, and host platform interface circuitry 815. SPKROUT 805 is further coupled to signal receiving circuitry 890 which in turn is coupled to speaker 895. Peripheral devices 830 and 831 also receive source input A 885 and source input B 886, respectively. Source input A 885 and source input B 886 are additionally coupled to host platform interface circuitry 815. RST 860, ALE 840, and ATCLK 865 are additionally coupled between host platform interface circuitry 815 and each peripheral device 830 and 831.
In accordance with one embodiment of the invention, to share SPKROUT 805 between peripheral device 830, peripheral device 831, and host platform interface circuitry 815, the SPKROUT output of each device is first initialized and each device is synchronized. To initialize, the SPKROUT outputs of each device are tri-stated at hard reset time and remain tri-stated until individually enabled. To synchronize, referring to FIG. 9a, on the first ALE generated by host platform interface circuitry 805, peripheral devices 830 and 831 will synchronize to ATCLK and derive the signal ATCLK/2 internally. Four distinct phases result: Phase 0 when ATCLK is high and ATCLK/2 is high; Phase 1 when ATCLK is low and ATCLK/2 is high; Phase 2 when ATCLK is high and ATCLK/2 is low; and Phase 3 when ATCLK is low and ATCLK/2 is low.
Once initialized and synchronized, a signal can be driven on the SPKROUT 805 line as shown in FIG. 9b. On the rising ATCLK edge starting Phase 0 a peripheral device 830 wishing to drive a signal on SPKROUT 805 samples the state of SPKROUT 805. Host platform interface circuitry 815 also samples the state of SPKROUT 805. Both peripheral device 830 and host platform interface circuitry 815 maintain the speaker output of each device tri-stated during the remainder of Phase 0. On the falling edge of the ATCLK edge starting Phase 1 peripheral device 830 and host platform interface circuitry 815 each sample digital audio source input (source input A) 885. During Phase 1, if the signal on source input A 885 sampled on the falling ATCLK edge has changed since a previous phase 1 in which it was sampled, both peripheral device 830 and host platform interface circuitry 815 toggle the signal on SPKROUT 805. Toggling occurs by driving the opposite logic value (0 or 1) of the SPKROUT value sampled in Phase 0 by peripheral device 830 and host platform interface device 831.
On the rising ATCLK edge starting phase 2, both peripheral device 830 and host platform interface circuitry 815 tri-state their respective speaker outputs and maintain them tri-stated during the remainder of Phase 2. On the rising ATCLK edge starting Phase 2, host platform interface circuitry 815 additionally samples the state of SPKROUT 805. On the falling ATCLK edge starting Phase 3, host platform interface circuitry 805 drives SPKROUT to the value of SPKROUT sampled in Phase 2 by host platform interface circuitry 815. Host platform interface circuitry 815 maintains SPKROUT driven with this value for the remainder of Phase 3 while peripheral device 830 maintains its speaker output tri-stated.
Although two devices will rarely simultaneously require use of SPKROUT, should simultaneous demands occur, the scheme of the present invention eliminates contention. Both devices will sample the SPKROUT line and should a toggle be required, both would toggle the line in the same direction.
It is possible that neither peripheral device 830 nor host platform interface circuitry 815 will drive the SPKROUT 805 line for up to 1.5 ATCLK cycles. Thus, shared SPKROUT line 805 depends on an RC time constant large enough that the signal on SPKROUT 805 will not change its level any appreciable amount across a period of 1.5 ATCLKs. In one embodiment of the invention, the bus capacitance inherent on the SPKROUT line 805 will be sufficient to act as a capacitive logic level holding mechanism 891. However, in some instances, a larger capacitance may be needed to hold the logic level, the value of which will be apparent to one of ordinary skill in the art.
Further, in the present embodiment, speaker 895 is an 8 ohm speaker. Connecting speaker 895 directly to line 805 would cause the line to begin a transition when it was tri-stated. Therefore, speaker 895 should be further coupled with a high impedance input 892, which may be a simple buffer in one embodiment of the invention, or a high impedance amplifier circuit in another embodiment of the invention.
During a stop clock cycle, described above, peripheral device 830 tri-states its speaker output during the period during which both STPACTV and STPRDY are high (see FIG. 6a). Host platform interface circuitry 815 drives SPKROUT 805 low. In another embodiment of the invention, host platform interface circuitry 815 tri-states its speaker output rather than driving SPKROUT 805 low. Even during such a stop clock cycle, however, peripheral device 830 remains synchronized to the correct phase of ATCLK and does not resynchronize on the next ALE.
Automatic Voltage Threshold Detection
CISA devices in accordance with the invention can utilize either a 5 v bus or a 3.3 v bus and can detect which threshold is being used automatically, without using external circuitry. To detect a 5 v threshold, host platform interface circuitry 115 asserts the ALE signal to a logical high when RST also goes to a logical high. The host keeps ALE asserted for at least one-half ATCLK cycle and at most one ATCLK cycle after RST goes to a logical low. To automatically detect a 3.3 v threshold, host platform interface circuitry 115 keeps the ALE signal at a logical low when RST goes to a logical high and maintains ALE at a logical low for at least one-half ATCLK cycles after RST goes to a logical low.
The invention has been described with respect to particular embodiments thereof, and it will be understood that numerous modifications are possible within the scope of the invention as set forth in the claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method of interfacing a host system with a peripheral device, comprising the steps of: (a) communicating address information between said host system and said peripheral device on a bus; (b) communicating data information between said host system and said peripheral device on said bus; (c) communicating ISA command information between said host system and said peripheral device on said bus; wherein said address information, said data information, and said ISA command information are multiplexed on said bus.
2. The method of claim 1, wherein step (c) occurs simultaneously with step (a).
3. The method of claim 1, where in step (c), command information includes a cycle type and a cycle direction.
4. The method of claim 1, wherein step (a) includes communicating a first part of said address information on said bus and subsequently communicating a second part of said address information on said bus.
5. The method of claim 1, further including the steps of: communicating interrupt request information on said bus; and communicating DMA request information on said bus.
6. The method of claim 1, wherein said steps of communicating each respectively include the step of transmitting.
7. The method of claim 1, wherein said steps of communicating each respectively include the step of receiving.
8. An interface structure for interfacing a host platform with a peripheral device, comprising: a clock signal line coupled between said host platform and said peripheral device for carrying a clock signal; a bus coupled between said host platform and said peripheral device, said bus carries, in a first mode of operation, address information during an address phase of a first cycle and data information during a data phase of said first cycle, wherein said address information is multiplexed on said bus with said data information such that said data phase follows said address phase in said first cycle, said bus carries, in a second mode of operation, interrupt request information during an interrupt request phase of a second cycle and DMA request information during a DMA request phase of said second cycle, wherein said interrupt request information is multiplexed on said bus with said DMA request information such that said DMA request phase follows said interrupt request phase in said second cycle, and said bus for further carrying, in said first mode of operation, signals indicating a selected address space, a cycle type, a data transfer direction, and cycle timing; an enable signal line coupled between said host platform and said peripheral device for carrying a signal at least indicating that said address information is valid in said first mode of operation; a peripheral device ready signal line coupled between said host platform and said peripheral device for carrying a peripheral device reading! ready signal indicating whether said peripheral device is ready to complete said first cycle in said first mode of operation; a device selected-backoff signal line coupled between said host platform and said peripheral device for carrying, in said first mode of operation, a device selected signal indicating, whether said first cycle belongs to said peripheral device, and in said second mode of operation, a backoff signal indicating whether said host platform should inhibit host platform access to said bus; and a command signal line coupled between said host platform and said peripheral device for carrying a timing signal indicating a time frame when an information transfer should take place.
9. The interface structure of claim 8, wherein said timing signal carried on said command signal line indicates when an information transfer should take place in combination with said clock signal and, in said first mode of operation, said peripheral device ready signal; and in said second mode of operation, said backoff signal.
10. The interface structure of claim 8, wherein said selected address space includes one of a memory address space and an I/O address space.
11. The interface structure of claim 8, wherein said cycle type includes one of an I/O cycle, a DMA acknowledge cycle, a memory cycle, and a configuration cycle.
12. The interface of claim 11, wherein: said cycle type is a configuration cycle; said host platform inhibits said clock signal to said peripheral device; and said device selected-backoff signal line carries a signal indicating that said clock signal should be restarted.
13. The interface structure of claim 8, wherein said data transfer direction includes one of a read direction and a write direction.
14. The interface structure of claim 8, wherein said cycle timing includes one of fast timing and slow timing.
15. The interface structure of claim 8, wherein said second mode of operation is indicated by a signal on said enable signal line in combination with said clock signal, a signal on said selected-backoff signal line and a signal on said command signal line.
16. The interface structure of claim 8, wherein said address information includes a first information part and a second information part, and said address phase includes a first address sub-phase and a second address sub-phase, wherein said address-data bus carries said first information part during said first address sub-phase and said second information part during said second address sub-phase, and wherein said first information part is multiplexed with said second information part on said bus.
17. The interface of claim 8, further comprising: a speaker; logic level holding means coupled to said speaker; a speaker output line coupled between said host platform, said peripheral device and said logic level holding means, said speaker output line carrying a first speaker output signal of a first level; and said logic level holding means maintaining said signal at said first level for at least a time period.
18. The interface structure of claim 8, further comprising: a reset signal line coupled between said host platform and said peripheral device for carrying a reset signal; said enable signal line carrying a second signal indicating, in combination with said reset signal and said clock signal, a voltage threshold level.
Patent Citations (16)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5109517 | 1992-04-01 | Houda et al. | |
| US5125080 | 1992-06-01 | Pleva et al. | |
| US5379403 | 1995-01-01 | Turvy | |
| US5467295 | 1995-11-01 | Young et al. | |
| US5511224 | 1996-04-01 | Tran et al. | |
| US5564114 | 1996-10-01 | Popat et al. | |
| US5574866 | 1996-11-01 | Smith et al. | |
| US5586294 | 1996-12-01 | Goodwin et al. | |
| US5592632 | 1997-01-01 | Leung et al. | |
| US5613075 | 1997-03-01 | Wade et al. | |
| US5617559 | 1997-04-01 | Le et al. | |
| US5632020 | 1997-05-01 | Gephardt et al. | |
| US5649125 | 1997-07-01 | Tietjen et al. | |
| US5651137 | 1997-07-01 | MacWilliams et al. | |
| US5748982 | 1998-05-01 | Smith et al. | |
| US5794070 | 1998-08-01 | Rabe et al. |