BACKGROUND

[0001] Mobile computing devices have been developed to increase the functionality that is made available to users in a mobile setting. 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. One challenge that faces developers of mobile computing devices is efficient power management and extension of battery life. For instance, the small form factor of many mobile computing devices may compel designs in which power connections are kept relatively small in size. Accordingly, developers may be further concerned with ensuring that adapters designed for use with such small form power connections are safe and supply the proper amount of power to the device. One concern is arcing that may occur when an external power adapter device is connected to a mobile computing device.

SUMMARY

[0002] Anti-arcing circuits are described herein that are configured to prevent or substantially mitigate arcing when a power adapter is connected/disconnected from a client device. In one or more implementation, the anti-arcing circuit is provided to restrict power supplied via the power adapter from a power source to the client device when a connection of the connector to the adapter interface is not fully established. The anti-arcing circuit is further configured to detect when the connection is made and remove the restriction to supply an appropriate power level for operations of the client device. In one approach, the anti-arcing circuit includes two different paths and components associated with a detection mode and operational mode, respectively. In the detection mode, power supply is suppressed and a current pulse may be sent to determine if a connection is established. If current is detected, a switch is made to operational mode and power for normal device operations is supplied. In this way, the device does not receive power sufficient to sustain arcing until the connection of the connector is fully established and therefore arcing may be mitigated.

[0003] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.

[0005] Fig. 1 is an illustration of an environment in accordance with one or more implementations .

[0006] Fig. 2 is an illustration of an example client device in accordance with one or more implementations .

[0007] Fig. 3 is a diagram depicting details of an example power adapter in accordance with one or more implementations.

[0008] Fig. 4 is a flow diagram depicting an example procedure in which a power adapter switches between modes.

[0009] Fig. 5 is diagram depicting an example anti-arcing circuit.

[0010] Fig. 6 is diagram depicting another example anti-arcing circuit.

[0011] Fig. 7 is a flow diagram depicting an example procedure for operation of an anti- arcing circuit.

[0012] Fig. 8 depicts an example computing system and devices in accordance with one or more embodiments.

DETAILED DESCRIPTION

Overview

[0013] Anti-arcing circuits are described herein that are configured to prevent or substantially mitigate arcing when a power adapter is connected/disconnected from a client device. In the absence of the anti-arcing circuit, arcing may occur across a connector and the adapter interface as the connection is being established (or during disconnection). This may reduce the life span of connector pins/contacts, may present a hazard in some settings, and/or may make user uncomfortable if they see the arcing. In one or more implementation, the anti-arcing circuit is provided to restrict power supplied via the power adapter from the power source to the client device when a connection of the connector to the adapter interface is not fully established. The anti-arcing circuit is further configured to detect when the connection is made and remove the restriction to supply an appropriate power level for operations of the client device. In one approach, the anti-arcing circuit includes two different paths and components associated with a detection mode and an operational mode, respectively. In the detection mode, power supply is suppressed and a current pulse may be sent to determine if a connection is established. If current is detected, a switch is made to the operational mode and power for normal device operations is supplied. In this way, the device does not receive power sufficient to sustain arcing until the connection of the connector is fully established and therefore arcing may be mitigated.

[0014] In the following discussion, an example operating environment is first described that may employ the techniques described herein. Next, example details and techniques are described which may be implemented in the example environment as well as other environments. Consequently, performance of the techniques is not limited to the example environment and the example environment is not limited to performance of the example techniques. Lastly, example systems and devices are described that may be employed to implement one or more embodiments.

Example Operating Environment

[0015] Fig. 1 is an illustration of an environment 100 in an example implementation that is operable to employ techniques described herein. The illustrated environment 100 includes a client device 102 that is communicatively coupled via a network 104 to a service provider 106. The service provider 106 may be configured to make various resources 108 (e.g. content and services) available over the network 104 to the client device 102 and other clients. Generally, resources 108 made accessible by a service provider 106 may include any suitable combination of services and/or content typically made available over a network by one or more providers. Some examples of services include, but are not limited to, a search service, an email service, an instant messaging service, an online productivity suite, and an authentication service to control access of clients to the resources. Content may include various combinations of text, multi-media streams, documents, application files, photos, audio/video files animations, images, web pages, web applications, device applications, content for display by a browser or other client application, and the like.

