CN115576877A - Charging method, terminal device and storage medium - Google Patents

Abstract

The embodiment of the present application discloses a charging method, a terminal device, and a storage medium. The method includes: when establishing a connection with an external device, determining the connection type of the connection line with the external device; if the connection line type is debugging line, and the device type of the external device is an adapter, then the pins of the USB interface are set to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; start the first timer at the same time; After the running time, disable the PMIC's control of the pins of the USB interface; activate the adapter to establish fast charge communication.

Description

Charging method, terminal device and storage medium

technical field

The present invention relates to the technical field of charging, in particular to a charging method, terminal equipment and a storage medium.

Background technique

Based on the method of fast charging by the Microcontroller Unit (MCU), an external fast charging control chip is arranged on the printed circuit board (PCB), referred to as the fast charging MCU, which is used to control the fast charging. logic implementation. On Qualcomm's 8350 platform, the charging control module is transplanted into the analog digital signal processing chip (AnalogDigital Signal Processor, ADSP) subsystem. In order to save costs, the MCU chip needs to be removed. To achieve the VOOCPHY physical layer of PM8350B.

However, although the fast charging method based on the combination of ADSP and VOOPPHY can save costs, due to the change of the hardware solution, there is a problem that the DEBUG line interferes with the fast charging communication, making the DEBUG line unable to support the fast charging function, which reduces the charging performance and charging efficiency.

Contents of the invention

The embodiment of the present application provides a charging method, a terminal device and a storage medium, which can ensure the successful establishment of a voice service and improve the reliability of the voice service.

The technical scheme of the embodiment of the application is realized in this way:

In a first aspect, an embodiment of the present application provides a charging method, the method comprising:

When establishing a connection with an external device, determine the connection line type of the connection line with the external device;

If the connection line type is a debugging line, and the device type of the external device is an adapter, then the pins of the USB interface are set to a high-impedance state, to prohibit USBPHY from controlling the pins of the USB interface; simultaneously start first timer;

After exceeding the running time of the first timer, prohibiting the PMIC from controlling the pins of the USB interface;

Activate the adapter to establish fast charge communication.

In the second aspect, the embodiment of the present application provides a terminal device, the terminal device includes: a determining unit, a setting unit, a prohibiting unit, an activating unit,

The determination unit is configured to determine the connection line type of the connection line with the external device when establishing a connection with the external device;

The setting unit is configured to set the pins of the USB interface to a high-impedance state if the connection line type is a debugging line, and the device type of the external device is an adapter, so as to prohibit the USBPHY from controlling the USB interface. Pin control; start the first timer at the same time;

The prohibition unit is configured to prohibit the PMIC from controlling the pins of the USB interface after exceeding the running time of the first timer;

The activation unit is configured to activate the adapter to establish fast charging communication.

In a third aspect, an embodiment of the present application provides a terminal device, the terminal device includes a processor and a memory storing instructions executable by the processor, and when the instructions are executed by the processor, the following is implemented: In one aspect, the charging method.

In a fourth aspect, the embodiment of the present application provides a computer-readable storage medium, on which a program is stored, and when the program is executed by a processor, the charging method as described in the first aspect is implemented.

The embodiment of the present application provides a charging method, a terminal device, and a storage medium. When establishing a connection with an external device, determine the type of the connection line connected to the external device; if the type of the connection line is a debugging line, and the external device If the device type is an adapter, set the pins of the USB interface to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; start the first timer at the same time; after exceeding the running time of the first timer, prohibit PMIC controls the pins of the USB interface; activates the adapter to establish fast charging communication. It can be seen that, in the embodiment of the present application, the terminal can determine the device type and connection line type corresponding to the external device, so that it can further determine whether to prohibit USBPHY and PMIC from connecting D+ and D- according to the device type and connection line type. control. Specifically, after determining that the external device is an adapter, the external device is connected to the terminal through a DEBUG line, and does not perform wireless charging, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, thereby It can avoid the DEBUG line from interfering with the fast charging communication, and can meet the demand of supporting the use of the DEBUG line for fast charging, greatly improving the charging performance and charging efficiency.

Description of drawings

Figure 1 is a schematic diagram of the fast charging communication process in the embodiment of the present application;

Figure 2 is a schematic diagram of the principle of fast charging in the MCU mode;

Figure 3 is a schematic diagram of the principle of fast charging realized by combining ADSP and VOOPPHY;

FIG. 4 is a schematic diagram of the implementation flow of the charging method proposed in the embodiment of the present application;

Figure 5 is a schematic diagram of the pin interface of TYPE-C;

Fig. 6 is the schematic diagram of resistance connection situation;

FIG. 7 is a second schematic diagram of the implementation flow of the charging method proposed in the embodiment of the present application;

FIG. 8 is a schematic diagram of the third implementation flow of the charging method proposed in the embodiment of the present application;

FIG. 9 is a schematic diagram 4 of the implementation flow of the charging method proposed in the embodiment of the present application;

FIG. 10 is a schematic diagram of the fifth implementation flow of the charging method proposed in the embodiment of the present application;

FIG. 11 is a schematic diagram of the implementation flow of the charging method proposed in the embodiment of the present application VI;

FIG. 12 is a first schematic diagram of the composition and structure of the terminal device proposed in the embodiment of the present application;

FIG. 13 is a second schematic diagram of the composition and structure of the terminal device proposed in the embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the specific embodiments described here are only used to explain the related application, not to limit the application. It should also be noted that, for the convenience of description, only the parts related to the relevant application are shown in the drawings.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application, and are not intended to limit the present application.

In the following description, references to "some embodiments" describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or a different subset of all possible embodiments, and Can be combined with each other without conflict. It should also be pointed out that the term "first\second\third" involved in the embodiment of the present application is only used to distinguish similar objects, and does not represent a specific ordering of objects. Understandably, "first\second\ The specific order or sequence of "third" can be interchanged where allowed, so that the embodiments of the application described herein can be implemented in an order other than that illustrated or described herein.

Currently, common fast charging technologies mainly include 5V/6A VOOC3.0 flash charging technology, 65W SUPERVOOC2.0 fast charging technology, and 125W fast charging technology based on Programmable Power Supply (PPS).

When the terminal is performing fast charging, it needs to use a customized adapter and battery to realize the flash charging function. Generally, the adapter used for flash charging is equipped with a Microcontroller Unit (MCU) smart chip, so the adapter is A smart charger that can be upgraded.

Further, in the embodiment of the present application, FIG. 1 is a schematic diagram of the fast charging communication flow in the embodiment of the present application, as shown in FIG. 1 . The process of fast charging the terminal by the adapter can mainly include the following five stages:

Phase 1: The terminal detects the adapter type, the adapter starts the handshake communication between the adapter and the terminal, the adapter sends a command to ask the terminal whether to enable the fast charging mode, and when the terminal agrees to enable fast charging, the fast charging communication process enters phase 2.

