WO2003029997A1 - Systeme bus et interface bus - Google Patents

Systeme bus et interface bus Download PDF

Info

Publication number
WO2003029997A1
WO2003029997A1 PCT/IB2002/003820 IB0203820W WO03029997A1 WO 2003029997 A1 WO2003029997 A1 WO 2003029997A1 IB 0203820 W IB0203820 W IB 0203820W WO 03029997 A1 WO03029997 A1 WO 03029997A1
Authority
WO
WIPO (PCT)
Prior art keywords
bus
processor
station
usb
bus interface
Prior art date
Application number
PCT/IB2002/003820
Other languages
English (en)
Inventor
Yeow K. Chang
Zhenyu Zhang
Original Assignee
Koninklijke Philips Electronics N.V.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Koninklijke Philips Electronics N.V. filed Critical Koninklijke Philips Electronics N.V.
Priority to KR10-2004-7004359A priority Critical patent/KR20040043198A/ko
Priority to EP02800198A priority patent/EP1433070A1/fr
Priority to JP2003533134A priority patent/JP2005504393A/ja
Publication of WO2003029997A1 publication Critical patent/WO2003029997A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/24—Handling requests for interconnection or transfer for access to input/output bus using interrupt
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4247—Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus
    • G06F13/426—Bus transfer protocol, e.g. handshake; Synchronisation on a daisy chain bus using an embedded synchronisation, e.g. Firewire bus, Fibre Channel bus, SSA bus