[0016] The client device 102 and service provider 106 may be implemented by one or more computing devices and also may be representative of one or more entities. A computing device may be configured in a variety of ways. For example, a computing device may be configured as a computer that is capable of communicating over the network, such as a desktop computer, a mobile station, an entertainment appliance, a set-top box communicatively coupled to a display device, a wireless phone, a game console, and so forth. Thus, the computing device may range from full resource devices with substantial memory and processor resources (e.g., personal computers, game consoles) to a low- resource device with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles). Additionally, although a single computing device is shown in some instances, the computing device may be representative of a plurality of different devices, such as multiple servers utilized by the service provider 106.

[0017] The client device 102 is further illustrated as including an operating system 110. The operating system 110 is configured to abstract underlying functionality of underlying hardware to applications 112 that are executable on the client device 102. For example, the operating system 110 may abstract processing, memory, network, and/or display functionality such that the applications 112 may be written without knowing "how" this underlying functionality is implemented. The applications 112, for instance, may provide data to the operating system 110 to be rendered and displayed by a display device without understanding how this rendering will be performed. Additionally, the computing device 102 may be physically and communicatively coupled to an accessory device 114 via an interface 116. Details regarding various example accessory devices and interfaces are discussed below in relation to Fig. 2.

[0018] In accordance with techniques described herein, the client device 102 is also illustrated as being connectable to a power adapter 118 (also referred to herein as a power supply unit (PSU)) that includes or makes use of an anti-arcing circuit 120 as described herein to prevent arcing. In particular, the anti-arcing circuit 120 may be implemented in various ways to mitigate arcing that may otherwise occur when the client device 102 is connected to a power supply via the power adapter 118. The power adapter 118 is representative of an external power supply unit that is connectable to the client device 102 a suitable power source such as an electrical wall receptacle, a battery, or other power source. In one approach, the anti-arcing circuit 120 is configured to implement a detection mode that initially restricts power to control arcing prior to connection to the client device. The anti-arcing circuit 120 may subsequently cause a switch to an operational mode for "normal" operations responsive to detection of a connection of the client device to the power adapter 118. Upon disconnection of the power adapter 1 18 from the client device 102, the anti-arcing circuit 120 may revert back to the detection mode with restricted power. Details regarding techniques to selectively switch between the modes to prevent arcing are discussed in relation to the following figures.

[0019] Fig. 2 depicts generally at 200 one illustrative example of an accessory device 114 that is connectable to a client device 102 via an interface 116. In the example, the client device 102 is depicted as a tablet or slate device. The example accessory device 114 is configured as a keyboard having a QWERTY arrangement of keys although other arrangements of keys are also contemplated. Further, other non-conventional configurations for an accessory device 114 are also contemplated, such as a game controller, configuration to mimic a musical instrument, a power adapter, and so forth. Thus, the accessory device 114 may assume a variety of different configurations to support a variety of different functionality. Different accessory devices may be connected to the computing device at different times.

[0020] As previously described, the accessory device 114 is physically and communicatively coupled to the client device 102 via an interface 116, which in this example is configured as a flexible hinge. The flexible hinge represents one illustrative example of an interface 116 that is suitable to connect and/or attach an accessory device 114 to a client device 102. The flexible hinge is flexible in that rotational movement supported by the hinge is achieved through flexing (e.g., bending) of the material forming the hinge as opposed to mechanical rotation as supported by a pin, although that embodiment is also contemplated. Further, this flexible rotation may be configured to support movement in one direction (e.g., vertically in the figure) yet restrict movement in other directions, such as lateral movement of the accessory device in relation to the client device. This may be used to support consistent alignment of the accessory device in relation to the client device 102, such as to align sensors used to change power states, application states, and so on.

