4 is a flow diagram depicting a procedure in an example implementation in which notifications are provided to an operating system to support device enumeration for busses that do not natively support enumeration.įIG. 3 is an example implementation of an architecture showing a transport mechanism to support a communicative coupling in greater detail.įIG. 2 is an illustration of an example implementation showing an architecture employable by a computing device and accessory device of FIG. 1 is an illustration of an environment in an example implementation that is operable to employ the techniques described herein.įIG. ![]() Entities represented in the figures may be indicative of one or more entities and thus reference may be made interchangeably to single or plural forms of the entities in the discussion.įIG. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The detailed description is described with reference to the accompanying figures. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This enables the operating system to enumerate and/or denumerate hardware devices within a device configuration and power management system implemented by the operating system that facilitates interaction with the hardware devices through corresponding representations. In response to such detection, the intermediate controller may send appropriate notifications to an operating system to alert the operating system when hardware devices come and go. The intermediate controller may detect connection and disconnection of hardware devices in association with one or more communication busses employed by the computing device. In one or more embodiments, an intermediate controller of a computing device is configured to interconnect and manage various hardware devices associated with the computing device. ![]() SUMMARYĭevice enumeration support techniques are described for busses that do not natively support enumeration. However, at least some alternative busses may not natively support device enumeration (e.g., plug-and-play or hot swapping capabilities), which may complicate addition/removal of hardware and detract from a user's experience with the device. Accordingly, alternative busses may be selected by a hardware developer for device designs to improve power consumption characteristics of the computing device. Some traditional communication busses (e.g., universal serial bus (USB)) used to interconnect connect hardware devices associated with a computing device may consume significant amounts of power, which may hinder the mobility of the device. For example, a user may interact with a mobile phone, tablet computer, or other mobile computing device to check email, surf the web, compose texts, interact with applications, and so on. Mobile computing devices have been developed to increase the functionality that is made available to users in a mobile setting. 19, 2012, and titled “Accessory Device Architecture.” BACKGROUND 13/471,186, filed May 14, 2012, and titled “Input Device Layers and Nesting ” and U.S. ![]() 13/470,633, filed May 14, 2012, and titled “Flexible Hinge and Removable Attachment ” U.S. 61/646,799, filed May 14, 2012, the disclosure of which is hereby incorporated by reference in its entirety, this application also incorporates the following applications by reference in their entirety: U.S. This application claims priority under 35 U.S.C.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |