GB2519640A - Topology and bandwidth management for IO and inbound AV - Google Patents

Abstract

Enabling a sink device e.g. display monitor, to stream audio/visual content to a source device e.g. CPU or GPU, 152 over a display interface; and enabling the sink device to receive audio/visual (AV) and/or input/output (I/O) information from a source device 154 and to transmit AV and/or I/O information to a source device 156 over the display interface. DisplayPort(RTM) topology may be managed in the presence of sink devices that can stream A/V content to the source device, or can receive or transmit I/O information from/to the source device. This I/O information may include raw sensor data for a touch screen. The framework could be used to support or map other published I/O interface standards, over DisplayPort(RTM) interface. A high bandwidth receive path can be configured in the topology independent of the transmit path to support inbound I/O and AV functions. Both isochronous and bulk I/O transfers and inbound A/V can be supported.

Description

TOPOLOGY AND BANDWIDTH

MANAGEMENT FOR 10 AND INBOUND AV

Cross Reference to Related Applications

[0001] This application claims priority to provisional applications 6 1/868,682 filed August 22, 2013 and 61/879.253 filed September 18. 2013, both expressly incorporated by reference herein.

Background

[0002] A DisplayPort link consists of a main link, an auxiliary channel (AUX CH), and a Hot Plug Detect (HPD) signal line.

[0003] The main link is a unidirectional, high-bandwidth and low-latency channel used to transport isochronous data streams such as uncompressed video and audio.

[0004] The auxiliary channel is a half-duplex bidirectional channel used for link management and device control. The HPD signal also serves as an interrupt request by the sink device.

[0005] The current DisplayPort (DP) standard, available from VESA, (vl.2a) only streams audio and/or video out from a source device (e.g., a graphics processing unit (GPU) and its software) to a sink device (e.g., a local flat panel or an external monitor). In the extended DisplayPort specification (v.1.4), input/output (JO) support is limited to touch information transmitted in the form of processed Human Jrncrface Device (HID) packets that can be transported over the auxiliary (AUX) channel.

Brief Description Of The Drawins

[0006] Some embodiments are described with respect to the following figures: Figure 1 isa schematic depiction of TO layers in a DP MST device according to one embodiment; Figure 2 is a flow chart for an Isoeh 10 according to one embodiment; Figure 3 is a flow chart for an inbound bulk 10 according to one embodiment; Figure 4 is a flow chart for another embodiment; Figure 5 is a system depiction for one embodiment; and Figure 6 is a front elevational view of one embodiment

Detailed Description

[0007] In accordance with some embodiments. DisplayPort or other display interface topology sink devices can stream audio/visual (AV) content to a source device, or can receive or transmit 10 information from/to the source device. This 10 information may include raw sensor data for a touch screen, for example. A high bandwidth receive link (referred to as RX Link in this document) exists independently of the main link (ML). The RX Link can be trained independently of the ML.

[0008] 10 and inbound AV makc use of Virtual Channcls VCs) that arc establishcd using extensions to DP1.2a topology management primitives. The difference in various types of JO and AV arise essentially from where the VC is established, whether it is dedicated or shared, and the framework for quality of service (QoS).

[0009] There are two types of JO data herein: isochronous (also referred to as Isoch) and bulk. The main difference between the two types of JO is with respect to guarantees on timeliness of delivery: there are none with hulk 10.

[0010] Current solutions for touch screens only support transmission of processed HID reports over a standard AUX channel. Similarly the non-standard "white paper" proposal for Universal Serial Bus version 2 (USB 2.0) over DP1.2a Fast AUX is a proposal for one particular type of 10 over DisplayPort. The Universal Serial Bus (USB) 2.0 "proposal" involves a framework specifically for the purpose of supporting USB 2.0. These solutions do not target support for any other 10 type, and also do not target native support in DP for inbound audio and/or video streams.

10011] A more complete or generic native framework supports any kind ol JO (lsochronous or Bulk, with QoS or without, Inbound or Outbound. USB or PCIe or other 10 buses). -inbound audio and/or inbound video is treated as an independent capability than 10.

[0012] Inbound 10 is supported by the ability of a source to read a (large) block of data, optionally at a dcsircd frequcncy -with first in first out (FIFO) scmantics. Once established, the sink may ideally sustain transfer of data at that frequency after the initial configuration. Also for inbound JO. a source can read specific DisplayPort S Configuration Data (DPCD) registers where JO data is made available through DPCD registers; these accesses are performed using local or remote AUX transactions.

[()013] Outbound tO is supported by a source that can write a (large) block of data, optionally at a desired frequency -with FIFO semantics. In an ideal solution the sourcc sustains transfer of this block of data aftcr the initial configuration. Also, a source can write to specific DPCD registers for outbound IC) operations where needed; these accesses are performed using local or reniotc AUX transactions.

[0014] Different types of transactions can include isochronous 10 involving delivery at configured intervals and allocated link bandwidth, and Bulk JO involving best effort (in terms of time) delivery and maintains FIFO semantics.