[0021] The flexible hinge may be formed using one or more layers of fabric and include conductors formed as flexible traces to communicatively couple the accessory device to the client device and vice versa. This communication, for instance, may be used to communicate a result of a key press to the client device, receive power from the client device, perform authentication, provide supplemental power to the computing device, and so on. The flexible hinge or other suitable interface 116 may be configured in a variety of ways to support multiple different accessory devices 114. Generally, the interface 116 supports movement of the accessory device 114 in relation to the client device 102 into various orientations/configurations. For instance, example keyboard accessory may be rotated against the display device of the client device 102 and thereby act as a cover. An accessory may also be rotated so as to be disposed against a back of the client device 102, e.g., against a rear housing of the client device 102 that is disposed opposite the display device for a viewing orientations. In another instance, a typing arrangement may be supported in which the accessory is laid flat against a surface and the client device 102 is disposed at an angle to permit viewing of the display device 110, e.g., such as through use of a kickstand disposed on a rear surface of the computing device 102. Other instances are also contemplated, such as a tripod arrangement, meeting arrangement, presentation arrangement, and so forth.

[0022] Having considered the foregoing discussion of an example operating environment, consider now details regarding a verification platform described in relation to the following example illustrations and procedures.

Anti-Arcing Details

[0023] This section discusses details of example anti-arcing circuits and techniques in accordance with one or more implementations. In portions of the following discussion reference may be made to the example operating environment described in relation to Figs. l and 2.

[0024] In particular, Fig. 3 depicts generally at 300 an example power adapter 118 that is connectable to a client device 102 in greater detail. As shown, the power adapter 118 provides the client device 102 with a connection to a power source 302 (e.g., a power receptacle, external battery, etc.). To do so, the power adapter 118 may include a connector 304 that is configured to connect to a corresponding an adapter interface 306 of the client device 102 to facilitate communication and power exchanges between the adapter and device. The power adapter may also include components and/or another connector to enable the connection to the power source 302. Thus, the connection of the connector 304 and adapter interface 306 provides both a power coupling for supplying power from the adapter to the device and a communicative coupling to carry communications between the adapter and device.

[0025] The connector 304 and adapter interface 306 may be configured in various ways to establish a suitable connection between the device and adapter. By way of example and not limitation, the example connector 304 of Fig. 3 is depicted as having five pins that create a connection by contact with five corresponding pins of the adapter interface 306. In this arrangement, two pins of the connection may be used for positive voltage, another two pins may be used for voltage return, and the remaining pin of the connection may establish a single pin communication line/channel used to convey communications between the adapter and device. A variety of other arrangements are also contemplated.

[0026] In the depicted example, the power adapter 118 is further illustrated as including an anti-arcing circuit 120. The anti-arcing circuit 120 may be configured in various was described herein to prevent or substantially mitigate arcing when the power adapter 118 is connected/disconnected from the client device 102. In the absence of the anti-arcing circuit 120, arcing may occur across the connector 304 and the adapter interface 306 as the connection is being established (or during disconnection). This may reduce the life span of connector pins/contacts, may present a hazard in some settings, and/or may make users uncomfortable if they see the arcing. Accordingly, the anti-arcing circuit 120 is provided to restrict power supplied via the power adapter 118 from the power source 302 to the client device 102 when a connection of the connector 304 to the adapter interface is not fully established. The anti-arcing circuit 120 is further configured to detect when the connection is made and remove the restriction to supply an appropriate power level for operations of the client device 102.