Wherein, the terminal can detect the adapter type through D+ and D-, and when it is detected that the adapter is a charging device that does not pass through the Universal Serial Bus (USB) type, the current absorbed by the terminal can be greater than a preset current value I2 . When the adapter detects that the adapter output current is greater than or equal to I2 within the preset time period, the adapter considers that the terminal has completed the identification of the adapter type, the adapter starts the handshake communication between the adapter and the terminal, and the adapter sends an instruction to ask the terminal whether to enable the fast charging mode. When the adapter receives a reply command from the terminal indicating that the terminal does not agree to enable the fast charging mode, it detects the output current of the adapter again, and when the output current of the adapter is still greater than or equal to I2, it initiates a request again to ask the terminal whether to enable the fast charging mode. Repeat the above steps in phase 1 until the terminal replies and agrees to turn on the fast charging mode, or the output current of the adapter no longer satisfies the condition of being greater than or equal to I2.

Stage 2: The adapter sends another instruction to the terminal, asking whether the output voltage of the adapter matches, and the terminal replies that the output voltage of the adapter is high, low or matched, and the adapter adjusts the output voltage until the output voltage is suitable.

Wherein, the voltage output by the adapter can include multiple gears, and the adapter can send an instruction to the terminal to ask the terminal whether the output voltage of the adapter is suitable as the charging voltage in the fast charging mode. When the feedback is low, the adapter adjusts its output voltage by one gear, and sends an instruction to the terminal again, asking whether the output voltage of the terminal adapter matches.

Stage 3: The adapter sends another instruction to the terminal, asking the terminal for the maximum charging current currently supported by the terminal, and the terminal replies with the maximum charging current of the adapter, and enters stage 4.

Stage 4: The adapter can set the output current to the maximum charging current currently supported by the terminal, and enter the constant current stage, that is, stage 5.

Stage 5: When entering the constant current stage, the adapter can send another command at intervals to inquire about the current voltage of the terminal battery, and the terminal can feed back the current voltage of the terminal battery to the adapter, and the adapter can use the current voltage of the terminal battery according to the current voltage of the terminal battery. Feedback to judge whether the contact is good and whether it is necessary to reduce the current charging current value of the terminal.

It should be noted that the constant current stage does not mean that the output current of the adapter remains constant in stage 5. The so-called constant current refers to segmental constant current, that is, it remains constant for a period of time.

The fast charging solution based on MCU has a two-stage switch, and its hardware cuts off the access of USBPHY to control D+ and D-. Therefore, when it is connected to the DEBUG line, it can be fast charged without special processing. Among them, Figure 2 It is a schematic diagram of the principle of fast charging in the MCU mode, as shown in Figure 2, the central processing unit (Central Processing Unit, CPU) directly controls the platform power management IC (Power Management IC, PMIC) to charge: the CPU directly through the system power management interface ( SystemPower Management Interface, SPMI) bus to operate platform PMIC registers to control general charging, analog digital signal processing chip (Analog Digital Signal Processor, ADSP) only audio module, through the application processor (Application Processor, AP) and ADSP communication link The GLINK bus exchanges data with the CPU.

When implementing fast charging through MCU, when the adapter is not connected, that is, when VBUS=0, switch 1 controls SW1, which is connected to SW2 by default. When the software is initialized, switch 2 controls SW2 to the serial port controller. When the terminal is directly connected to the serial port line, the serial port log can be output from D+ and D- by default; when the adapter is connected to power, the quick switch 1 control SW1 will be switched to the platform PMIC, and the charger type is BC1.2 after the ASPD recognizes it. (Battery Charging v1.2) dedicated charging port (Dedicated Charging Port, DCP), set switch 1 on the software to control SW1 to switch to SW2, and set switch 2 to control SW2 to switch to MCU, so that MCU<--- ->SW2<---->SW1<---->The adapter directly communicates through D+ and D-. Since the fast charging switch 1 controls SW1 to switch to SW2, neither PMIC nor USBPHY can interfere with the fast charging communication. At the same time, switch 2 controls SW2 to switch to the MCU. Therefore, the serial port output will not interfere with the fast charging communication.

Based on the MCU-style fast charging solution, an external fast charging control chip is arranged on the PCB, referred to as the fast charging MCU, which is used to control the logic implementation of fast charging. On Qualcomm's 8350 platform, the charging control module is transplanted into the ADSP subsystem. In order to save costs, the MCU chip needs to be removed, and the hardware sending and receiving logic of fast charging communication data is realized by the VOOPPHY physical layer integrated into PM8350B.

Figure 3 is a schematic diagram of the principle of fast charging realized by combining ADSP and VOOPPHY. As shown in Figure 3, the ADSP subsystem directly controls the charging module. Specifically, the ADSP subsystem controls the charging logic related to PM8350B. PM8350, VOOPPHY, and USBPHY are all integrated On the ADSP, the ADSP exchanges charging status information and USB related status information through the GLINK bus. Compared with the MCU-style fast charging solution, the hardware switch of the fast charging solution combined with ADSP and VOOPPHY only has switch 1, that is, when the VBUS is out of power, it will switch to the serial port module, and when the VBUS is powered, it will switch to the common one of PM8350, VOOCPHY, and USBPHY. port. Such a logical architecture leads to the fact that PMIC and USBPHY can control D+ and D- data communication even during fast charging. If the DEBUG line is connected, because the hardware is not disconnected, the DEBUG line interferes with fast charging communication, and the adapter passes through D+ , The information sent by D- will interfere with the half-high level, causing the data received by VOOCPHY to be incorrect and unable to perform fast charging.

It can be seen that although the fast charging method combined with ADSP and VOOCPHY can reduce the setting of hardware switches and save costs, due to the change of the hardware solution, there is a problem that the DEBUG line interferes with the fast charging communication, so that the DEBUG line cannot support the fast charging function, which reduces the charging time. performance and charging efficiency.

In order to solve the above problems, in the embodiment of this application, the terminal can determine the device type and connection line type corresponding to the external device, so that it can further determine whether to prohibit USBPHY and PMIC from connecting D+ and D- control. Specifically, after determining that the external device is an adapter, the external device is connected to the terminal through a DEBUG line, and does not perform wireless charging, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, thereby It can avoid the DEBUG line from interfering with the fast charging communication, and can meet the demand of supporting the use of the DEBUG line for fast charging, greatly improving the charging performance and charging efficiency.

That is to say, due to the significant changes in the fast charging hardware solution, for the DEBUG line, the terminal can be adapted on the software so that it can support the fast charging function when the DEBUG line is recognized, and then it can be based on the physics of receiving and sending VOOC fast charging information. The logic module VOOPPHY realizes the fast charging solution.

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

An embodiment of the present application provides a charging method. FIG. 4 is a schematic diagram of the implementation flow of the charging method proposed in the embodiment of the present application. As shown in FIG. 4, in the embodiment of the present application, the method for charging the terminal may include The following steps:

Step 101. When establishing a connection with an external device, determine a connection line type of a connection line with the external device.