[0015] JO and inbound audio/video (AV) functions are available when the Multi-stream transport (MST) link 18, including a sideband channel 18a with HPD and an auxiliary channel as well as main link 18b having Secondary Data Packets (SDPs), is configured to be in a bi-directional mode of operation. 10 layers on a DisplayPort source, branch or sink device are shown in Figure 1. Topology Management Layer 10 and Payload Bandwidth Management Layer 12 are extended to use message transactions on the bi-directional Main Link for inbound JO and inbound AV. Payload Mapper Layer 14 is an extension of the Stream-to-Virtual Channel mapping block to include virtual channel to stream mapping for inbound AV. virtual channel to data mapping for inbound JO, and data to virtual channel mapping for outbound JO. Topology Management Layer. Payload Bandwidth Management Layer, and the Payload Mapper are part of the DP version 1.2 standard (Jan. 2010) Isochronous Transport Layer 26.

[0016] 10 Policy Maker 16 resides in parallel to the Stream Policy Maker (18) and is responsible for implementing JO-related policies in the device. It functions in conjunction with Isoch 10 Manager 20 and Bulk 10 Manager Layers 22 to enable 10 capability in the device. Isoch JO Manager is responsible for virtual channel VC) establishment and management for isoch JO. Similarly. Bulk JO Manager is responsible for VC establishment and management, and data priority management/arbitration. JO Policy Maker. Isoch JO Manager, and Bulk tO Manager are part of the DPI.2 Virtual Channel Management Layer 24. They can use both the services provided by any members of the DP1.2 Isoch Transport Layer 26.

[0017] 10 Bridge Layer 28 is a client of the DPI.2 VC Management Layer, and contains bridgc protocols mapping abstractions made available to 10 interfaces such as Universal Serial Bus USB) or Peripheral Componcnt Interconnect cxtcndcd PCIc) onto JO Scrviccs exported by the DP 1.2 VC Management Layer. PCIe bridges target specific 10 buses.

There could also be a Generic JO Bridge 34 that provides a set of abstractions independent of specific JO buses.

[0018] 10 Services available from the DP1.2 VC Management Layer without the need for any bridging are called the Native 10 Services 36. In contrast, certain bridging functions may he needed to map existing 10 interfaces such as USB or PCIe onto the functionality defined in the DP specification. These blocks arc shown as USB Bridge 38 and PCIe Bridge 40 respectively.

10019] Applications using isochronous 10 42 and/or bulk 10 44 are layered above the 10 Policy Maker, and Isoch 10 and Bulk 10 Managers.

[0020] All the links along a given path in a topology are in bi-directional mode before any IC) data transfers or inbound AV streaming can he initiated on that path. This switch is initiated by the DP source dcvice on that path.

[0021] A DP sink device initiates REQUEST_BIDIRECTIONAL_MODE Message Transaction to request the DP source on the desired path to initiate a switch to bi-directional mode along that path; it does this when it desires to initiate an 10 data transfer.

[0022] Devices announce their ability to support bi-directional mode by setting the BIDIRECTIONAL_CAP bit in the MSTM_CAP DisplayPort Configuration Data (DPCD) register.

[0023] When a source desires to switch a link to hi-directional mode: (1) It sets the BIDIRECTIONAL_EN bit in the MSTM_CTRL DPCD register.

(2) Once it receives the Achiowledge (ACK) for the DPCD transaction in Step #1, it initiates a training sequence on the inbound link. The mechanisms and procedure described here can work on a variety of PHY layer implementations so long as they provide hi-directional access at link speeds sufficient to sustain the desired 10 and inbound AV transfer rates.

(3) It optionally rcads thc BIDIRECTIONAL_STATUS bits in SINK_STATUS DPCD rcgistcr in any downstrcam devicc to verify that the transition to Bidirectional modc is complete in that device.

[0024] When BIDIRECTIONAL_EN hit is set in a branch device on one of its input ports, it attempts to initiate a similar switch on any BIDIRECTIONAL-PHY capable device detected on its output ports.

10025] A high level sequence of operations for 10 data transfer is as follows: (1) DP source device allocates a VC along the desired path, if needed. The policy for VC allocation is controlled by the 10 Policy Maker on the DP Source. The 10 Policy Maker can optionally pre-allocate VCs for certain JO operations and not release them until such time as it no longer expects these tO operations to occur.

(2) DP source device configures all the devices along the given path for the upcoming 10 operation by using CONFIGURE_tO Message Transaction. VC Payload ID to he used for the upcoming 10 operations is one of the parameters iii CONFIGURE_b.

(3) Either the DP source or the DP sink initiates 10 data transfer(s) using the configuration received in the prcviou s stcp.

(4) DP source device releases the VC as per policies set by the 10 Policy Maker.

At a high level, similar sequences oloperations are used for inbound AV streaming also.

[0026] Inbound isoehronous transfers are used for AV streaming and for isoch JO data transfers from a sink to a source -potentially through a given number of intermediate branch devices.

[0027] VC for inbound isochronous transfers is allocated in the inbound path of the bidirectional Main Link using TB_ALLOCATE_PAYLOAD Message Transaction. This Message Transaction fails if any device along the path is not ready in hi-directional mode.