[0027] As further illustrated, the client device 102 may include a power controller 308 that represents functionality of the client device to perform various operations for power management. This may include management of different power sources and switching between the sources, implementing a defined and/or selected power management scheme, managing battery life, and so forth. The power controller 308 may also facilitate connections and communications with a power adapter 118 configured to supply power to the device via a suitable power source 302, such as a wall socket, external battery, or other external source of power. The power controller 308 may be implemented in hardware, software, firmware and/or combinations thereof. By way of example and not limitation, a microcontroller or other suitable hardware logic device may be configured to implement various functionally that is described herein in relation to power controller 308. The power controller 308 may operate using relatively low power, independently of operating a "primary" processing system (for example, one or more central processing units of the device) of the host computing device, and/or without booting/executing an operating system or using other device components and applications. In other words, the power controller 308 may operate to perform some power management tasks without having to operate or supply power to the processing system and other device components (e.g., device memory, network interface, display device, etc.) and/or without completely starting-up or waking-up the computing device.

[0028] In an implementation, an anti-arcing circuit 310 as represented in Fig. 3 may be included with the client device 102 in addition to or in lieu of providing the anti-arcing circuit 120 as a component of the power adapter 118. As shown, the anti-arcing circuit 310 may be implemented as a component of the adapter interface 306. Alternatively the anti- arcing circuit 310 may be implemented as a component of the power controller, as a standalone device, or otherwise be integrated with the client device 102. In this approach, the anti-arcing circuit 310 may operate to restrict/suppress power across the connection of the adapter interface 306 and connector 304 in the absence of detecting a complete connection. The anti-arcing circuit 310 may then detect when the connection is made and enable an appropriate power level for operations of the client device. To do so, the anti- arcing circuit 310 may communicate instructions, notifications, or other suitable directives to the power adapter 118 to cause the power adapter to switch between providing restricted power and normal power levels in appropriate circumstances. Notably, the anti-arcing circuit 310 may operate without having or relying upon dedicated pins of the connector 304 that are used strictly for sensing connections and/or arcing mitigation. Instead, the connector 304 may be used without modification and is arranged with pins used for other, normal functions, such as the five pins in the example described above.

[0029] To further illustrate, consider now a discussion of some example procedures and anti-arcing circuits. Aspects of each of the procedures may be implemented in hardware, firmware, software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference may be made to the example operating environment 100 of Fig. 1 and the example devices of Figs. 2 and 3, respectively.

[0030] Fig. 4 depicts an example procedure 400 to selectively switch between different modes to prevent arcing. A power supply unit is initiated in a detection mode that restricts power supplied to a client device (block 402). Then, monitoring is performed to detect a connection of the power supply unit to an interface of the client device (block 404). For example, an anti-arcing circuit 120 of a power adapter 118 may be set to operate in a detection mode by default. This may occur when the power adapter 118 is initially connected to a power source 302. In the detection mode, the anti-arcing circuit 120 is configured to supply restricted power output so that arcing does not occur when a connection of the adapter to a client device is being established. Further, the anti-arcing circuit 120 is configured to monitor to determine when a connection is established to a client device 102. In one approach, the anti-arcing circuit 120 may include detection components to implement the monitoring. This may include a monitoring integrated circuit, a microcontroller device, and/or other hardware suitable to check the connection between the connector 304 and adapter interface 306 and recognize when the connector 304 is connected and disconnected to a corresponding client device 102. By way of example and not limitation, the anti-arcing circuit 120 may be configured to recognize changes in electrical current indicative of whether or not the power adapter is connected. Other techniques to recognize when a connector is connected or disconnected are also contemplated, including but not limited to processing notifications or other feedback sent by a power controller of 308 of the computing device, detecting actuation of a physical switch or button that is toggled into different states as the connector is connected/disconnected, using one or more sensors configured to provide information indicative of connection/disconnection such as a light sensor or IR sensor, and so forth.

[0031] Responsive to detection of the connection to the interface, the power supply unit is operated in an operational mode to supply power to the client device (406). In the operational mode, monitoring is performed to detect a disconnection of the power supply unit to the interface of the client device (block 408). Upon disconnection of the power supply unit, the power supply unit is switched back to the detection mode (block 410).