Definitions

  • the invention relates to a bus system comprising a first station and a second station coupled by a bus for transferring data and control signals, said bus operating according to a protocol in which said first station repeatedly sends requests to said second station and said second station responds to said requests.
  • the invention also relates to a bus interface comprising a connection for a bus and an interrupt output for applying an interrupt to an interruptible processor.
  • USB Universal Serial Bus
  • USB Computer Corporation, Hewlett-Packard Company, Intel Corporation, Lucent Technologies Inc, Microsoft Corporation, NEC Corporation, and Koninklijke Philips Electronics N.V. Described below are various aspects of the USB relevant to a complete understanding of the present invention. Further background concerning the USB may be obtained from USB Specification, Revision 2.0, which is included herein by reference.
  • the USB is a standard bus designed to support data exchange between a personal computer and a wide variety of peripherals such as webcams, printers, scanners, microphones and keyboards.
  • the USB thus replaces existing interfaces such as the RS-232C serial ports, parallel ports, and PS/2 interfaces.
  • Further developments of the USB aim at bus systems where another apparatus replaces the personal computer.
  • Such an apparatus could be, for example, a digital still camera, a video camera, a personal digital assistant, or a cellular phone.
  • USB stations are defined as hosts (e.g. personal computers) and as devices (peripherals). In general there is only one host on any USB system.
  • a USB interface at the host is also referred to as a host controller.
  • the host controller may be implemented in a combination of hardware, firmware, or software.
  • USB devices are defined as hubs which provide additional attachment points or functions which provide capabilities to the system. The devices are connected to the host via a tiered-star topology. Hubs indicate the attachment or removal of a USB device.
  • the host determines if a newly attached USB device is a hub or a function and assigns a unique USB address to the USB device. All USB devices are accessed by a unique USB address. Each device additionally supports one or more endpoints with which the host may communicate. The following description will be limited to USB devices defined as functions.
  • the USB is a polled bus.
  • the host controller initiates all data transfers. Most bus transactions involve the transmission of up to three packets. Each transaction begins when the host controller, on a scheduled basis, sends a USB packet describing the type and direction of the transaction, the USB device address, and endpoint number. This packet is referred to as the "token packet".
  • the USB device that is addressed selects itself by decoding the appropriate address fields.
  • data is transferred either from the host to a device or from a device to the host.
  • the direction of data transfer is specified in the token packet.
  • the source of the transaction then sends a data packet or indicates it has no data to transfer.
  • the destination in general, responds with a handshake packet indicating whether the transfer was successful.
  • the USB architecture comprehends three basic types of data transfer: (1) isochronous transfers: periodic, continuous communication between host and device, typically used for time-relevant information, which occupies a pre-negotiated amount of USB bandwidth with a pre-negotiated latency; (2) interrupt transfers: low-frequency, bounded latency communication, typically used for asynchronous data such as characters or coordinates with human perceptible echo or feedback response characteristics, and; (3) bulk transfers: non-periodic, large-packet bursty communication, typically used for data that can use any available bandwidth and can also be delayed until bandwidth is available.
  • bus station, host and device comprise a processor or computing system to either process or generate data or to control the flow of data or both.
  • USB system A straightforward implementation of a USB system as described above could lead to a significant overhead for both the processor in the bus station acting as a host and the processor in the bus station acting as a device. This holds especially for the interrupt transfers. Due to the polled nature of the bus system, the host needs to interrogate the involved device, for instance a keyboard, on a regular basis and to evaluate the returned responses. It is inter alia an object of the invention to reduce the amount of overhead needed to transport data from a processor in a first station of a bus system to a second station of the bus system or vice versa.
  • the invention provides a bus system as defined in the opening paragraph which is characterized in that said first station comprises an interruptible processor and a bus interface, where said bus interface is operable for interrupting said interruptible processor upon reception of selected responses of said second station, and said interruptible processor is operable to handle the interrupts of said bus interface.
  • the processor within the first station needs to provide information to the second station or needs to obtain information from the second station.
  • the first station needs to communicate with the second station.
  • a polled bus system such as a USB system
  • the communication is initiated by the first station, being a host in a USB system.
  • the second station being a device in a USB system
  • the second station is only capable of receiving or providing data on an irregular basis, it happens frequently that the first station needs to poll the second station quite a number of times before a successful transfer of information takes place. In other words, under these circumstances the first station needs to evaluate the responses of the second station relatively often before a successful transfer of information takes place.
  • the second station may respond by sending a message with a data item acknowledge signal, a negative acknowledge signal, by sending a signal to indicate it is stalled. Furthermore, if the second station does not respond by sending a signal, or if no signal is received by the first station due to an error in the communication between the first station and the second station, this may be interpreted as a response too. Thus, the selected responses may comprise the absence of a response signal from the second station.
  • a bus interface interface comprises a connection for a bus and an interrupt output for applying an interrupt to an interruptible processor and is characterized in that it also comprises a controller operable to receive responses from said connection and to interrupt said processor upon reception of selected responses by sending an interrupt signal to the interrupt output.
  • Fig. 1 is a diagram showing the interrupt transaction format as specified in the
  • Fig. 2 is a block diagram showing a bus system according to the invention.
  • Fig. 3 A is a message diagram showing transactions for data transmission
  • Fig. 3B is a message diagram showing transactions for data transmission
  • Fig. 4 is a block diagram showing a bus interface according to the invention.
  • Fig. 5 is schematic overview of a buffer organized in a first-in, first-out manner.
  • identical parts are denoted by identical references.
  • Fig. 1 is a diagram showing the interrupt transaction format as specified in the USB specification, revision 2.0.
  • All USB devices are accessed by a unique USB address.
  • Each device additionally supports one or more endpoints with which the host may communicate.
  • the USB supports functional data and control exchange between the USB host and USB devices.
  • USB data transfers take place between host software and a particular endpoint on a USB device.
  • the USB architecture comprehends three basic types of transfer: isochronous transfers: isochronous or streaming real time data which occupies a prenegotiated amount of USB bandwidth with a pre-negotiated latency; interrupt transfers: asynchronous interactive data such as characters or coordinates with human perceptible echo or feedback response characteristics, and bulk transfers: asynchronous block transfer data which is generated or consumed in relatively large and bursty quantities and has wide dynamic latitude and transmission constraints.
  • Bus transactions including data transfers generally involve three stages: a Setup stage 102, a Data stage 103, and a Status stage 104.
  • Bus transactions including data transfers generally involve the transmission of three different packets, e.g. a Token packet 105, 106, a Data packet 107, 108, and a Handshake packet 109, 110, 111, 112, 115, 116.
  • Interrupt transactions may consist of IN transfers or OUT transfers.
  • the USB host will start the transaction by sending an IN token 105.
  • a USB device may return data 107, a negative acknowledge signal (NAK) 111, or a signal indicating the USB device is unable to complete a command (STALL) 112. If the endpoint has no new interrupt information to return (i.e. no interrupt is pending), the USB device returns a NAK handshake 111 during the Data stage 103.
  • NAK negative acknowledge signal
  • the USB device If the USB device is unable to complete a command, the USB device returns a STALL handshake 112. If an interrupt is pending the USB device returns the interrupt information as a Data packet 107.
  • the USB host in response to receipt of the Data packet 107 issues either an ACK handshake 109 (acknowledge signal) if the data was received error- free or returns no handshake, indicated by line 113, if the Data packet 107 was received corrupted. Furthermore the USB host will not issue an ACK 109 in case no response to the IN token 105 is received at all from the USB device. This situation is indicated by line 114. After completion of the IN transfer, the USB system returns to the Idle mode 101.
  • the USB host will start the transaction by sending an OUT token 106. This is followed by sending a Data packet 108.
  • the USB device may issue in the Status stage 104 an ACK handshake 110 if the data was received error free, a NAK handshake 115 indicating the device is not able to process the data, or a STALL handshake 116 indicating the USB device is currently stalled.
  • the USB device returns no handshake, indicated by line 117, if the Data packet 107 was received corrupted.
  • the USB device will not issue an ACK handshake 110 in case it does not receive data from the USB host, a situation indicated by line 118. After completion of the OUT transfer the USB system returns to the Idle mode 101.
  • All packets begin with a SYNC field, which is used by input circuitry to align incoming data with a local clock.
  • a packet identifier (PID) immediately follows the SYNC field of every USB packet.
  • the PID consists of a four-bit ID field followed by a four-bit check field.
  • the PID indicates the type of packet (e.g. Token 105, 106, Data 107, 108, and Handshake 109, 110, 111, 112, 115, 116) and the format ofthe packet along with the type of variant detection applied to the packet.
  • the four-bit check field ofthe PID ensures reliable decoding.
  • a Token packet 105, 106 includes an ADDR field which specifies the target USB device, via its USB address, that is the source or destination of a Data packet 107, 108, depending on the value ofthe Token PID. USB devices must perform a complete decoding of the ADDR field.
  • a Data packet 107, 108 includes a data field which may range from zero to N bytes and must amount to integral numbers of bytes. Data bits within each byte are shifted out most significant bit first. The data field of a Data packet is divided into fields which give extra information to the USB device regarding the request being made. One field, the command code, tells what the targeted USB device should do, such as set up a read from a USB device space or set up a write to a USB device space.
  • the read space command is used to request information from a given location in a given space of a USB device.
  • the command is used to set up the read, which is followed by a request from the host for the USB device to send data.
  • the USB device then sends the data it has retrieved from the previously specified space.
  • the write space uses exactly the same definition as the read space. However, the Data packet contains data transferred by the host to the USB device.
  • a Handshake packet 109, 110, 111, 112, 115, 116 consists of only a PID. As indicated above Handshake packets are used to report the status of a data transfer and can return values indicating successful reception of data, CRC failure, flow control, and certain fault conditions.
  • Fig. 2 is a block diagram showing a bus system according to the invention.
  • the bus system 201 comprises a first station 202, acting as a USB host, and second stations 203 and 204, acting as USB devices.
  • the stations 202, 203, 204 are coupled by bus connections 205.
  • the first station 202 is shown in more detail. It comprises an interruptible processor 206 and a bus interface 207.
  • the bus interface comprises a buffer 208 and a controller 209. It is not necessary that the buffer is part ofthe bus interface. In an alternative arrangement the buffer could be placed within the first station 202, but outside the bus interface. Both the processor 206 and the controller 209 have access to the buffer 208.
  • the controller is coupled to the bus connections 205. Furthermore, the controller 209 has an interrupt connection 210 to the processor 206. Fig.
  • FIG. 3 A is a message diagram showing transactions for data transmission.
  • the message diagram illustrates the operation ofthe system of Fig. 1 for interrupt transactions consisting of IN transfers. Going top-down the time increases.
  • Information exchange between the processor 206 and the bus interface 207 is symbolized by arrows between a first line 301 and a second line 302.
  • Information exchange between the bus interface and the second station 203, 204 is symbolized by arrows between the second line 302 and a third line 303.
  • the processor 206 requires data from one ofthe second stations 203, 204, a USB device.
  • the bus interface 207 should repeatedly issue a request for data to the bus connections 205. To reduce the communication overhead for the processor it should be sufficient to have the processor provide the request properties only once. If the addressed
  • USB device returns data
  • the bus interface 207 should interrupt the processor via the interrupt connection and provide the processor with the data. In case an error occurs the processor should also be notified. In these situations the bus interface 207 should apply an interrupt to the processor too. In other situations no action is required from the processor, so that the bus interface 207 should not interrupt the processor.
  • the processor 206 in a message 309 sends the request properties to the bus interface 207, where the request properties are stored in the buffer. Based on the request properties within the message 309, which are retrieved from the buffer, the bus interface 207 initiates the IN transfer by issuing an IN token 310 on the bus. The second station, the addressed USB device, responds by sending a message 311 with a data item. Upon reception of this message the bus interface 207 sends an interrupt signal 312, via the interrupt connection 210, to the processor 206 to inform the processor 206 that new data is available. Furthermore, it issues an Acknowledge signal 313 to the addressed USB device. This completes the IN transfer 304.
  • the bus interface 207 again retrieves the request properties from the buffer, while no new information is required from the processor 206.
  • the bus interface 207 initiates the IN transfer by issuing an IN token 314 on the bus.
  • the addressed USB device responds by sending a message 315 with a data item. Due to an error on the bus the second message 315 is received corrupted by the bus interface 207. Therefore, the bus interface 207 does not issue an ACK handshake. Instead it sends an interrupt signal 316 via the interrupt connection 210 to the processor 206 to inform the processor 206 an error occurred. This completes the IN transfer 305.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the IN transfer by issuing an IN token 317 on the bus. Due to a bus error the IN token 317 is received corrupted at the addressed USB device. For this reason it does not respond to the IN token 317.
  • the bus interface 207 sends an interrupt signal 318, via the interrupt connection 210, to the processor 206 to inform the processor 206 an error occurred. This completes the IN transfer 306.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the IN transfer by issuing an IN token 319 on the bus.
  • the addressed USB device responds with a NAK handshake 320, indicating it has no data available. This completes the IN transfer 307.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the IN transfer by issuing an IN token 321 on the bus.
  • the addressed USB device responds with a STALL handshake 322, indicating it cannot complete the command.
  • the bus interface 207 sends an interrupt signal 323 via the interrupt connection 210 to the processor 206. This completes the IN transfer 308.
  • Fig. 3B is a message diagram showing transactions for data transmission.
  • the message diagram illustrates the operation ofthe system of Fig. 1 for interrupt transactions consisting of OUT transfers. Going top-down the time increases.
  • Information exchange between the processor 206 and the bus interface 207 is symbolized by arrows between a first line 301 and a second line 302.
  • Information exchange between the bus interface and the second station 203, 204 is symbolized by arrows between the second line 302 and a third line 303.
  • the processor 206 needs to transfer data to one ofthe second stations 203, 204, a USB device.
  • the bus interface 207 should repeatedly issue a request to receive data to the bus connections 205. To reduce the communication overhead for the processor 206 it should be sufficient to have the processor 206 provide the request properties only once. If the addressed USB device accepts data the bus interface 207 should interrupt the processor via the interrupt connection and inform the processor. In case an error occurs the processor 206 should also be notified. In these situations the bus interface 207 should apply an interrupt to the processor 206 too. In other situations no action is required from the processor 206, so that the bus interface 207 should not interrupt the processor 206.
  • a OUT transfer 324 the processor in a message 329 sends the request properties to the bus interface 207, where the request properties are stored in the buffer. Based on the request properties within the message 329, which are retrieved from the buffer, the bus interface 207 initiates the OUT transfer by issuing an OUT token 330 on the bus. Subsequently, the bus interface issues a Data packet 331. The second station, the addressed USB device, responds by sending an ACK handshake 332. Upon reception ofthe ACK handshake 332, the bus interface 207 sends an interrupt signal 333, via the interrupt connection 210, to the processor 206 to inform the processor 206 that the data is transferred successfully. In a different arrangement the bus interface 207 does not send the interrupt signal 332 to the processor 206, since the processor 206 will assume that a successful transmission ofthe data has occurred if it is not interrupted.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the OUT transfer by issuing an OUT token 334 on the bus. Subsequently, the bus interface issues a Data packet 335.
  • the addressed USB device responds by issuing a NAK handshake 336 to indicate it is not ready to process the transferred data. This completes the OUT transfer 325.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the OUT transfer by issuing an OUT token 337 on the bus. Subsequently, the bus interface issues a Data packet 338.
  • the USB device sends a STALL handshake 339 to indicate it cannot process the OUT transfer.
  • the bus interface sends an interrupt signal 340 via the interrupt connection, to the processor 206 to inform the processor on the status ofthe addressed USB device. This completes the OUT transfer 326.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the OUT transfer by issuing an OUT token 341 on the bus. Subsequently, the bus interface issues a Data packet 342. Due to an error on the bus the Data packet 342 is received corrupted by the addressed USB device. For this reason the addressed USB device does not respond.
  • the bus interface 207 sends an interrupt signal 343 via the interrupt connection 210, to the processor 206 so as to notify the processor. This completes the OUT transfer 327.
  • the bus interface 207 again retrieves the request properties from the buffer 208, while no new information is required from the processor 206.
  • the bus interface 207 initiates the OUT transfer by issuing an OUT token 344 on the bus. Due to the occurrence of an error condition the bus interface does not start or complete an already started issuing of a subsequent Data packet. For this reason the bus interface 207 sends an interrupt signal 345 via the interrupt connection 210, to the processor 206 so as to notify the processor. This completes the OUT transfer 328.
  • Fig. 4 is a block diagram showing a bus interface according to the invention.
  • the block diagram shown in the figure is a block diagram of a bus interface integrated circuit.
  • the bus interface integrated circuit 401 has a dual role. It can be both part of a bus station acting as a USB device and of a bus station acting as a USB host. This is especially useful in a USB On-The-Go (OTG) apparatus.
  • OTG On-The-Go
  • Such a USB OTG apparatus could be, for example, a digital still camera, a digital video camera, a personal digital assistant, or an oscilloscope, which in a certain mode of operation is connected, via USB, for example, to a mass storage apparatus (e.g.
  • USB OTG apparatus In this mode of operation the USB OTG apparatus should act as a USB host. In another mode of operation the USB OTG is connected, via USB, for example, to a personal computer. In this mode of operation the USB OTG apparatus should act as a USB device.
  • the mode in which the bus interface integrated circuit ofthe USB OTG apparatus operates could be software determined and controlled by a processor within the USB OTG apparatus.
  • USB OTG apparatus In case the USB OTG apparatus is portable it could be advantageous to include a low power consumption mode available in which the bus interface integrated circuits shuts down certain functional blocks or operates at a lower clock speed in time periods with, for example, low bus traffic or no bus traffic at all.
  • a low power consumption mode could be enhanced by including a so-called remote wake-up feature, controlled by the processor ofthe USB OTG apparatus to bring back to operation certain or all functional blocks or to increase the clock speed ofthe bus interface integrated circuit.
  • the remote wake-up feature could be activated, for example, if the processor anticipates increased bus traffic.
  • the bus interface integrated circuit 401 comprises a connection 402 with an processor, a connection 403 for connection to a USB in case the bus interface integrated circuit 401 operates as a USB host, and a connection 404 for connection to a USB in case the bus interface integrated circuit 401 operates as a USB device.
  • connections 403 and 404 could share the same I/O terminals, while an internal multiplexer takes care ofthe internal routing ofthe bus signals. Such an implementation could be advantageous in case it is guaranteed that connections 403 are not used simultaneously.
  • the bus interface integrated circuit 401 also comprises a host-device multiplexer 405, a timing block 406, a host interface 407, a device interface 408, a host controller 409, a device controller 410, a host buffer 411, a device buffer 412, a host transceiver 413, and a device transceiver 414.
  • the host-device multiplexer 405 is connected to the connection 402 with the processor. Preferably under the control ofthe processor it determines the internal routing of the communication ofthe bus interface integrated circuit 401 with the processor. In case the bus interface integrated circuit 401 operates as a USB host, the host-device multiplexer 405 links the host controller 409, via the host interface 407, to the processor. In case the bus interface integrated circuit 401 operates as a USB device, the host-device multiplexer links the device controller 410, via the device interface 408, to the processor.
  • the device controller 409 has access to the bus connection 403 via the host transceiver 413.
  • the device controller 409 has access to the bus connection 403 via the host transceiver 413.
  • the host buffer 411 is accessible by both the host controller 409 and via the host-device multiplexer 405, by the processor. It can be used, for example, for storing request properties issued by the processor and for storing results ofthe communication between the host controller 411 and a USB device.
  • the device buffer 412 is accessible by both the device controller 410 and via the host-device multiplexer 405, by the processor. It can be used, for example, for buffering data generated by the processor, so as to be sent to a USB host.
  • the host buffer 411 and the device buffer 412 are preferably accessible by the processor in both a direct memory access (DMA) mode and a parallel input- output mode.
  • DMA direct memory access
  • Fig. 5 is schematic overview of a buffer 501 organized in a first-in, first-out (FIFO) manner. This in an efficient manner to organize the host buffer 411.
  • the top ofthe FIFO buffer is indicated by an arrow 502.
  • the bottom ofthe FIFO buffer is indicated by an arrow 503.
  • the buffer stores request properties of several requests 504, 505, 506, for example, for initiating USB transactions or more in particular USB interrupt transactions.
  • the request properties first issued are indicated by 504, the request properties issued second are indicated by 505, the request properties issued last are indicated by 506.
  • the area 507 indicates the remaining request properties, while the area 508 indicates the remaining space in the FIFO buffer not being used.
  • Request properties are divided in two parts: a transfer descriptor or header 509 and, if applicable, payload data 510.
  • the transfer descriptor 509 describes the characteristics ofthe transaction to be handled by the host controller 409.
  • the payload data 510 is the data that should be included in the Data packet of the transaction to be handled by the host controller.
  • the transfer descriptor is also used by the host controller 409 to store the results of transactions. Therefore, both the processor and the host controller 409 have access to the FIFO buffer 501.
  • the buffer in a first-in first-out mode. In this way it is relatively simple to access the data stored in the buffer for both the processor as the controller.
  • the buffer it is advantageous to use the buffer to store both request properties and the results ofthe communication with the second station.
  • the processor can access the buffer in an identical way as when it writes the request properties, only the type of access has to changed from a write mode to a read mode.
  • the bus interface determine the exact polling interval based on information provided by the processor. Limiting the number of possible polling rates simplifies the task ofthe bus interface in handling different requests with different polling rates.
  • the bus interface maps the chosen polling rate to one ofthe following actual polling rates: 1, 2, 4, 8, 16, 32, 64, or 128 milliseconds, thus reducing the potential number of different polling rates to handle from 128 to 8.
  • the bus interface maps the polling rate chosen by the processor on the actual polling rate that is closest to the chosen polling rate.
  • the table below shows a format ofthe transfer descriptor. The format shown consists of 8 bytes, indicated as Byte 0, Byte 1, ..., Byte 7. Every byte consists of 8 bits, enumerated as 0, 1, ..., 7.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Systems (AREA)
  • Bus Control (AREA)

Abstract

L'invention concerne un système bus comprenant une première station (202) et une seconde station (203, 204) reliées par un bus destiné au transfert de données et de signaux de commande. Le bus est conçu pour fonctionner selon un protocole dans lequel la première station (202) transmet sans cesse des demandes à la seconde station (203, 204) et la seconde station répond à ces demandes. La première station (202) comprend un processeur interruptible (206) et une interface bus (207). L'interface bus (207) peut interrompre le processeur interruptible (206) sur réception de réponses sélectionnées de la seconde station (203, 204). Le processeur interruptible (206) peut gérer les interruptions de l'interface bus (207).
PCT/IB2002/003820 2001-09-27 2002-09-16 Systeme bus et interface bus WO2003029997A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR10-2004-7004359A KR20040043198A (ko) 2001-09-27 2002-09-16 버스 시스템 및 버스 인터페이스
EP02800198A EP1433070A1 (fr) 2001-09-27 2002-09-16 Systeme bus et interface bus
JP2003533134A JP2005504393A (ja) 2001-09-27 2002-09-16 バス・システムおよびバス・インターフェース

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SG0100195 2001-09-27
SGPCT/SG01/00195 2001-09-27

Publications (1)

Publication Number Publication Date
WO2003029997A1 true WO2003029997A1 (fr) 2003-04-10

Family

ID=20428994

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2002/003820 WO2003029997A1 (fr) 2001-09-27 2002-09-16 Systeme bus et interface bus

Country Status (7)

Country Link
US (1) US7043589B2 (fr)
EP (1) EP1433070A1 (fr)
JP (1) JP2005504393A (fr)
KR (1) KR20040043198A (fr)
CN (1) CN1561491A (fr)
TW (1) TW583572B (fr)
WO (1) WO2003029997A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7469343B2 (en) * 2003-05-02 2008-12-23 Microsoft Corporation Dynamic substitution of USB data for on-the-fly encryption/decryption
JP2005176233A (ja) * 2003-12-15 2005-06-30 Canon Inc 通信装置及び通信システム
US7413129B2 (en) * 2004-09-30 2008-08-19 Stmicroelectronics, Inc. USB device with secondary USB on-the-go function
DE102005009021A1 (de) * 2005-02-28 2006-09-07 Advanced Micro Devices Inc., Sunnyvale Vereinheitliche USB OTG-Steuerungseinheit
TWI321011B (en) * 2005-12-30 2010-02-21 Altek Corp Portable electronic device for sharing a common storage device via by-pass mode
CN102103560A (zh) * 2009-12-16 2011-06-22 中兴通讯股份有限公司 用于系统总线的防死锁方法及装置
EP2602959B1 (fr) * 2011-12-06 2014-06-04 FESTO AG & Co. KG Noeud de bus et système de commande
US9817468B2 (en) 2014-02-03 2017-11-14 Dell Products, Lp System and method for automatic detection and switching between USB host and device rolls on a type-A connector
US9804942B2 (en) 2014-06-10 2017-10-31 Analog Devices, Inc. Safety node in interconnect data buses

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6145045A (en) * 1998-01-07 2000-11-07 National Semiconductor Corporation System for sending and receiving data on a Universal Serial Bus (USB) using a memory shared among a number of end points

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS60126945A (ja) * 1983-12-14 1985-07-06 Hitachi Ltd ポ−リング方式
JPH0771094B2 (ja) * 1989-05-19 1995-07-31 オムロン株式会社 通信ネットワークシステム
US5675807A (en) * 1992-12-17 1997-10-07 Tandem Computers Incorporated Interrupt message delivery identified by storage location of received interrupt data
EP0652523B1 (fr) * 1993-11-10 1999-06-02 Nec Corporation Système de surveillance à distance
JPH07210537A (ja) * 1993-12-10 1995-08-11 Advanced Micro Devicds Inc コンピュータシステム
EP0776504B1 (fr) * 1995-05-26 2004-08-18 National Semiconductor Corporation Circuit integre a fonctions multiples partageant des bus de signal internes multiples pour distribuer des controles d' acces au bus et d'arbitrage
US5903912A (en) * 1996-08-14 1999-05-11 Advanced Micro Devices, Inc. Microcontroller configured to convey data corresponding to internal memory accesses externally
US5948097A (en) * 1996-08-29 1999-09-07 Intel Corporation Method and apparatus for changing privilege levels in a computer system without use of a call gate
US5854908A (en) * 1996-10-15 1998-12-29 International Business Machines Corporation Computer system generating a processor interrupt in response to receiving an interrupt/data synchronizing signal over a data bus
US6058440A (en) * 1997-09-05 2000-05-02 Intel Corporation Programmable and adaptive resource allocation device and resource use recorder
US6449663B1 (en) * 1998-07-08 2002-09-10 International Business Machines Corporation Method and apparatus for adjusting an interval of polling a network printer based on changes in working status of the network printer
US6640268B1 (en) * 1998-08-28 2003-10-28 Intel Corporation Dynamic polling mechanism for wireless devices
US6665807B1 (en) * 1998-09-04 2003-12-16 Hitachi, Ltd. Information processing apparatus
US6742076B2 (en) * 2000-01-03 2004-05-25 Transdimension, Inc. USB host controller for systems employing batched data transfer
US6691190B1 (en) * 2000-01-24 2004-02-10 Agere Systems Inc. Inter-DSP data exchange in a multiple DSP environment
US6751724B1 (en) * 2000-04-19 2004-06-15 Motorola, Inc. Method and apparatus for instruction fetching

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6145045A (en) * 1998-01-07 2000-11-07 National Semiconductor Corporation System for sending and receiving data on a Universal Serial Bus (USB) using a memory shared among a number of end points

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Universal Host Controller Interface (UHCI) Design Guide", March 1996, INTEL CORP., XP002225237 *

Also Published As

Publication number Publication date
TW583572B (en) 2004-04-11
KR20040043198A (ko) 2004-05-22
JP2005504393A (ja) 2005-02-10
CN1561491A (zh) 2005-01-05
US7043589B2 (en) 2006-05-09
EP1433070A1 (fr) 2004-06-30
US20030101298A1 (en) 2003-05-29

Similar Documents

Publication Publication Date Title
US7349973B2 (en) Data transfer control device, electronic equipment, and data transfer control method
JP3636157B2 (ja) データ転送制御装置、電子機器及びデータ転送制御方法
US20160224490A1 (en) Command queue for communication bus
US6898751B2 (en) Method and system for optimizing polling in systems using negative acknowledgement protocols
US7058747B2 (en) Bus system and bus interface for connection to a bus
US7028111B2 (en) Bus system and bus interface for connection to a bus
US20050091564A1 (en) Data transfer control device, electronic instrument, and data transfer control method
US7043589B2 (en) Bus system and bus interface
US7359996B2 (en) Data transfer control device, electronic equipment, and data transfer control method
US7469304B2 (en) Data transfer control device, electronic equipment, and method for a data transfer through a bus, the data transfer control device including a register and a packet buffer that are commonly used during a host operation and a peripheral operation
EP1516261A2 (fr) Systeme de bus, station utilisee dans un systeme de bus, et interface de bus
JP3636160B2 (ja) データ転送制御装置、電子機器及びデータ転送制御方法
JP4127071B2 (ja) データ転送制御装置、電子機器及びデータ転送制御方法
JP2003316730A (ja) データ転送制御装置、電子機器及びデータ転送制御方法
JP2003316734A (ja) データ転送制御装置、電子機器及びデータ転送制御方法
JP2003323391A (ja) データ転送制御装置、電子機器及びデータ転送制御方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): CN JP

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FR GB GR IE IT LU MC NL PT SE SK TR

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2002800198

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2003533134

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 1020047004359

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 20028190521

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2002800198

Country of ref document: EP

WWW Wipo information: withdrawn in national office

Ref document number: 2002800198

Country of ref document: EP