In the embodiment of the present application, when the terminal establishes a connection with the external device, it may first determine the connection line type of the connection line with the external device. Wherein, the connection line type of the connection line may be a debugging line (DEBUG line) or a TYPE-C line.

It should be noted that, in the embodiments of this application, the terminal can be any terminal device with communication and storage functions, such as: tablet computer, mobile phone, e-reader, remote control, personal computer (Personal Computer, PC), notebook Terminal equipment such as computers, vehicle-mounted equipment, Internet TV, wearable equipment, personal digital assistants (Personal Digital Assistant, PDA), portable media players (Portable Media Player, PMP), navigation devices, etc.

It should be noted that, in the embodiment of the present application, the terminal may be configured with an analog and digital signal processing chip ADSP and an application processor AP, wherein the communication link between the ADSP and the AP is GLINK.

It can be understood that, in the embodiment of the present application, the terminal can support the normal charging mode and the fast charging mode, wherein the charging current of the fast charging mode is greater than the charging current of the normal charging mode, that is, the charging speed of the fast charging mode is greater than the above-mentioned The charging speed of normal charging mode.

Optionally, in this embodiment of the application, the external device may be a device for charging the terminal. Specifically, the external device may wirelessly charge the terminal by establishing a wireless connection with the terminal, or may establish a wireless connection with the terminal. Physical connection for wired charging to the terminal. For example, the external device may be an adapter, a power supply, or the like, and the external device may also be a charging base or the like.

Optionally, in the embodiment of the present application, the external device may also be a device for communicating with the terminal.

Further, in the embodiment of the present application, the terminal and the external device may be connected through a Universal Serial Bus (Universal Serial Bus, USB) interface, and the USB interface may be a common USB interface, or may be a microUSB interface or a USB interface, etc. . The power cord in the USB interface is used for external devices to charge the terminal, where the power cord in the USB interface may be a VBus line and/or a ground line in the USB interface. The data line in the USB interface is used for two-way communication between the external device and the terminal. The data line can be the D+ line and/or D- line in the USB interface. The so-called two-way communication can refer to the information exchange between the external device and the terminal.

It should be noted that, in the embodiment of this application, the USB interface has three interfaces with different appearances, namely Type-A, Type-B, and Type-C, and Type-C has a size smaller than Type-A and Type-B. It is the latest USB interface form factor standard. In addition, Type-C is an interface type that can be applied to both a PC (master device) and an external device (slave device, such as a mobile phone). Among them, the Type-C port has 4 pairs of sending (transport, TX)/receiving (receive, RX) branch lines, 2 pairs of USB D+/D-, a pair of SBUs, 2 CCs (CC1, CC2), and 4 VBUS and 4 ground wires.

Exemplarily, in this application, Figure 5 is a schematic diagram of the pin interface of TYPE-C, as shown in Figure 5, in the pin interface diagram of TYPE-C, its pins are symmetrical, so it supports positive and negative insertion . TYPE-C supports USB, DP and other protocols, and its symmetrical CC1 and CC2 pins are used to identify the connected device. The CC pin needs to have a pull-up/pull-down resistor inside the DPF (Downstream Facing Port, DPF) and UFP (Upstream Facing Port, UFP), respectively, to identify their respective functions. According to the detection of different pull-up and pull-down resistors, the load information can be confirmed. The internal CC of the DFP is pulled up to the power supply through different pull-up resistors Rp, and the internal CC of the UFP is pulled down to the ground wire (Ground, GND) through a 5.1K resistor. DFP directly refers to the downstream port, which can be considered as HOST equipment, power adapter, etc.; UFP can be considered as slave device DEVICE, U disk, powered equipment, etc.

Among them, the connection resistance of CC1 and CC2 in different TYPE-C lines or OTG (On-The-Go) lines is different. Figure 6 is a schematic diagram of the resistance connection situation. For example, assume that the mobile phone is used as a DFP and connected through an OTG line The situation of the U disk is shown in Figure 6.

When the terminal is connected to the adapter through a standard TYPE-C line, there is only one pull-up resistor on the standard TYPE-C line CC, and the other CC is open. From the perspective of the adapter as HOST, CC1 and CC2 are OPEN and RD respectively. state, the terminal is used as a SINK device, connected to a standard TYPE-C line, and the ADSP will only work when the charger type is recognized as a Standard Downstream Port (SDP)/Charging Downstream Port (CDP) by BC1.2. Notify the AP to pull up D+ to 3.3V to enumerate the device; when the terminal is connected to a non-standard TYPE-C line, there are pull-up resistors on both CCs, and from the adapter side of the HOST, both CC1 and CC2 are RD status, it will be recognized as DEBUG AccessoryMode attached, once it is recognized as a DEBUG line, ADSP will immediately notify the AP to pull up D+ to enumerate, that is, the AP will control the USBPHY to act on the high level of D+3.3V.

It can be understood that, in the embodiment of the present application, after the terminal establishes a connection with the external device through the connection line, it can first determine the specific connection line type of the connection line, so that it can be further determined based on the connection line type whether to perform Establishment of fast charging communication.

Optionally, in this application, when establishing a connection with an external device, the terminal may determine the connection line type of the connection line by triggering a Type-C interrupt. Wherein, the connection line type may be a debugging line (DEBUG line) or a TYPE-C line.

Exemplarily, in the embodiment of the present application, when an external device is plugged in, the terminal may first trigger a TYPE-C interrupt. Specifically, after the Type-C interrupt is triggered, in the interrupt processing function, it can be judged by reading the corresponding TYPE-C register whether the connection line corresponding to the inserted external device is a standard TYPE-C line or a DEBUG line, if it is a DEBUG line , the ADSP can send a notify message to the AP through the GLINK bus to inform the AP that the connection line corresponding to the external device inserted this time is the DEBUG line.

Step 102, if the connection line type is a debugging line, and the device type of the external device is an adapter, then set the pins of the USB interface to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; simultaneously start the first timer device.

In an embodiment of the present application, when the terminal establishes a connection with an external device, after determining the type of the connection line with the external device, if the type of the connection line corresponding to the external device is a debugging line, and if the external device If the device type is an adapter, the terminal can choose to set the pins of the USB interface to a high-impedance state, thereby prohibiting USBPHY from controlling the pins of the USB interface; at the same time, the terminal can also choose to start the first timer, so that It may be determined by the running time of the first timer that the PMIC is prohibited from controlling the pins of the USB interface.

It should be noted that, in the embodiment of this application, if the connection line type between the terminal and the external device is a debugging line, and the device type of the external device is an adapter, then, in order to prevent the ADSP from notifying the AP to pull the D+ to enumerate devices, that is, to prevent the AP side from controlling the USBPHY to act on the high level of D+3.3V, the terminal needs to set the pins of the USB interface to a high-impedance state, thereby prohibiting the USBPHY from controlling the pins of the USB interface. Control, and then solve the problem that the DEBUG line does not support fast charging in the case of ADSP+VOOCPHY.