[0028] A detailed sequence for inbound isoch JO and inbound AV for one embodiment is shown in Figure 2. In some embodiments the sequence shown in Figure 2 may he implemented in software. finnware and/or hardware. lii software and firmware embodiments it may he implemented by computer executed instructions stored in one or more non-transitory computer readable media such as magnetic, optical, or semiconductor storages.

Separate sequences maybe used for each of the source 50, branch 52,54 and sink 56 devices in some embodiments.

[0029] An application on the source 50 conveys 58 the desired service parameters for the upcoming JO to the Isoch JO Manager on the source. This list of parameters includes the sink 56 from which the 10 data or AV stream is requested. Alternatively, the appUcation on (he sink conveys the desired parameters for the upcoming 10 to the Isoch 10 Manager on the sink. This list of parameters includes the source targeted for the JO data or AV stream. The Isoch JO Manager on the sink transmits these parameters to the Isoch 10 Manager on the source using REQUEST_IB_VC_ALLOCATJON Message Transaction.

10030] Isoch 10 Manager on (lie Source calculates (lie payload bandwidth number (PBN) required 60 for the desired operation using the service parameters it has received.

[0031] Isoch 10 Manager on the source issues lB_ALLOCATE_PAYLOAD Message Transaction 62 to establish the VC on Inbound main link. Source devices may have no more than one TB_ALLOCATE_PAYLOAD Message Transactions outstanding at any point in time in one embodiment. In the scenario where the sink is directly attached to the source, lB_ALLOCATE_PAYLOAD degenerates into DPCD writes to the lB Payload ID Table on the Sink. IB_ENUM_PATH_RESOURCES, lB_QUERY_PAYLOAD, LB_RESOURCE STATUS NOTIFY, and TB CLEAR PAYLOAD ID TABLE Message Transactions work on main link ffibound in a manner analogous to their counterparts on the main link.

[0032] Lsoch 10 Manager on the source transmits a CONFIGURE_b Message Transaction 64 to the target sink. Parameters for this CONFIGURE_JO may be as follows in one embodiment: i. Service_Type: as provided by the application ii. Tmnsfer_Type: Periodic iii. Frequency: as provided by the application iv. JO_Type: Isochronous v. Direction: Inbound vi. VC_Payload_ID: VC Payload ID returned by lB_ALLOCATE_PAYLOAD (66) vii. Sen'ice_Specfic_I-'arameters: as providcd by thc application [0033] The Isoch JO Manager on intermediate branch devices and the sink device process CONFIGURE_JO and prepare for the inbound 10 or AV operation.

[0034] The Isoch 10 Manager on the sink initiates transmission of 10 data at the desired frequency, or initiates the specificd AV stream. In case of JO data, the Isoch 10 Manager transnnts VC Payload Fill Symbol Sequence when there is no real data to be transmitted.

[0035] Upon eventual completion of the JO or AV operation, the Isoch JO Manager on the source transmits STOP_rn_TRANSFER Message Transaction to stop the transfer.

STOP_TB_TRANSFER does not cause the VC Payload ID to be released.

[0036] Isoch 10 Manager on the Source optionally releases the VC using lB_ALLOCATE_PAYLOAD Message Transaction 66. This causes all devices to release the specified VC Payload ID.

[0037] Bulk JO data transfers are non-periodic 10 transfers scheduled by the Bulk 10 Manager based on a parameter, which could be a 3-bit Quality of Service (QoS) field in one embodiment. A detailed sequence for inbound bulk 10 according to one embodiment is shown in Figure 3. In sonic embodiments the sequence shown in Figure 3 maybe implemented in software, firmware and/or hardware. In software and firmware embodiments it maybe implemented by computer executed instructions stored in one or more non-transitory computer readable media such as magnetic, optical, or semiconductor storages.

Separate sequences may he used for each of the source, branch and sink devices in some embodiments. The sequence includes the following steps: (1) The JO Policy Maker on the source 100 optionally directs the Bulk JO Manager to pre-aflocate 105 bandwidth on the path (a VC that is shared by all bulk 10 transfers) to each Bulk JO-capable sink 108, 112 at source device initialization time. This enables a certain minimum level of bandwidth that can subsequently he enhanced, reduced, or released. Such a pre-allocation reserves bandwidth for bulk 10, and VCs for subsequent isoch 10 transfers arc allocated around this bandwidth. Without a pre-allocation, dynamic allocation of the (shared) VC for bulk JO would happen around the VCs allocated till that point for isoch ifl For dynamic allocations of VC for bulk JO (ii any), the Bulk JO uses lB_ALLOCATE_PAYLOAD Message Transaction (108).

(2) An application on the source conveys 110 the desired parameters for the upcoming JO to the Bulk JO Manager on the source. This list of parameters includes the sink from which the IC) data is requested. It also includes the desired 3-bit quality of service (QoS) for this transaction. Alternatively, the application on the sink conveys 114, 116 the desired parameters for the upcoming JO to the Bulk JO Manager on the sink. This list of parameters includes the source to which the JO data is targeted, and the 3-bit QoS. In case a VC for bulk JO transaction has not been established yet. the Bulk JO Manager on the sink transmits the same desired parameters to the Bulk IC) Manager on the source using REQUEST_TB_VC_ALLOCATION Message Transaction.