[0032] Here, the anti-arcing circuit 120 may operate to cause a switch from limited/restricted power to an appropriate power supply for normal operations of the device. The power supply in the operational mode is set to a designated level for the device and is relatively higher than power in the detection mode. Since the power level associated with the operational mode is not available until a connection is detected, arcing while the connection is being established can be avoided. While in the operational mode, the detection components of the anti-arcing circuit 120 may perform monitoring to determine when the power adapter 118 is disconnected. When the disconnection is recognized, the anti-arcing circuit 120 may cause a switch back to the detection mode and restricted power supply. In this way, the power adapter 118 is prepared for mitigation of arcing in relation to a subsequent connection to a client device.

[0033] An anti-arcing circuit 120 may be configured is various ways to implement the monitoring and selective switching in response to connection and disconnection of a power supply unit to a device. In general, the anti-arcing circuit 120 includes at least a detection component to monitor connection status to a device, switching components operable to change between restricted and operational power levels, and a control mechanism to cause operation of the switching components in response to changes in the connection status determined via the detection component. One example arrangement of a suitable anti-arcing circuit 120 is described in relation to an example circuit of Figs. 5 and 6 and a corresponding flow diagram of Fig. 7.

[0034] In particular, Fig. 5 depicts an example implementation of an anti-arcing circuit 120 circuit, generally at 500. The example arrangement depicted in Fig. 5A includes a supply source 502, two current detectors, CD1 504 and CD2 506, two metal-oxide- semiconductor field-effect transistors (MOSFETs) Ql 508 and Q2 510, a monitor integrated circuit 512, and a connector 514. These components form different respective current paths with the connector that are associated with the detection mode and the operational mode. The supply source 502 may represent a connection to a power source to power a client device, such as an AC to DC converter, a DC to DC converter, an external battery pack, and so forth. The monitor integrated circuit 512 represents functionality and/or logic implemented in a hardware form for monitoring the connection of the connector 514 and switching between the detection mode and operational mode described herein. The connector 514 represents a connector configured to connect the anti-arcing circuit and/or power supply unit/power adapter to the device, such as the example connector 304 described in relation to Fig. 3. As those of skill in the art will appreciate, the MOSFETs are a type of transistor used in digital and analog circuits for various functionality, such as switching and amplifying. In the context of an anti-arcing circuit, the MOSFETs may provide switching functionality to selectively restrict current or supply current in appropriate scenarios. Other types of transistors, switches, and components may be employed in addition to or in lieu of the MOSFETs to accomplish comparable switching functionality.

[0035] The current detectors CD1 504 and CD2 506 are each connected in series between the supply source positive output and a drain of a corresponding MOSFET. The outputs of the current detectors are connected to the respective inputs (labeled CD1 and CD2) associated with the monitor integrated circuit 512. The source of each MOSFET is connected to the positive terminal of the connector 514. The gates of the MOSFETs are connected to respective outputs (labeled Gl and G2) of the monitor integrated circuit 512. A first current path between the source and connector for a detection mode is established by CD1 504 and Ql 508. A second current path for the operational mode is established by CD2 506 and Q2 510. Both paths include the monitor integrated circuit 512. The first current path may be associated with suppressed power and the second current path may be associated with unrestricted power for normal device operations. A switch between the paths may be effectuated by selectively turning on and off the MOSFETS (Ql, Q2) in the paths. Thus, the first current path is selected when Ql is on and disabled when Ql is off. Likewise, the second current path is selected when Q2 is turned on and disabled when Q2 is off.

[0036] In an implementation, the current detectors include respective comparators and resistors. In particular, Fig. 5 depicts CD1 504 as including a comparator 516 and a resistor Rl 518. Likewise, CD2 506 is depicted as including a comparator 520 and a resistor R2 522. As shown in Fig. 5, a negative input terminal of each comparator 516, 520 is connected to a respective one of the resistors 518, 522. A junction of this connection is connected to the supply source positive output. The positive input terminal of each comparator is connected to the other end of the respective resistor. Further, the junction of this connection is connected to the drain of a corresponding MOSFET. The output sides of the comparators 516, 520 are connected to corresponding inputs (labeled CDl and CD2) of the monitor integrated circuit 512. In this arrangement, when current flows through either Rl 518 or R2 522, the output of the respective comparator will go high because of a voltage drop across the resistor in the particular path.

[0037] Fig. 6 depicts details of another example anti-arcing circuit 310 that may be integrated with a client device as previously mentioned. The anti-arcing circuit operates in a comparable manner as the example circuit of Fig. 5 but is implemented on the device side rather than as part of the power adapter 118. The example arrangement depicted in Fig. 6 again includes two current detectors, CDl 504 and CD2 506, two metal-oxide- semiconductor field-effect transistors (MOSFETs) Ql 508 and Q2 510, and a monitor integrated circuit 512. In this case however, the anti-arcing circuit 310 is shown as being arranged between a battery 602 of a client device 102 and a connector interface 604 that enables connection to a power adapter 118, e.g., on the device side. Again, these components form different respective current paths with the connector interface that are associated with the detection mode and the operational mode. Details regarding operation of the example circuits are now discussed in relation to Fig. 7.

[0038] Fig. 7 depicts an example procedure 700 that represent operations and/or logic that may be implemented by anti-arcing circuit in accordance with one or more embodiments. The procedure may be performed at least partially in hardware such as by a monitor integrated circuit 512 of the example circuit in Fig. 5, a microcontroller, a power controller device of a client, and so forth. The procedure may also be performed by other hardware elements, logic devices, firmware, or combinations thereof. Fig. 7 also represents a logical division of operations between a detection mode and an operational mode as described herein. This division is represented by way of a dashed vertical line between the various blocks.

[0039] When the power adapter is plugged in and/or turned on, a corresponding anti- arcing circuit may be initialized in a detection mode as discussed previously. The anti-arcing circuit may be incorporated with a power adapter 118. In some implementations, though an anti-arcing circuit may be provided as a component of the computing device such as being integrated with a power controller 308 or an adapter interface 306 as discussed in relation to Fig. 3. Thus, although procedure 700 is discussed in relation to the example circuit of Fig. 5, comparable logic and techniques may be applied to other circuits arrangements and/or to anti-arcing circuits incorporated with a power adapter, client device as in Fig. 6, or otherwise.

[0040] Initially, the anti-arcing circuit may be initialized in the detection mode (block 702). In relation to the example circuit of Fig. 5 for example, the monitor integrated circuit may be set to start in detection mode when plugged in and/or before a connection to a device is established. For this initialization stage, both MOSFETs (Ql and Q2) are turned off. In other words, the outputs of the monitor integrated circuit are set to zero (e.g., Gl = 0, G2 =0).

[0041] A delay is then applied (block 704). The delay may be configured as a relatively brief delay such as few seconds or a fraction of a second. This delay period provides time between checks and an interval in which a connection of the power adapter may occur. The delay may be set to control the frequency of monitoring for connection/disconnection. In the depicted example a delay of one second is shown although other delay periods are also contemplated.

[0042] After the appropriate delay, a monitor pulse is sent to enable current detection (block 706). In the detection mode, the supply to the device is flowing through CDl 504 and the corresponding resistor Rl 518. Here, sending the monitor pulse involves turning on the MOFSET Ql 508 (e.g., Gl = 1, G2 =0) so that current may be detected in the loop through CDl 504 and Rl 518. The pulse may be a relatively narrow pulse on the order of a few milliseconds.

[0043] After the monitor pulse is sent, a check for current through the circuit is made (block 708). In relation to the example circuit of Fig. 5, this involves checking the output of the comparator 516. In other words, a determination is made regarding whether the output of the comparator 516 is high (CDl =1) or low (CD1=0). As mentioned if current is flowing across Rl 518, CDl is driven high. On the other hand, if the connector is not connected, then CDl is low. Thus, the monitor integrated circuit is configured to check the output of the comparator 516 and take appropriate action in response.

[0044] In particular, if the output is low (CD 1=0) this indicates that a connection has not been established. Accordingly, the circuit stays in detection mode and the procedure returns to block 702. While still in the detection mode, restricted power is supplied to suppress arcing and blocks 702 to 708 may then be repeated one or more times to monitor and detect connections to a device in the described manner. [0045] On the other hand, if the output is high (CD1 =1) this indicates that a connection has been established and current is flowing across Rl 518. In response, the monitor integrated circuit 512 may cause as switch to the operational mode. In general, this involves switching the current path between the MOFSETs, such as by shutting off Ql 508 and turning on Q2 510. By so doing, the circuit may switch to supplying power to the device through CD2 506 and the corresponding resistor R2 522. The power supply in operational mode is relatively higher than in detection mode due to lower resistance selected for Rl 522 in comparison with Rl 518 as discussed in greater detail below. Thus, the power supplied in operational mode is sufficient to support normal operation of the device. The anti-arcing circuit may then be reset to monitor for disconnection and switch back from the operational mode to the detection mode if appropriate. The monitoring that occurs in the operational mode is similar to the monitoring just described, but is applied to the components associated with a current path through CD2 506.

[0046] In particular, while in the operational mode the anti-arcing circuit is reset (block 710). The reset enables switching to operational power supply for the device and/or sets up the circuit for detection of a disconnection. As shown in Fig. 7, this may involve turning both MOSFETs Ql 508 and Q2 510 off (e.g., G1=0, G2=0). Then a delay is again applied (block 712) and another monitor pulse is sent (block 714), this time through the current path and components associated with CD2 506. After the monitor "high signal" is sent, a check for current through the circuit is made (block 716). In the operational mode, the check for current is made with respect to CD2 506. In particular, a determination may be made regarding whether the output of the comparator 520 is low or high. If the output is high, this indicates that current is flowing through R2 522 and the connector 514 is connected to the device. If the output is low, there is no current flow across R2 522. This is indicative of a disconnection and may cause the anti-arcing circuit to initiate a change back to detection mode.

[0047] As long as the output of the comparator 520 is high (e.g., CD2 =1), the circuit remains in operational mode. As shown in Fig. 7, the procedure 700 may return to block 714 and send repeated monitoring continuous high signals. Here, operational power continues to be supplied until a disconnection is detected at block 716 (e.g., CD2 = 0). In response to the disconnection, operational power is cutoff and the procedure 700 returns to block 702. Both MOFSETs are again turned off to initiate the circuit in detection mode. Now, the anti-arcing system is once again set-up to suppress power supply and perform operations to detect subsequent connection of the connector 514 to a device. [0048] A noted above, Rl 518 may be configured with relatively high resistance on the order of ten-thousand kilohms or more. In detection mode, a relatively small current (e.g., less than a couple of milliamp) flows through Rl 518 when Ql 508 is turned on and the power adapter is connected to a device. Thus, current may be detected using a monitor pulse (e.g., a one millisecond pulse) as discussed above. When current flows there is a voltage drop across Rl and CD1 is pulled high. In response, Ql 508 is shutoff and after a designated delay (e.g., 1 second) Q2 510 is turned on Q2 to enable supply of operational power. R2 522 is configured with relatively low resistance on the order a few milliohms. The relatively low resistance is selected to enable delivery of high current to the device without significant loss of power due to the resistance of R2 522. As long as current flows across R2, Q2 is remains on to deliver operational power in the operational mode. In response to detecting lack of current flow across R2, the circuit turns Q2 off and switches back to detection mode, which suppresses the power supply to the device.

[0049] Accordingly, when an attempt to connect a connector 514 to a device is made, the anti-arcing circuit is in detection mode and suppresses power. Monitor pulses may be employed to make sure the connector 514 is actually connected before operational power is sent to the device. The brief monitor pulses of one millisecond or so are not sufficient to sustain arcing. Further, operational power is not supplied until the connection is established and is cutoff upon disconnection. In this manner, arcing may be substantially mitigated and/or eliminated completely.

[0050] Having considered the foregoing example details and procedures, consider now a discussion of an example system and device to implement various aspects in accordance with one or more embodiments.

Example System and Device

[0051] Fig. 8 illustrates an example system 800 that includes an example computing device 802 that is representative of one or more computing systems and/or devices that may implement the various techniques described herein. The computing device 802 may be, for example, a server of a service provider, a device associated with a client (e.g., a client device), an on-chip system, and/or any other suitable computing device or computing system.

[0052] The example computing device 802 as illustrated includes a processing system 804, one or more computer-readable media 806, and one or more I/O interfaces 808 that are communicatively coupled, one to another. Although not shown, the computing device 802 may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.

[0053] The processing system 804 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 804 is illustrated as including hardware elements 810 that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 810 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.

[0054] The computer-readable media 806 is illustrated as including memory/storage 812. The memory/storage 812 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage 812 may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage 812 may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media 806 may be configured in a variety of other ways as further described below.

[0055] Input/output interface(s) 808 are representative of functionality to allow a user to enter commands and information to computing device 802, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone for voice operations, a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non- visible wavelengths such as infrared frequencies to detect movement that does not involve touch as gestures), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile- response device, and so forth. Thus, the computing device 802 may be configured in a variety of ways as further described below to support user interaction. [0056] Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms "module", "functionality", and "component" as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

[0057] An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 802. By way of example, and not limitation, computer-readable media may include "computer-readable storage media" and "communication media".

[0058] "Computer-readable storage media" refers to media and/or devices that enable storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media does not include signal bearing media or signals per se. The computer-readable storage media includes hardware such as volatile and nonvolatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.

[0059] "Communication media" refers to signal-bearing media configured to transmit instructions to the hardware of the computing device 802, such as via a network. Communication media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Communication media also include any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

[0060] As previously described, hardware elements 810 and computer-readable media 806 are representative of instructions, modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein. Hardware elements may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware devices. In this context, a hardware element may operate as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element as well as a hardware device utilized to store instructions for execution, e.g., the computer-readable media described previously.

[0061] Combinations of the foregoing may also be employed to implement various techniques and modules described herein. Accordingly, software, hardware, or program modules including operating system 110, applications 112, and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements 810. The computing device 802 may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of modules as a module that is executable by the computing device 802 as software may be achieved at least partially in hardware, e.g., through use of computer- readable media and/or hardware elements 810 of the processing system. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 802 and/or processing systems 804) to implement techniques, modules, and examples described herein.

[0062] As further illustrated in Fig. 8, the example system 800 enables ubiquitous environments for a seamless user experience when running applications on a personal computer (PC), a television device, and/or a mobile device. Services and applications run substantially similar in all three environments for a common user experience when transitioning from one device to the next while utilizing an application, playing a video game, watching a video, and so on.

[0063] In the example system 800, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one embodiment, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.

[0064] In one embodiment, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one embodiment, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.

[0065] In various implementations, the computing device 802 may assume a variety of different configurations, such as for computer 814, mobile 816, and television 818 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 802 may be configured according to one or more of the different device classes. For instance, the computing device 802 may be implemented as the computer 814 class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.

[0066] The computing device 802 may also be implemented as the mobile 816 class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device 802 may also be implemented as the television 818 class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on.

[0067] The techniques described herein may be supported by these various configurations of the computing device 802 and are not limited to the specific examples of the techniques described herein. The functionality of various modules may also be implemented all or in part through use of a distributed system, such as over a "cloud" 820 via a platform 822 as described below.

[0068] The cloud 820 includes and/or is representative of a platform 822 for resources 824. The platform 822 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 820. The resources 824 may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device 802. Resources 824 can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi network.

[0069] The platform 822 may abstract resources and functions to connect the computing device 802 with other computing devices. The platform 822 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources 824 that are implemented via the platform 822. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system 800. For example, the functionality may be implemented in part on the computing device 802 as well as via the platform 822 that abstracts the functionality of the cloud 820.

Conclusion

[0070] Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed invention.