It can be understood that, in the embodiment of the present application, the pins of the USB interface are D+ and D− of the USB interface. Correspondingly, when the connection line between the terminal and the adapter is identified as a DEBUG line, since the AP side will control the USBPHY to act on the high level of D+3.3V, the information sent by the adapter through D+ and D- will interfere with the process. Half-high level, so fast charging cannot be performed. Correspondingly, in order to prevent the DEBUG line from interfering with the fast charging communication, when the terminal determines that it is connected to the adapter through the DEBUG line, it can choose to directly ignore the USBPHY communication to prohibit the USBPHY from controlling D+ and D-.

It should be noted that, in the embodiment of the present application, the high-impedance state can be a state capable of performing wired AND with other states, wherein the wired-AND logic, that is, two output terminals (including more than two) are directly interconnected The logical function of "AND" can be realized. The above other states may represent other states that control D+ and D-, specifically may include the low-high state of 01 loaded on D+ and D- by VOOPPHY and the adapter.

Optionally, in this embodiment of the application, after determining that the external device is an adapter, and the connection line between the terminal and the external device is a DEBUG line, the AP in the terminal can act on the USBPHY of ADSP through GLINK, so that the D+ The state of D- and D- is set to a high-impedance state, so as to realize the prohibition of the control of D+ and D- by USBPHY.

Further, in the embodiment of the present application, FIG. 7 is a schematic diagram of the second implementation flow of the charging method proposed in the embodiment of the present application. As shown in FIG. 7, when establishing a connection with the external device, determine the After the connection line type of the connection line, that is, after step 101, and after the running time of the first timer is exceeded, before the PMIC is prohibited from controlling the pins of the USB interface, that is, before step 103, the terminal is charged The method may also include the following steps:

Step 105. If the connection line type is a debugging line, the device type is the adapter, and the charging mode is wired charging, then set the pins of the USB interface to a high-impedance state to prohibit USBPHY from Controlling the pins of the USB interface; starting the first timer at the same time.

In the embodiment of the present application, the terminal may also first determine the charging mode, and then further determine whether it is necessary to prohibit the USBPHY from controlling the pins of the USB interface in combination with the charging mode, the type of the connecting line, and the type of the device.

It can be understood that, in this application, the charging mode may include wireless charging and wired charging.

Correspondingly, in the embodiment of the present application, when the terminal determines that the connection line type of the connection line with the external device is a debugging line, the device type of the external device is an adapter, and the charging mode is wired charging, the terminal can choose to ignore the USBPHY. communication. Specifically, the terminal can set the pins of the USB interface to a high-impedance state, thereby prohibiting the control of D+ and D- by the USBPHY, thereby preventing the debugging line (DEBUG line) from interfering with the fast charging communication.

It can be understood that in this application, since wireless charging is coupled to VBUS through a wireless coil, an action similar to wired charging charger type identification will also occur. Therefore, the terminal can also eliminate wireless charging by confirming the charging mode. misidentification.

Step 103, after the running time of the first timer is exceeded, prohibit the PMIC from controlling the pins of the USB interface.

In the embodiment of the present application, if the type of connection line corresponding to the external device is a debugging line, and if the device type of the external device is an adapter, then after starting the first timer, the terminal may After runtime, the PMIC is disabled from controlling the pins of the USB interface.

It should be noted that, in the embodiment of the present application, the terminal may set the running time of the first timer in advance, for example, the running time of the first timer may be set to 800ms. Wherein, the running time of the first timer may be the transition time between wireless charging and wired charging, and correspondingly, the running time of the first timer may be used to determine the timing of starting VOOCPHY for fast charging communication.

Optionally, in the embodiment of the present application, since the OTG mode of the wireless reverse charging operation can be switched to the general charging mode when the wired fast charging is connected after the wireless reverse charging, that is, the conversion process from wireless charging to wired charging, PMIC needs a certain conversion time. Therefore, after the terminal determines that the external device is an adapter, and the connection line between the terminal and the external device is a debugging line, it will not immediately start VOOPPHY for fast charging communication, nor will it immediately disable PMIC. To control the pins of the USB interface, it is necessary to turn on and run the first timer. After ensuring that the conversion between wireless charging and wired charging has been completed, the PMIC is prohibited from booting the USB interface. foot control.

That is to say, in the embodiment of the present application, when the running time of the first timer is exceeded, it can be considered that the conversion process from wireless charging to wired charging has been completed. At this time, the terminal can choose to prohibit the PMIC from pin control.

Optionally, in the embodiment of the present application, the terminal can realize the requirement of prohibiting the PMIC from controlling D+ and D- by prohibiting the identification function of the high voltage dedicated charging port (HVDCP) and BC1.2.

Exemplarily, in this application, after the connection line between the terminal and the adapter is identified as a DEBUG line, the ADSP in the terminal can start a first timer with a running time of 800ms, and when the 800ms time of the first timer exceeds After the running time, in order to avoid the control of D+ and D- by the PMIC, the terminal can directly disable the identification of HVDCP and BC1.2, so that the PMIC cannot control D+ and D-.

Further, in the embodiment of the present application, the terminal may further determine whether it is necessary to prohibit the PMIC from controlling the pins of the USB interface in combination with the charging mode, the type of the connecting wire, and the type of the device.

Specifically, in this application, when the terminal determines that the connection line type of the connection line with the external device is a debugging line, the device type of the external device is an adapter, and the charging mode is wired charging (that is, wired charging), the terminal can select Disable the identification function of HVDCP and BC1.2, thus prohibiting the control of D+ and D- by PMIC.

It can be seen that in the embodiment of the present application, after the external device is determined to be an adapter, and the external device is connected to the terminal through a debugging cable, the terminal can either choose to prohibit the USBPHY from controlling D+ and D-, or choose to prohibit the PMIC from controlling D+ at the same time. , D-, at this time, only VOOCPHY can control D+, D-, so as to avoid the debugging line (DEBUG line) from interfering with the fast charging communication.

Step 104, activate the adapter to establish fast charging communication.

In the embodiment of the present application, after the terminal completes the process of prohibiting USBPHY and PMIC from controlling D+ and D-, it can activate the adapter, so as to establish fast charging communication with the adapter.

Optionally, in this embodiment of the application, the terminal can choose to activate the adapter by sending bursts through the enable level shift function, and after activating the adapter, establish normal fast charging communication with the adapter through the debugging line.

To sum up, through the charging method proposed in step 101 to step 104 above, after the terminal determines that the external device is an adapter, the external device is connected to the terminal through the DEBUG line, and it is not for wireless charging, it can set D+ and D- to For the high-impedance state, USBPHY is prohibited from controlling D+ and D-. It is also possible to prohibit the PMIC from controlling D+ and D- by disabling the identification functions of HVDCP and BC1.2, thereby ensuring the establishment of fast charging communication. That is to say, for the fast charging method combining ADSP and VOOPPHY, when the DEBUG line is recognized, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, so as to avoid DEBUG line interference Fast charging communication can meet the needs of supporting fast charging using the DEBUG line.