(3) If needed, the Bulk 10 Manager on the source calculates the PBN required for the desired operation using the parameters it has received. Tt then allocates a VC for hulk JO using rn_ALLOCATE_PAYLOAD Message Transaction 112, as described in Step (I) above.

(4) The Bulk JO Manager on the source transmits a CONFIGURE_JO Message Transaction 114, 116 to the target sink * Parameters for this CONFIGURE_IC) may he as follows in one embodiment: i. Service_Type: as provided by the application ii. Transfer_Type: One-Shot iii. J-'riorit: 3-bit QoS provided by the application iv. 10_Type: Bulk v. Direction: hibound or Outbound, as desired by the application vi. VC_Payload_ID: the VC to be used for this bulk JO transfer vii. Service_Specific_Parameters: as provided by the application * In case the VC allocation was in response to a prior REQUEST_IIB_VC_ALLOCATION. the source executes this step even in the case of a failure in VC allocation. The VC Payload ID communicated hack to the sink is INVALID_VC_PAYLOAD_ID, which causes thc sink and intermcdiatc branch devices to ignore rest of the parameters in this Message Transaction.

(5) The Bulk JO Manager on intermediate branch devices 102. 104 and the sink device 106 process CONFIGURE_ID 116 and prepare for the inbound to or AV operation 118.

(6) The Bulk JO Manager on the JO data-originator (source or sink) schedules 120 transfer of the 10 data as per the 3-bit QoS.

[0038] Sequences for outbound isoch and bulk JO are similar to the corresponding sequences for inbound JO. Key differences are as follows in one embodiment: * Isoch or Bulk JO Manager on the source allocates VC (as needed) for outbound 10 transfers on the main link using ALLOCATE_PAYLOAD Message Transaction.

* Isoch or Bulk 10 Manager on the source transmits CONFIGURE_JO Message Transaction after allocating YC. as done for inbound JO. Based on this the downstream devices monitor the YC for JO data from the source and propagate it downstream.

* In case of outbound bulk JO, the Bulk JO Manager on the source schedules data from the applications for transmission based on their 3-bit QoS fields. Bulk 10 Managers in the downstream devices process the received JO data in First Come First Served order.

* In case of outbound isochronous JO. the Isoch JO Manager on the source initiates 10 transfer as per frequency specified by the Application.

10039] IB_ENUM_PATH_RESOURCES is a path resource Message Transaction used to dctcrminc thc minimum availahlc PBN on thc inbound path of thc hi-dircctional Main Link.

Syntax for this Mcssagc Transaction's Request and Aek_Reply arc idcntical to thc syntax for its outbound equivalent WNUM_PATH_RESOURCES) already defined in the Display Port Spec vl.2a. A device in the path will fail this request if it is not already in hi-directional mode when it receives this message.

[0040] lB_ALLOCATE_PAYLOAD is a path or nodc request Message Transaction that allows a change of the payload allocation for a virtual channel between DP source and sink device on inbound path of bidirectional link, lB_ALLOCATE_PAYLOAD request is used to allocatc payload for a ncw virtual channel, changc thc payload allocation of an existing virtual channel, or deletion of the payload allocation of an existing virtual channel. Syntax for this Message Transaction's Request and Ack_Reply are identical to the syntax for ALLOCATE_PAYLOAD, which is already dcfincd in DP Standard vl.2a. A dcvicc in thc path will fail this request if it is not already in hi-directional mode when it receives this message. Dcviccs maintain an lB VC Payload ID Tablc to track lB VC allocations on thc inbound path of bidirectional link.

[0041] lB_QUERY_PAYLOAD Message Transaction determines the available PEN for the Virtual Channel on the specified by the LB VC Payload ID parameter. Syntax for this Message Transaction's Request and Ack_Reply are identical to the syntax for QUERY_PAYLOAD, which is already defined in DP Standard v 1.2a. A device in the path will fail this request if it is not already in Bidirectional mode when it receives this message.

[0042] rn_RESOURCE_STATUS_NOTIFY is a node broadcast Message Transaction.

whose functionality and syntax for Request and Ack_Reply parallel those for RESOURCE_STATUS_NOTIFY, which is already defined in DP Standard vl.2a. A difference is that this Message Transaction is used for bandwidth events on the bi-directional mode Inbound path.

OO43j After receiving this message, the DP Source can use lB_QUERY_PAYLOAD request to detciminc which streams are still allocated and which were dc-allocated in response to the bandwidth events.

[0044] The rn_CLEAR_PAYLOAD_ID_TABLE path broadcast Message Transaction is sent by an MST DP device in bidirectional mode to dc-allocate all TB VC Payload IDs allocated to the port the message is received from. As in the case of CLEAR_PAYLOAD_ID_TABLE, this message is only sent to those downstream ports with lB VC Payloads allocated from the input port being cleared. Syntax for this Message Transaction's Request and Ack_Reply are identica' to those for CLEAR_PAYLOAD_ID_TABLE, as already defined in DP Standard vl.2a.

[0045] CONFIGURE_JO path Message Transaction is sent by a DP Source to the Sink Device to configure devices along the path with parameters that will be used in the upcoming transfer. A device in the path will fail this request if it is not already in bi-directional mode when it receives this message.

OO46j A source initiates STOP_lB_TRANSFER Path Message Transaction to stop an isochronous. periodic, inbound 10 or AV transfer it had initiated in the past. The specific inbound transfer to be stopped is identified by the VC Payload ID that is included as a parameter in this Message Transaction. The Message Transaction is propagated all the way to (he destination node, with intermediate devices updating their state tables helore propagating the ACK_Reply hack to the Source. A device in the path will fail this request if it is not already in hi-directional mode with the VC Payload ID already being in use for an inbound, isochronous. aM penodic 10 transfer.

OO47j The syntax for STOP_lB_TRANSFER_Request is exactly the same as for CONFIGURE_JO_Request, which is already defined in DP Standard vi.2a. The difference is that the parameters are being proposed by the sink for the upcoming transfer. Importantly. the YC_Payload_ID parameter is set to zero by (lie sink and is not to he interpreted by the Source.

[0048] A sink initiates REQUEST_IIB_VC_ALLOCATION node Message Transaction to request the source to allocate a VC br a sink-initiated inbound transfer. The transfer could he for isochronous 10, bulk 10, or for inbound AV. The sink communicates all the parameters for this proposed transfer to the source. The source determines the PBN required based on these parameters and initiates allocation of appropriate IB_VC (as needed) aM notifies all devices along the path (including the Sink) about the VC and parameters to bc used br the upcoming inbound transfer. The Sink should already be in hi-directional mode when it initiates a REQUEST_IB_VC_ALLOCATION.

[0049] 10 devices and their capabilities may be discovered when they are plugged into downstream DP devices using LINK_ADDRESS: Input_Port When set to a one the port information is for a uPacket RX. Otherwise port information is for uPacket TX.

10_Port When set to a one, the port is for an JO device. Else, it is for an AV device.

lB_Audio_Capable When set to a one, the port is capable of inbound Audio.

lB_Video_Capable When set to a one, the port is capable of inbound Video.

Nuniher_SDP_Stream_Sinks The Number_SDP_Stream_Sinks reports the number of SDP stream sinks associated with the DP Port. This number is valid if the DisplayPort_Devicc_Plug_Status is sct to one.

IB_Isoch_JO_Capable When set to a one, the device on this port is capable of inbound Isoch 10. This number is valid if the DisplayPort_Device_Plug_Status is set to one.

OB_Isoch_JO_Capable When set to a one, the device on this port is capable of outbound Isoch TO. This number is valid if the DisplayPort_Deviee_Plug_Status is set to one.

ffi_B ulk_I0 When set to a one, the device on this port is capable of inbound Bulk IC).

This number is valid if the DisplayPort_Deviee_Plug_Status is set to one.

OB_Isoch_lO_Capable When set to a one, the device is on this port is capable of outbound Bulk 10. this number is valid ii the DisplayPort_Device_Plug_Status is set to one.

Native_JO_Services_Capability This is a hit-held indicating Native 10 Service capability oh the device at this port. Encoding of this bit-field follows the definition of DPCD register 62001h. This number is valid if the DisplayPort_Device_Plug_Status is set to one.

Bridged_lO_Services_Capahility When set to a one, the port is capable of outbound Bulk JO. Encoding of this bit-field follows the definition of DPCD register 62002h. This number is vaJid if the DisplayPort_Device_Plug_Status is set to one.

[0050] RefelTing to Figure 4. a sequence for implcmenting 10 aM inbound AV in a source dcvice in accordancc with somc embodiments may be implemented in software, firmware and/or hardware. h software and firmware embodiments it may be implemented by computer executed instructions stored in one or more non-transitory computer readable media such as a magnetic, optical or semiconductor storage.

1] The sequence 150 begins by enahling the sink to stream AV content of the sources indicated in block 152. Then the sink is enabled to receive AV information from the source as indicated in block 154. Next the sink is enabled to transport AV JO information to the source as indicated in block 156.

[0052] Figure 5 illustrates an embodiment of a system 700. In embodiments, system 700 may be a media system although system 700 is not limited to this context. For example, system 700 may be incorporated into a personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad, portable computer, handheld computer, palmtop computer, personal digital assistant (PDA), cellular telephone, comhination cellifiar telephonc/PDA, television, smart device (e.g., smart phone, smart tablet or smart television), mobile internet. device (MID), messaging device, data communication device.

and so forth.

0053] In embodiments, system 700 comprises a platform 702 coupled to a display 720.

Platform 702 may receive content from a content device such as content services device(s) 730 or content delivery device(s) 740 or other similar content sources. A navigation controller 750 comprising one or more navigation features may he used to interact with, for example, platform 702 and/or display 720. Each of these components is described in more detail below.

10054] In embodimenk, platlorm 702 may comprise any combination of a cliipset 705, processor 7W, memory 712, storage 714, graphics subsystem 715, applications 716 and/or radio 718. Chipset 705 may provide intercommunication among processor 710, memory 712, storage 714, graphics subsystem 715, applications 716 and/or radio 718. For example, chipset 705 may include a storage adapter (not depicted) capable of providing intercommunication with storage 714.

[0055] Processor 710 may be implemented as Complex hmtruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors, xSô instruction set compatible processors, multi-core, or any other microprocessor or centra' processing unit (CPU). In embodiments, processor 710 may comprise dual-core processor(s), dual-corn mobile S processor(s), and so forth. The processor may implement the sequence of Figure 8 together with memory 712.

[0056] Memory 712 may he implemented as a volatile memory device such as, hut not limitcd to, a Random Access Memory (RAM), Dynamic Random Access Memory (DRAM), or Static RAM (SRAM).

[0057] Storage 714 may he implemented as a non-volatile storage device such as, hut not limited to. a magnetic disk drive, optical disk drive, tape drive, an internal storage device, an attached storage device, flash memory, battery backed-up SDRAM (synchronous DRAM), and/or a network accessible storage device. In embodiments, storage 714 may comprise technology to increase the storage performance enhanced protection for valuable digital media when multiple hard drives are included, for example.

[0058] Graphics subsystem 715 may perform processing of images such as still or video for display. Graphics subsystem 715 may be a graphics processing unit (GPU) or a visual processing unit (VPU), for example. An analog or digital interface may be used to communicatively couple graphics subsystem 715 and display 720. For example, the interface may be any of a High-Definition Multimedia Interface, DisplayPor, wireless HDMI. andlor wireless HD compliant techniques. Graphics subsystem 715 could be integrated into processor 710 or chipset 705. Graphics subsystem 715 could he a stand-alone card communicatively coupled to chipset 705.

[0059] The graphics and/or video processing techniques described herein may be implemented in various hardware architectures. For example. graphics and/or video functionality may he integrated within a chipset. Alternatively, a discrete graphics and/or video processor may he used. As still another embodiment, the graphics andlor video functions may be implemented by a general purpose processor, including a multi-core processor. In a further embodiment, the functions may he implemented in a consumer electronics device.

[0060] Radio 718 may include one or more radios capable of transmitting and receiving signals using various suitable wireless communications techniques.Such techniques may involve communications across one or more wireless networks. Exemplary wireless networks include (hut arc not limited to) wireless local area networks (WLANs), wireless personal area networks (WPANs), wireless metropolitan area network (WMANs), cellular networks, and satellite networks. In communicating across such networks, radio 718 may operate in accordance with one or more applicable standards in any version.

[0061] hi embodiments, display 720 may comprise any telcvision type monitor or display.

Display 720 may comprise, for example, a computer display screen, touch screen display, video monitor, television-like device, and/or atdevision. Display 720 may he digital and/or analog. In einbodinients, display 720 may be a holographic display. Also, display 720 may be a transparent surface that may receive a visual projection. Such projections may convey various forms of information, images. and/or objects. For example, such projections may he a visual overlay for a mobile augmented reality (MAR) application.

Under the control of one or more software applications 716, platform 702 may display user interface 722 on display 720.

[0062] hi embodiments, content services device(s) 730 may be hosted by any national, international and/or independent service and thus accessible to platform 702 via the Internet. for example. Content services device(s) 730 may he coupled to plaiform 702 and/or to display 720. Platform 702 and/or content services device(s) 730 may be coupled to a network 760 to communicate (e.g., send and/or receive) media information to and from network 760. Content delivery device(s) 740 also may he coupled to platform 702 and/or to display 720.

[0063] hi embodiments, content services device(s) 730 may comprise a cable television box, personal computer, network, telephone. Internet enabled devices or appliance capable of delivering digital information and/or content, and any other similar device capable of unidirectionally or bidirectionally communicating content between content providers and platform 702 and/display 720, via network 760 or directly. It will be appreciated that the content may he communicated unidirectionally and/or hidirectionally to and from any one of the components in system 700 and a content provider via network 760. Examples of content may include any media information including, for example, video, music, medical and gaming information, and so forth.

[0064] Content services device(s) 730 receives content such as cable television programming including media information, digital information, and/or other content.

Examples of content providers may include any cable or satellite television or radio or Internet content providers. The provided examples are not meant to limit the applicable embodiments.

[0065] hi embodiments, platform 702 may reccivc control signals from navigation controller 750 having one or more navigation features. Thc navigation features of controller 750 may be used to interact with user interface 722, for example. In embodiments, navigation controller 750 may be a pointing device that may be a computer hardware component (specifically human interface device) that allows a user to input spatial (e.g., continuous and multi-dimensional) data into a computer. Many systems such as graphical user interlaces (GUI), and televisions and monitors a'low the user to control and provide data to the computer or television using physical gestures.

[0066] Movements of the navigation features of controller 750 may be echoed on a display (e.g., display 720) by movements of a pointer, cursor, focus ring, or other visual indicators displayed on the display. For example, under the control of software applications 716, the navigation features located on navigation controller 750 may he mapped to virtual navigation features displayed on user interface 722, for example. hi embodiments.

controller 750 may not he a separate component hut integrated into platform 702 and/or display 720. Embodiments, however, are not limited to the elements or in the context shown or described herein.

[0067] lii embodiments, drivers (not shown) may comprise technology to enable users to instantly turn on and off platform 702 like a television with the touch of a button after initial hoot-up. when enabled, for example. Program logic may allow platform 702 to stream content to media adaptors or other content services device(s) 730 or content delivery device(s) 740 when the platform is turned "off." In addition, chip set 705 may comprise hardware and/or software support for 5.1 surround sound audio and/or high definition 7.1 surround sound audio, for example. Drivers may include a graphics driver for integrated graphics platforms. In embodiments, the graphics driver may comprise a peripheral component interconnect (PCI) Express graphics card.

[0068] In various embodiments, any one or more of the components shown in system 700 may be integrated. For example. platform 702 and content services device(s) 730 may be S integrated, or platform 702 and content delivery device(s) 740 may be integrated, or platform 702, content services device(s) 730, and content delivery device(s) 740 may he integrated, for example. lii various embodiments, platform 702 and display 720 may be an integrated unit. Display 720 and content service device(s) 730 may he integrated, or display 720 and content delivery device(s) 740 may be integrated, for example. These examples arc not meant to he scope limiting.

[0069] In various embodiments, system 700 may be implemcntcd as a wireless system, a wired system, or a combination of both. When implemented as a wireless system. system 700 may include components and interfaces suitable for communicating over a wireless shared media, such as one or more antennas, transmitters, receivers, transceivers, amplifiers.

filters, control logic, and so forth. An example of wireless shared media may include portions of a wireless spectrum, such as the RF spectrum and so forth. When implemented as a wired system. system 700 may include components and interfaces suitable for communicating over wired communications media, such as input/output (110) adapters.

physical connectors to connect the 1/0 adapter with a corresponding wired communications medium, a network interface card (NIC), disc controller, video controller, audio controller, and so forth. Examples of wired communications media may include a wire, cable, metal leads, printed circuit hoard (PCB), backplane, switch fabric, semiconductor material, twisted-pair wire, co-axial cable, fiber optics, and so forth.

[0070] Platform 702 may establish one or more logical or physical channels to communicate information. The information may include media information and control information. Media information may refer to any data representing content meant for a user. Examp'es of content may include, for example, data from a voice conversation, videoconfercncc, streaming video, electronic mail ("email") message. voice mail message.

alphanumeric symbols, graphics, image, video, text and so forth. Data from a voice conversation may be, for example, speech information, silence periods, background noise, comfort noise, tones and so forth. Control information may refer to any data representing commands, instructions or control words meant for an automated system. For example, control inlormation may he used to route media inlormation through a system, or instruct a node to process the media information in a predetermined manner. The embodiments, however, are not limited to the elements or in the context shown or described in Figure 5.

[0071] As described above, system 700 may be embodied in varying physical styles or lorm lactors. Figure 6 illustrates embodiments ol a small form lactor device 800 in which system 700 may be embodied. In embodiments, for example, device 800 may be implemented as a mobile computing device having wireless capabilities. A mobile computing device may refer to any device having a processing system and a mobile power source or supply, such as one or more batteries. br example.

[0072] As described above, examples of a mobile computing device may include a personal computer (PC), laptop computer, ultra-laptop computer, tablet, touch pad. portable computer, handheld computer. palmtop computer, personal digital assistant (PDA), cellular telephone, combination cellular telephone/PDA, television, smart device (e.g.. smart phone, smart tablet or smart television), mobile internet device (MID), messaging device, data communication device, and so forth.

[0073] Examples of a mobile computing device also may include computers that are arranged to he worn by a person, such as a wrist computer, finger computer, ring computer, eyeg'ass computer, belt-clip computer. arm-band computer, shoe computers. clothing computers, and other wearable computers. In embodiments, for example, a mobile computing device may he implemented as a smart phone capable of executing computer applications, as well as voice communications and/or data communications. Although some embodiments may he described with a mobile computing device implemented as a smart phone by way of example. it may be appreciated that other embodiments may be implemented using other wireless mobile computing devices as well. The embodiments are not limited in this context.

[0074] The following clauses and/or examples pertain to further embodiments: One example embodiment may be a method comprising enabling a sink device to stream audio/visual content to a source device over a display interface, and enahhng the sink device to receive audio/visual and/or input/output information from a source device and to transmit audio and/or video and/or input/output information to a source device over the display interface. The method may also include wherein the input/output information includes raw touch screen sensor data. The method may also include providing a main link and an independent receive link. The method may also include implementing a DisplayPort topology that includes audio/visual and input/output devices. The method may also include supporting both isochronous and hulk input/output transfers and inbound audio and/or video.

The method may also include enabling multiple concurrent input/output operations. The method may also include enabling prioritization of bulk I/O from applications on a device originating a request. The method may also include enabling entities to priontize among concurrent isoch 1/0 applications on an originating dcvice. Thc method may also include enabling discovery of input/output devices and their capabilities when they are plugged into downstream devices and thereby applying an address generation mechanism for a DisplayPort interface for input/output devices. The method may also include enabling the source to read a block of data with first in first out semantics. The method may also include enabling the source to read DisplayPort configuration data registers for inbound and outbound input/output information. The method may also include a sink to request a source to initiate a switch to enable an input/output data transfer from sink to source. The method may also include enabling the source to configure all devices along the path for the input/out data transfer.

[0075] Another example embodiment. may be one or more non-transitory computer readable media storing instructions executed by a processor to perform a sequence comprising enabling a sink device to stream audio/visual content to a source device, and enabling the sink device to receive audio/visual input/output information froni a source device and to transmit audio/video input/output information to a source device. The media wherein the input/output information includes raw touch screen sensor data. The media may include said sequence including providing a main link and an independent receive link. The media may include said sequence including implementing a DisplayPort topology. The media may include said sequence including supporting both isochronous and bulk transfers and inbound audio and video. The media may include said sequence including enabling the source to read a block of data with first in first out semantics. The media may include said sequence including enabling the source to read DisplayPort configuration data registers for inbound and outbound input/output information. The media may include said sequence including a sink to request a source to initiate a switch to enable an input/output data transfer from sink to source. The media may include said sequence including enabling the source to configure all devices along the path for the input/out data transfer.

[0076] In another example embodiment may be a sink comprising a processor to stream audio/visual content to a source device, to receive audio/visual input/output inlormation from a source device and to transmit audio/video input/output information to a source device, and a memory coupled to said processor. The sink wherein the input/output information includes raw touch screen sensor data. The sink of said processor to provide a main link and an independent rcccivc link. Thc sink of said processor to implement a DisplayPort topology.

The sink of said processor to support both isochronous and hufic transfers and inbound audio and video. The sink of said processor to request a source to initiate a switch to enable an input/output data transfer from sink to source. The sink may include a display communicatively coupled to the processor. The sink may include a battery coupled to the 1 5 processor.

[0077] References throughout this specification to "one embodiment" or "an embodiment" mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one implementation encompassed within the present.

disclosure. Thus, appearances of the phrase "one embodiment" or "in an embodiment" are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be instituted in other suitable forms other than the particular embodiment illustrated and all such forms may be encompassed within the claims of the present application.

[0078] While a limited number of embodiments have been described, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and

scope of this disclosure.

Claims (28)

1. Claims 1. A method comprising: enahhng a sink device to stream audio/visual content to a source device over a display interface; and cnahhng the sink device to receive audio/visual and/or input/output information from a source device and to transmit audio and/or video andlor input/output information to a source device over the display interface.
2. 2. The method of claim I wherein the input/output information includes raw touch screen sensor data.
3. 3. The method of claim 1 including providing a main link and an independent receive I ink.
4. 4. The method of claim I including implementing a DisplayPort topology that indudes audio/visual and input/output devices.
5. 5. The method of claim I including supporting both isochronous and hulk input/output transfers and inbound audio and/or video.
6. 6. The method of claim 5 including enabling multiple concurrent input/output operations.
7. 7. The method of claim 5 including enabling prioritization of bulk 110 from applications on a device originating a request.
8. 8. The method of claim 5 including enabling entities to prioritize among concurrent isoch 110 applications on an originating device.
9. 9. The method of claim 5 including enabling discovery of input/output devices and their capabilities when they are plugged into downstream devices and thereby applying an address generation mechanism for a DisplayPort interface for input/output devices.
10. 10. The method of claim 1 including enabling the source to read a block of data with first in first out semantics.
11. 11. The method of claim 1 including enabling the source to read DisplayPort configuration data registers for inbound and outbound input/output information.
12. 12. The method of claim I including a sink to request a source to initiate a switch to enable an input/output data transfer from sink to source.
13. 13. One or more non-transitory computer readable media storing instructions executed by a processor to perform a sequence comprising: cnabhng a sink device to stream audio/visual content to a source device; and enabling the sink device to receive audio/visual input/output information from a source device and to transmit audio/video input/output information to a source device.
14. 14. The media of claim 13 wherein the input/output information includes raw touch screen sensor data.
15. 15. The media of claim 13 said sequence including providing a main link and an independent receive link.
16. 16. The media of claim 13 said sequence including implementing a DisplayPort topology.
17. 17. The media of claim 13 said sequence including supporting both isochronous and bulk transfers and inbound audio and video.
18. 18. The media of claim 13 said sequence including enabling the source to read a Hock of data with first in first out semantics.
19. 19. The media of claim 13 said sequence including enabling the source to read DisplayPort configuration data registers for inbound and outbound input/output information.
20. 20. A sink comprising: a processor to stream audio/visual content to a sourcc device, to receive audio/visua' input/output information from a source device and to transmit audio/video input/output information to a source device; and a memory coupled to said processor.
21. 21. The sink of claim 20 wherein the input/output information includes raw touch screen sensor data.
22. 22. The sink of claim 20 said processor to provide a main link and an independent receive link.
23. 23. The sink of claim 20 said processor to implement a DisplayPort topology.
24. 24. The sink of claim 20 said processor to support both isochronous and hulk transfers and inbound audio and video.
25. 25. The sink of claim 20 said processor to request a source to initiate a switch to enable an input/output data transfer from sink to source.
26. 26. A method as hereinbefore described with reference to and as illustrated in any one of Figures 2 to 4 of the accompanying drawings.
27. 27. One or more non-transitory computer readable media storing instructions executed by a processor to perform a sequence as hereinbefore described with reference to and as illustrated in any one of Figures 2 to 4 of the accompanying drawings.
28. 28. A sink as hereinbefore described with reference to and as illustrated in any one of Figures 1, 5 and 6 of the accompanying drawings.