It can be seen that the charging method proposed in this application can realize the requirement that the DEBUG line can support fast charging based on the combination of ADSP and VOOPPHY. Compared with the MCU-based fast charging solution, while ensuring that the DEBUG line supports the fast charging function, a hardware switch is removed, which saves costs.

It should be noted that the charging method proposed in this application is also applicable to the subsequent MCU solution. The fast charging solution implemented by MCU can be used for reference in this application, which can also save costs by saving hardware switches.

An embodiment of the present application provides a charging method. When establishing a connection with an external device, determine the type of the connection line with the external device; if the type of the connection line is a debugging line, and the device type of the external device is an adapter, Then the pins of the USB interface are set to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; at the same time, the first timer is started; foot control; activate the adapter to establish fast charge communication. It can be seen that, in the embodiment of the present application, the terminal can determine the device type and connection line type corresponding to the external device, so that it can further determine whether to prohibit USBPHY and PMIC from connecting D+ and D- according to the device type and connection line type. control. Specifically, after determining that the external device is an adapter, the external device is connected to the terminal through a DEBUG line, and wireless charging is not performed, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, so that It can avoid the DEBUG line from interfering with the fast charging communication, and can meet the demand of supporting the use of the DEBUG line for fast charging, greatly improving the charging performance and charging efficiency.

Based on the above-mentioned embodiments, another embodiment of the present application proposes a charging method. FIG. 8 is a schematic diagram of the third implementation flow of the charging method proposed in the embodiment of the present application. As shown in FIG. 8, when establishing a connection with an external device, After determining the connection line type of the connection line with the external device, that is, after step 101, the method for charging the terminal may further include the following steps:

Step 106, determine the device type of the external device.

In the embodiment of the present application, when the terminal establishes a connection with the external device, after determining the connection line type of the connection line with the external device, the terminal can also determine the device type of the external device, that is, determine the type of the external device Is it an adapter.

It should be noted that, in the embodiment of the present application, before determining whether to establish fast charging communication, the terminal needs to first determine the device type of the external device. Wherein, the device type of the external device may be an adapter, or may be a non-adapter.

Specifically, in the embodiment of the present application, the method for the terminal to determine the device type of the external device may include the following steps:

Step 106a, after the Type-C interrupt is triggered, start a second timer.

In the embodiment of the present application, after determining the type of the connection line by triggering the Type-C interrupt, the terminal may first start the second timer.

It should be noted that, in the embodiment of the present application, the terminal may set the running time of the second timer in advance, for example, the running time of the second timer may be set to 200ms. Wherein, the running time of the second timer can be used to determine the triggering timing of the APSD interrupt.

Step 106b, after the running time of the second timer is exceeded, determine the port information corresponding to the external device by triggering an APSD interrupt.

In the embodiment of the present application, after the terminal starts the second timer, after the running time of the second timer exceeds, the terminal can further determine the port information corresponding to the external device by triggering an APSD interrupt.

It should be noted that, in the embodiment of the present application, after triggering the Type-C interrupt and reaching the running time of the second timer, the terminal can choose to trigger the APSD interrupt, wherein the APSD interrupt can be passed through BC1.2 (Battery Chargingv1.2 ) The charger type identification protocol acquires the port information corresponding to the external device.

Among them, BC1.2 is a protocol formulated by the BC (Battery Charging) group under the USB-IF, which is mainly used to standardize battery charging requirements. This protocol was first implemented based on the USB2.0 protocol.

Specifically, the three ports of BC1.2 mainly include the standard downlink port SDP, DCP, and charging downlink port CDP. Among them, the D+ and D- lines of the SDP port have 15kΩ pull-down resistors. The current limit values are as discussed above: 2.5mA when suspended, 100mA when connected, and 500mA when connected and configured for higher power. The port of DCP does not support any data transmission, but it can provide more than 1.5A of current. There is a short circuit between the D+ and D- lines of the port. This type of port supports higher-capacity wall chargers and car chargers without enumeration. This port of CDP not only supports high-current charging, but also supports data transmission that is fully compatible with USB2.0. The ports have 15kΩ pull-down resistors necessary for D+ and D- communication, and also internal circuitry for charger detection phase switching. Internal circuitry allows portable devices to distinguish the CDP from other types of ports.

Step 106c, determine the device type according to the port information.

In the embodiment of the present application, after the terminal exceeds the running time of the second timer, after determining the port information corresponding to the external device by triggering the APSD interrupt, it can further determine the device of the external device according to the port information Types of.

Exemplarily, in this application, if the port information corresponding to the external device is DCP, then the terminal can determine that the type of the device is an adapter.

Further, in the embodiment of the present application, FIG. 9 is a schematic diagram of the fourth implementation flow of the charging method proposed in the embodiment of the present application. As shown in FIG. 9, when establishing a connection with the external device, determine the After the connection line type of the connection line, that is, after step 101, the method for charging the terminal may also include the following steps:

Step 107. If the connection line type is Type-C line and the device type of the external device is an adapter, activate the adapter to establish fast charging communication.

In the embodiment of the present application, when the terminal establishes a connection with the external device, after determining the type of the connection line with the external device, if the type of the connection line corresponding to the external device is a standard Type-C line, At the same time, if the device type of the external device is an adapter, the terminal can choose to directly activate the adapter, so that fast charging communication can be established through the Type-C cable.

Optionally, in this embodiment of the application, after determining that the external device is an adapter, and the connection line between the terminal and the external device is a standard Type-C line, it can be determined that VOOPPHY controls D+ and D-, at this time, The terminal can use the enablelevel shift function to send pulse trains to activate the adapter, so that normal fast charging communication can be established with the adapter after the adapter is activated.

Further, in the embodiment of the present application, after establishing the connection with the external device, after determining the connection line type of the connection line with the external device, that is, after step 101, the method for charging the terminal may further include the following steps:

Step 108, when disconnecting from the external device, turn off the first timer and the second timer, and initialize the connection line identifier, the first control identifier, and the second control identifier.

In the embodiment of this application, after the terminal establishes a connection with the external device, when disconnecting from the external device, it can choose to close the first timer and the second timer. At the same time, the terminal can also initialize the connection line identifier, the second A control identifier and a second control identifier.

It should be noted that, in the embodiment of this application, if the terminal is disconnected from the external device, then the terminal does not need to prohibit the PMIC from controlling the pins of the USB interface, so there is no need for wireless charging and wired charging. The transition time between transitions is monitored and the first timer can optionally be turned off.

Correspondingly, in the embodiment of the present application, if the terminal is disconnected from the external device, the terminal does not need to trigger the APSD interrupt to determine the device type of the external device, so there is no need to determine the triggering timing of the APSD interrupt. Furthermore, the second timer can be selected to be turned off.

Further, in the embodiment of the present application, the connection line identifier may be used to determine the type of the data line. Specifically, the connection line identifier can be used to determine whether it is a DEBUG line.

Exemplarily, in this application, the variable DEBUG_flag may be used to represent the connection line identifier. When the value of DEBUG_flag is 1 or true, it means that the data line is a DEBUG line; when the value of DEBUG_flag is 0 or false, it means that the data line is not a DEBUG line.

Correspondingly, in the embodiment of the present application, when the terminal establishes a connection with the external device, after determining the connection line type of the connection line with the external device, if the connection line type corresponding to the external device is a debugging line, then The terminal may set the value of the connection line identifier as the first value. Wherein, the first value may be 1 or true.

Further, in the embodiment of the present application, the first control flag may be used to determine whether to prohibit the USBPHY from controlling D+ and D− before charging.

Exemplarily, in this application, the variable USB_ROLE may be used to represent the first control identifier. When the value of USB_ROLE is NONE, it means that the communication of USBPHY needs to be ignored, that is, USBPHY is prohibited from controlling D+ and D-.

Further, in the embodiment of the present application, the second control flag can be used to determine whether to prohibit the USBPHY from controlling D+ and D− before and during charging.

Exemplarily, in this application, the variable ignore_usb_flag may be used to represent the second control flag. When the value of ignore_usb_flag is 1 or true, it means ignoring the state of setting the USB as HOST or DEVICE, releasing the control right of USBPHY to D+ and D- before fast charging, and indicating that the subsequent charging process of this connection is also USBPHY is prohibited from controlling D+ and D-; when the value of ignore_usb_flag is 0 or false, it means that USBPHY is allowed to control D+ and D- before and during charging.

Correspondingly, in this embodiment of the present application, the terminal may choose to set the value of the first control identifier to a second value, and/or set the value of the second control identifier to a third value, Therefore, the USBPHY can be prohibited from controlling the pins of the USB interface. Wherein, the second value may be NONE, and the third value may be 1 or true.

An embodiment of the present application provides a charging method. When establishing a connection with an external device, determine the type of the connection line with the external device; if the type of the connection line is a debugging line, and the device type of the external device is an adapter, Then the pins of the USB interface are set to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; at the same time, the first timer is started; foot control; activate the adapter to establish fast charge communication. It can be seen that, in the embodiment of the present application, the terminal can determine the device type and connection line type corresponding to the external device, so that it can further determine whether to prohibit USBPHY and PMIC from connecting D+ and D- according to the device type and connection line type. control. Specifically, after determining that the external device is an adapter, the external device is connected to the terminal through a DEBUG line, and does not perform wireless charging, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, thereby It can avoid the DEBUG line from interfering with the fast charging communication, and can meet the demand of supporting the use of the DEBUG line for fast charging, greatly improving the charging performance and charging efficiency.

Based on the above-mentioned embodiments, another embodiment of the present application proposes a charging method, which is applied to a terminal, wherein the terminal can be configured with an analog digital signal processing chip ADSP and an application processor AP, wherein the communication between the ADSP and the AP The communication link is GLINK. FIG. 10 is a schematic diagram of the fifth implementation process of the charging method proposed in the embodiment of the present application. As shown in FIG. 10, the method for charging the terminal may further include the following steps:

Step 201, establish a connection with an external device.

Step 202, triggering a TYPE-C interrupt to determine the connection line type.

Step 203 , judging whether the connection line type is a DEBUG line, if yes, execute step 204 and step 205 , otherwise execute step 215 .

In the embodiment of the present application, after the terminal establishes a connection with the external device through the connection line, it can first determine the specific connection line type of the connection line, so that it can further determine whether to establish fast charging communication based on the connection line type . Specifically, the terminal may determine the connection line type of the connection line by triggering a Type-C interrupt. Wherein, the connection line type may be a debugging line (DEBUG line) or a TYPE-C line.

Exemplarily, in this application, when an external device is inserted, the terminal will first trigger a TYPE-C interrupt, wherein, in the interrupt processing function, it will read the corresponding TYPE-C register to determine whether the insertion is a standard TYPE-C line Or the DEBUG line.

Step 204, start timer 1.

Step 205, set the value of the connection line identifier to true.

In the embodiment of the present application, after determining that the type of the connection line is a DEBUG line, the terminal may first start timer 1, and at the same time set the value of the connection line identifier to true.

Exemplarily, in this application, if the terminal is connected to the external device through the DEBUG line, then the ADSP can send a notify message to the AP through the GLINK bus, informing the AP that the currently inserted connection line is the DEBUG line, and accordingly, the AP can connect the connection line The value of the flag DEBUG_flag is set to true, that is, DEBUG_flag=true is set.

Step 206, when the running time of timer 1 is reached, an APSD interrupt is triggered to determine the device type.

Step 207 , judging whether the device type is an adapter, if yes, execute step 208 , otherwise execute step 215 .

Step 208, start timer 2.

In the embodiment of the present application, after the running time of timer 1 is reached, the terminal can determine the device type of the external device by triggering an APSD interrupt. If it is determined that the device type is an adapter, then the terminal chooses to start timer 2. Among them, the running time of timer 1 is used to determine the triggering opportunity of APSD interrupt.

Optionally, in this application, after a period of time after the TYPE-C interrupt (reaching the running time of timer 1, such as several hundred ms), the terminal can choose to trigger the APSD interrupt, wherein the APSD interrupt is charged by BC1.2 The result obtained by the device type identification protocol. When the DCP is recognized, it means that the device type of the external device at this time is an adapter, so APSD needs to send a notify message to the AP again through the GLINK bus to inform the AP that the currently inserted external device is an adapter.

Further, in this application, the ADSP can start the timer 2 with a running time of 800ms, so as to ensure the completion of the conversion process from wireless charging to wired charging.

Step 209 , judging whether the condition for prohibiting the control of D+ and D− is satisfied, if so, execute step 210 , step 211 , step 2012 and step 2013 , otherwise execute step 215 .

Step 210, setting D+ and D- to a high-impedance state.

Step 211. Set the value of the first control flag to NONE.

Step 212. Set the value of the second control identifier to true.

Step 213, when the running time of timer 2 is reached, the identification function of PMIC and BC1.2 is disabled.

In the embodiment of the present application, the terminal can judge whether the conditions for prohibiting the control of D+ and D- are satisfied, and if so, the terminal can choose to set D+ and D- to a high-impedance state, and at the same time, set the value of the first control flag to Set it to NONE, set the value of the second control flag to true, and disable the identification function of PMIC and BC1.2 after the running time of timer 2 is reached. Wherein, the terminal may also choose to combine the charging mode, connection line type and device type to further determine whether to prohibit the control of D+ and D-.

Specifically, when the terminal determines that the connection line type of the connection line with the external device is a debugging line, the device type of the external device is an adapter, and the charging mode is wired charging, it can set D+ and D- to a high-impedance state, thereby Forbid USBPHY to control D+, D-. Then, after exceeding the running time of Timer 2, the PMIC is prohibited from controlling D+ and D-.

Exemplarily, in this application, the AP in the terminal can combine the obtained connection line type, device type, and charging mode to determine whether the condition for prohibiting the control of D+ and D- is met. When DEBUG_flag=true, the external device is an adapter, and When it is not wireless charging, the AP can determine that the USBPHY communication needs to be ignored at this time, so the AP can directly set the value of the first control flag USB_ROLE to NONE, and then it can be applied to the USBPHY of the ADSP through GLINK, that is, the setting of D+ and D- into a high-impedance state.

It should be noted that, in this application, since wireless charging is coupled to the vbus through a wireless coil, an action similar to the identification of the charger type of wired charging will also occur, so the charging mode of wireless charging needs to be eliminated.

It can be understood that, in this application, the high-impedance state means that this state can perform wired AND with other states that control D+ and D-. The above-mentioned other states are the low and high levels of 01 loaded on D+ and D- by VOOPPHY and the adapter level status.

Further, in the embodiment of the present application, in order to prohibit the USBPHY from controlling D+ and D- during the fast charging process, the terminal can also set the second control flag, wherein the second control flag ignore_usb_flag means that it will ignore setting USB as HOST Or a flag of the status of DEVICE. Correspondingly, when the connection line is a DEBUG line, before fast charging, release the right of USBPHY to control D+, D-, and at the same time, the subsequent USBPHY marked by the second control flag ignore_usb_flag is also prohibited from controlling D+, D- , so that the DEBUG line can support fast charging requirements.

It should be noted that, in the embodiment of the present application, when the wireless reverse charging is connected to the wired fast charging, the OTG mode of the wireless reverse charging operation must be switched to the normal charging mode, that is, the conversion process from wireless charging to wired charging , the PMIC needs a certain conversion time, therefore, the terminal will choose to disable the identification function of the PMIC and BC1.2 after reaching the running time of the timer 2.

Optionally, in this application, ADSP can enable VOOCPHY for fast charging communication after starting timer 2 with a running time of 800ms. When the running time of timer 2 is reached, the identification of HVDCP and BC1.2 can be directly disabled, so that the PMIC can avoid the control of D+ and D-.

That is to say, in this application, after determining that the external device is an adapter, and the external device is connected to the terminal through a debugging cable, the terminal can either choose to prohibit the USBPHY from controlling D+, D-, or choose to prohibit the PMIC from controlling D+, D- at the same time. At this time, only VOOPPHY can control D+ and D-, so as to avoid the debugging line (DEBUG line) from interfering with the fast charging communication.

Step 214, activate the adapter, and establish fast charging communication.

In the embodiment of the present application, after the terminal completes the process of prohibiting USBPHY and PMIC from controlling D+ and D-, it can activate the adapter, so as to establish fast charging communication with the adapter.

Optionally, in this application, the terminal can choose to use the enable level shift function to send bursts to deactivate the adapter, and after activating the fast charge adapter, the fast charge communication can be performed normally.

Step 215, do not prohibit USBPHY and PMIC from controlling D+, D-.

Further, in the embodiment of the present application, FIG. 11 is a schematic diagram of the sixth implementation flow of the charging method proposed in the embodiment of the present application. As shown in FIG. 11 , after the connection with the external device is established, that is, after step 201, the terminal performs charging The method may also include the following steps:

Step 216, after the connection with the external device is disconnected, timer 1 and timer 2 are turned off.

Step 207, initialize the connection line ID, the first control ID, and the second control ID.

In the embodiment of this application, when the external device is disconnected from the terminal, the terminal can choose to turn off timer 1 and timer 2, and can also choose to initialize the connection line identifier, the first control identifier, and the second control identifier, that is, in During the unplugging interrupt, you can choose to clear USB_ROLE, DEBUG_flag, ignore_usb_flag and timer, and return to the initial state.

The embodiment of the present application provides a charging method, a terminal device, and a storage medium. When establishing a connection with an external device, determine the type of the connection line connected to the external device; if the type of the connection line is a debugging line, and the external device If the device type is an adapter, set the pins of the USB interface to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; start the first timer at the same time; after exceeding the running time of the first timer, prohibit PMIC controls the pins of the USB interface; activates the adapter to establish fast charging communication. It can be seen that, in the embodiment of the present application, the terminal can determine the device type and connection line type corresponding to the external device, so that it can further determine whether to prohibit USBPHY and PMIC from connecting D+ and D- according to the device type and connection line type. control. Specifically, after determining that the external device is an adapter, the external device is connected to the terminal through a DEBUG line, and does not perform wireless charging, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, thereby It can avoid the DEBUG line from interfering with the fast charging communication, and can meet the demand of supporting the use of the DEBUG line for fast charging, greatly improving the charging performance and charging efficiency.

Based on the above embodiments, in another embodiment of the present application, FIG. 12 is a schematic diagram of the composition and structure of the terminal device proposed in the embodiment of the present application. As shown in FIG. 12 , the terminal device 10 proposed in the embodiment of the present application may include a determination unit 11, setting unit 12, disabling unit 13, activating unit 14,

The determination unit 11 is configured to determine the connection line type of the connection line with the external device when establishing a connection with the external device;

The setting unit 12 is configured to set the pins of the USB interface to a high-impedance state if the connection line type is a debugging line, and the device type of the external device is an adapter, so as to prohibit the USBPHY from controlling the USB interface. The control of the pin; start the first timer at the same time;

The prohibition unit 13 is configured to prohibit the PMIC from controlling the pins of the USB interface after exceeding the running time of the first timer;

The activation unit 14 is configured to activate the adapter to establish fast charging communication.

In the embodiment of the present application, further, FIG. 13 is a second schematic diagram of the composition and structure of the terminal device proposed in the embodiment of the present application. As shown in FIG. 13 , the terminal device 10 proposed in the embodiment of the present application may also include a processor 15, The memory 16 stores instructions executable by the processor 15 . Further, the terminal device 10 may further include a communication interface 17 and a bus 18 for connecting the processor 15 , the memory 16 and the communication interface 17 .

In the embodiment of the present application, the above-mentioned processor 15 may be an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a digital signal processor (Digital Signal Processor, DSP), a digital signal processing device (Digital Signal Processing Device, DSPD) , Programmable Logic Device (ProgRAMmable Logic Device, PLD), Field Programmable Gate Array (Field ProgRAMmable GateArray, FPGA), Central Processing Unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor at least A sort of. It can be understood that, for different devices, the electronic device used to implement the above processor function may also be other, which is not specifically limited in this embodiment of the present application. The terminal device 10 may also include a memory 16, which may be connected to the processor 15, wherein the memory 16 is used to store executable program codes, the program codes include computer operation instructions, and the memory 16 may include a high-speed RAM memory, and may also include Includes non-volatile memory, eg, at least two disk memories.

In the embodiment of the present application, the bus 18 is used to connect the communication interface 17 , the processor 15 and the memory 16 and communicate with each other among these devices.

In the embodiment of the present application, the memory 16 is used to store instructions and data.

Further, in the embodiment of the present application, the above-mentioned processor 15 is configured to determine the connection line type of the connection line with the external device when establishing a connection with the external device; if the connection line type is debugging line, and the device type of the external device is an adapter, then the pins of the USB interface are set to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; simultaneously start the first timer; After the running time of the first timer, the PMIC is prohibited from controlling the pins of the USB interface; the adapter is activated to establish fast charging communication.

In practical application, the above-mentioned memory 16 may be a volatile memory (volatile memory), such as a random access memory (Random-ACCess Memory, RAM); or a non-volatile memory (non-volatile memory), such as a read-only memory (Read-Only Memory, ROM), flash memory (flash memory), hard disk (Hard DiskDrive, HDD) or solid state disk (Solid-State Drive, SSD); instructions and data.

In addition, each functional module in this embodiment may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software function modules.

If the integrated unit is implemented in the form of a software function module and is not sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this embodiment is essentially or The part contributed by the prior art or the whole or part of the technical solution can be embodied in the form of software products, the computer software products are stored in a storage medium, and include several instructions to make a computer device (which can be a personal A computer, a server, or a network device, etc.) or a processor (processor) executes all or part of the steps of the method of this embodiment. The above-mentioned storage medium includes: U disk, mobile hard disk, read only memory (Read Only Memory, ROM), random access memory (Random ACCess Memory, RAM), magnetic disk or optical disk and other various media that can store program codes.

An embodiment of the present application provides a terminal device that determines the connection line type of the connection line with the external device when establishing a connection with the external device; if the connection line type is a debugging line, and the device type of the external device is an adapter, Then the pins of the USB interface are set to a high-impedance state to prohibit the USBPHY from controlling the pins of the USB interface; at the same time, the first timer is started; foot control; activate the adapter to establish fast charge communication. It can be seen that, in the embodiment of the present application, the terminal can determine the device type and connection line type corresponding to the external device, so that it can further determine whether to prohibit USBPHY and PMIC from connecting D+ and D- according to the device type and connection line type. control. Specifically, after determining that the external device is an adapter, the external device is connected to the terminal through a DEBUG line, and does not perform wireless charging, the terminal can choose to prohibit USBPHY and PMIC from controlling D+ and D-, so that only VOOPPHY can control D+ and D-, thereby It can avoid the DEBUG line from interfering with the fast charging communication, and can meet the demand of supporting the use of the DEBUG line for fast charging, greatly improving the charging performance and charging efficiency.

An embodiment of the present application provides a computer-readable storage medium, on which a program is stored, and when the program is executed by a processor, the above-mentioned charging method is implemented.

Specifically, the program instructions corresponding to a charging method in this embodiment can be stored on a storage medium such as an optical disc, a hard disk, or a USB flash drive. When the program instructions corresponding to a charging method in the storage medium are stored in an electronic device When read or executed, it includes the following steps:

When establishing a connection with an external device, determine the connection line type of the connection line with the external device;

If the connection line type is a debugging line, and the device type of the external device is an adapter, then the pins of the USB interface are set to a high-impedance state, to prohibit USBPHY from controlling the pins of the USB interface; simultaneously start first timer;

After exceeding the running time of the first timer, prohibiting the PMIC from controlling the pins of the USB interface;

Activate the adapter to establish fast charge communication.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to the implementation flow diagrams and/or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and/or block in the schematic flowchart and/or block diagram, and a combination of processes and/or blocks in the schematic flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a Means for realizing the functions specified in one or more steps of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in implementing one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in implementing the process flow or processes of the flowchart diagrams and/or the block or blocks of the block diagrams.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the protection scope of the present application.

Claims (13)

1. A charging method, characterized in that the method comprises: When establishing a connection with an external device, determine the connection line type of the connection line with the external device; If the connection line type is a debugging line, and the device type of the external device is an adapter, then the pins of the Universal Serial Bus USB interface are set to a high-impedance state to prohibit the USBPHY from pinning the USB interface. control; start the first timer at the same time; After exceeding the running time of the first timer, prohibiting the PMIC from controlling the pins of the USB interface; Activate the adapter to establish fast charge communication. 2. The method according to claim 1, wherein, when establishing a connection with an external device, determining a connection type of the connection line with the external device comprises: When establishing a connection with the external device, the type of the connection line of the connection line is determined by triggering a Type-C interrupt. 3. The method according to claim 1 or 2, characterized in that, after establishing the connection with the external device, after determining the connection line type of the connection line with the external device, the method further comprises: If the connection line type is a Type-C line and the device type of the external device is an adapter, activate the adapter to establish fast charging communication. 4. The method according to claim 2, characterized in that, after establishing the connection with the external device, after determining the connection line type of the connection line with the external device, the method further comprises: The device type of the external device is determined. 5. The method according to claim 4, wherein the determining the device type of the external device comprises: After triggering the Type-C interrupt, start the second timer; After the running time of the second timer is exceeded, determine the port information corresponding to the external device by triggering an APSD interrupt; Determine the device type according to the port information. 6. The method according to claim 5, wherein the determining the device type according to the port information comprises: If the port information is a dedicated charging port DCP, it is determined that the device type is the adapter. 7. The method according to claim 5, characterized in that, after establishing the connection with the external device, after determining the connection line type of the connection line with the external device, the method further comprises: When the connection with the external device is disconnected, the first timer and the second timer are turned off, and the connection line identifier, the first control identifier, and the second control identifier are initialized. 8. The method according to claim 7, further comprising: If the connection line type is a debugging line, then set the value of the connection line identifier as the first value. 9. The method according to claim 7, further comprising: Set the value of the first control flag to a second value, and/or set the value of the second control flag to a third value, so as to prohibit the USBPHY from controlling the pins of the USB interface. 10. The method of claim 1, further comprising: If the connection line type is a debugging line, the device type is the adapter, and the charging mode is wired charging, then set the pins of the USB interface to a high-impedance state to prohibit the USBPHY from charging the USB control of the pins of the interface; and simultaneously start the first timer. 11. A terminal device, characterized in that the terminal device comprises: a determination unit, a setting unit, a prohibition unit, an activation unit, The determination unit is configured to determine the connection line type of the connection line with the external device when establishing a connection with the external device; The setting unit is configured to set the pins of the USB interface to a high-impedance state if the connection line type is a debugging line, and the device type of the external device is an adapter, so as to prohibit the USBPHY from controlling the USB interface. Pin control; start the first timer at the same time; The prohibition unit is configured to prohibit the PMIC from controlling the pins of the USB interface after exceeding the running time of the first timer; The activation unit is configured to activate the adapter to establish fast charging communication. 12. A terminal device, characterized in that the terminal device includes a processor and a memory storing instructions executable by the processor, and when the instructions are executed by the processor, the implementation of claims 1-10 any one of the methods described. 13. A computer-readable storage medium, on which a program is stored, wherein when the program is executed by a processor, the method according to any one of claims 1-10 is implemented.

Images