CN117271398A - Low-power interface control method, device, equipment and storage medium - Google Patents

Low-power interface control method, device, equipment and storage medium Download PDF

Info

Publication number
CN117271398A
CN117271398A CN202311391068.2A CN202311391068A CN117271398A CN 117271398 A CN117271398 A CN 117271398A CN 202311391068 A CN202311391068 A CN 202311391068A CN 117271398 A CN117271398 A CN 117271398A
Authority
CN
China
Prior art keywords
state
target
jump
determining
handshake protocol
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311391068.2A
Other languages
Chinese (zh)
Inventor
官志勇
陈举龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xinli Intelligent Technology Jiangsu Co ltd
Original Assignee
Xinli Intelligent Technology Jiangsu Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Xinli Intelligent Technology Jiangsu Co ltd filed Critical Xinli Intelligent Technology Jiangsu Co ltd
Priority to CN202311391068.2A priority Critical patent/CN117271398A/en
Publication of CN117271398A publication Critical patent/CN117271398A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/10—Program control for peripheral devices
    • G06F13/12—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor
    • G06F13/124—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine
    • G06F13/126—Program control for peripheral devices using hardware independent of the central processor, e.g. channel or peripheral processor where hardware is a sequential transfer control unit, e.g. microprocessor, peripheral processor or state-machine and has means for transferring I/O instructions and statuses between control unit and main processor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/40—Bus structure
    • G06F13/4063—Device-to-bus coupling
    • G06F13/4068—Electrical coupling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
    • G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Power Sources (AREA)

Abstract

The invention discloses a low-power interface control method, a device, equipment and a storage medium. Comprising the following steps: acquiring configuration parameters of a slave-end low-power interface, and determining a target handshake protocol according to the configuration parameters; acquiring a state jump request of a slave end, and carrying out state jump of a master end according to a target handshake protocol and the state jump request so as to generate an interrupt signal; and acquiring a control instruction based on the interrupt signal, and performing interface control according to the control instruction. The method comprises the steps of determining a target handshake protocol through configuration parameters of a low-power interface, sending a state jump request to a master terminal through a slave terminal when the power consumption state of the slave terminal changes, enabling the master terminal to carry out state jump according to the target handshake protocol and the state jump request, generating an interrupt signal through a hardware module to remind software, further realizing interface control, avoiding the software from participating in a complicated and lengthy handshake process, reducing the cost of the software, realizing the whole power consumption jump process through the hardware module, and providing maximum flexibility and usability without software participation.

Description

Low-power interface control method, device, equipment and storage medium
Technical Field
The present invention relates to the field of interface control technologies, and in particular, to a method, an apparatus, a device, and a storage medium for controlling a low power interface.
Background
The interface types of the AMBA low-power interface comprise Q-Channel and P-Channel, and the Q-Channel is used for realizing simple power control, such as power-on and power-off. P-Channel is used to implement complex power control, such as full power up, half power up, 1/4 power up, etc.
A common implementation is in software, but this approach requires a significant overhead in software. Because the whole P/Q channel protocol adopts a handshake mechanism, the software needs to constantly read and write related registers and perform state inquiry and register setting, so the software spends more, and for some special power consumption state changes, the software is more complex to process, and the software cannot directly jump among some power consumption states, and the like. And in the power consumption control process, the cooperation of handshaking of the power consumption interface and other signals requires additional processing, such as cooperation with a reset signal, etc.
Disclosure of Invention
The invention provides a low-power interface control method, a device, equipment and a storage medium, which are used for realizing automatic interface conversion according to a protocol and realizing control of a low-power interface.
According to an aspect of the present invention, there is provided a low power consumption interface control method, including:
acquiring configuration parameters of a slave-end low-power interface, and determining a target handshake protocol according to the configuration parameters, wherein the target handshake protocol comprises a state jump array;
acquiring a state jump request of a slave end, and carrying out state jump of a master end according to a target handshake protocol and the state jump request so as to generate an interrupt signal;
and acquiring a control instruction based on the interrupt signal, and performing interface control according to the control instruction.
Optionally, determining the target handshake protocol according to the configuration parameters includes: determining the number of power consumption states according to the configuration parameters; determining a target interface type according to the number of power consumption states, wherein the interface type comprises Q-Channel and P-Channel; and acquiring a handshake protocol list, and screening the handshake protocol list through the target interface type to acquire a target handshake protocol corresponding to the target interface type, wherein the handshake protocol list comprises handshake protocols corresponding to the interface types.
Optionally, determining the number of power consumption states according to the configuration parameter includes: matching the configuration parameters according to the specified fields to obtain target parameters corresponding to the specified fields; the target parameter is extracted as the number of power consumption states.
Optionally, determining the target interface type according to the number of power consumption states includes: judging whether the number of the power consumption states is more than two, if so, determining that the type of the target interface is P-Channel; otherwise, determining the type of the target interface as Q-Channel.
Optionally, before acquiring the state jump request of the slave, the method further includes: determining the current working state of the slave end, and determining the last working state adjacent to the current working state according to the appointed period; when the slave end judges that the current working state is inconsistent with the previous working state, the current working state is taken as a state to be jumped; a state jump request is generated based on the state to be jumped.
Optionally, performing state skipping of the master according to the target handshake protocol and the state skipping request includes: when the host receives the state jump request, inquiring a target element value corresponding to the state jump request according to the state jump number group; judging whether the target element value is 1, if so, directly performing state jump of the main terminal; otherwise, the indirect state jump of the master terminal is carried out based on the state jump request.
Optionally, performing indirect state jump of the master based on the state jump request includes: determining a state to be jumped contained in the state jump request, and setting an indirect jump state and an indirect jump mark for the state to be jumped; and reading the indirect jump mark based on the master terminal so as to jump the master terminal to an indirect jump state.
According to another aspect of the present invention, there is provided a low power interface control apparatus comprising:
the target handshake protocol determining module is used for acquiring configuration parameters of the slave-end low-power interface and determining a target handshake protocol according to the configuration parameters, wherein the target handshake protocol comprises a state jump array;
the interrupt signal generation module is used for acquiring a state jump request of the slave end, and carrying out state jump of the master end according to the target handshake protocol and the state jump request so as to generate an interrupt signal;
and the interface control module is used for acquiring a control instruction based on the interrupt signal and performing interface control according to the control instruction.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform a low power interface control method according to any one of the embodiments of the present invention.
According to another aspect of the present invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to implement a low power interface control method according to any one of the embodiments of the present invention when executed.
According to the technical scheme, the target handshake protocol is determined through the configuration parameters of the low-power interface, the state jump request is sent to the main terminal when the power consumption state of the main terminal is changed, so that the main terminal performs state jump according to the target handshake protocol and the state jump request, and the hardware module generates an interrupt signal to remind software, so that interface control is realized, the software can be prevented from participating in a complicated and lengthy handshake process, the cost of the software is reduced, the whole power consumption jump process is realized through the hardware module, the software participation is not needed, and the maximum flexibility and usability are provided.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a low power interface control method according to a first embodiment of the present invention;
FIG. 2 is a flowchart of another low power interface control method according to a first embodiment of the present invention;
FIG. 3 is a flowchart of another low power interface control method according to a first embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating a signal interaction process of a low power interface control system according to a first embodiment of the present invention;
FIG. 5 is a flowchart of another low power interface control method according to the second embodiment of the present invention;
fig. 6 is a schematic structural diagram of a low power interface control device according to a third embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device implementing a low-power interface control method according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1 is a flowchart of a low power interface control method according to an embodiment of the present invention, where the method may be performed by a low power interface control device, the low power interface control device may be implemented in hardware and/or software, and the low power interface control device may be configured in a computer controller. As shown in fig. 1, the method includes:
s110, acquiring configuration parameters of the slave-end low-power-consumption interface, and determining a target handshake protocol according to the configuration parameters, wherein the target handshake protocol comprises a state jump array.
The low power interface refers to an advanced microcontroller bus architecture (Advanced Microcontroller Bus Architecture, AMBA) interface. The low power interface is used to implement the power control function. Currently, AMBA contains 2 types of low power interfaces, Q-Channel and P-Channel. Handshaking refers to the process of establishing a connection between two devices, i.e., a connection needs to be established between a master and a slave before communication can take place. The master end and the slave end can carry out a handshake process according to a target handshake protocol, wherein the target handshake protocol comprises a state jump array. The state jump number group refers to an array set by a user and used for judging a state jump mode, and the hardware module can check the state to be jumped according to the state jump array. The configuration parameters refer to the number of parameterized power consumption states of a user, and the parameterized power consumption states are defined, so that the user can configure the parameters according to the actual conditions of the interfaces, and different interfaces can be supported. The user refers to a worker or technician performing low power interface control. For example, there are 5 power consumption states supported by ARM A78 core, and the number of bits of the packet is 20 bits; whereas a common q-channel has only 2 power consumption states, no active. The number of power consumption states, the number of bits of a section, etc. must therefore be defined by parameters to support different interfaces.
Fig. 2 is a flowchart of a low power interface control method according to an embodiment of the present invention, and step S110 mainly includes steps S111 to S114 as follows:
s111, acquiring configuration parameters of the slave-end low-power-consumption interface.
S112, determining the number of power consumption states according to the configuration parameters.
Optionally, determining the number of power consumption states according to the configuration parameter includes: matching the configuration parameters according to the specified fields to obtain target parameters corresponding to the specified fields; the target parameter is extracted as the number of power consumption states.
Specifically, since the configuration parameters include the number of parameterized power consumption states configured by the user, the controller can match the configuration parameters according to the specified field, wherein the specified field is a field including the number of power consumption states, and the target parameters corresponding to the specified field can be obtained through matching, and then the target parameters are extracted as the number of power consumption states.
S113, determining a target interface type according to the number of power consumption states, wherein the interface type comprises Q-Channel and P-Channel.
Optionally, determining the target interface type according to the number of power consumption states includes: judging whether the number of the power consumption states is more than two, if so, determining that the type of the target interface is P-Channel; otherwise, determining the type of the target interface as Q-Channel.
The interface types comprise Q-Channel and P-Channel, and the Q-Channel is used for realizing simple power control, such as power-on and power-off. P-Channel is used to implement complex power control, such as full power up, half power up, 1/4 power up, etc. In some scenarios, the component has only two power states, power-up, power-down, respectively. Therefore, the power control of the component only needs to be powered on and powered off. This is achieved with Q-Channel. While in other scenarios, the component has multiple power states, such as full power, half power, 1/4 power, etc. The power control of such a component is therefore much more complex, and it is not simple to power it up, it is powered down, and some additional control is required. In this case, Q-Channel is not suitable, and P-Channel is required.
Specifically, the controller may determine the target interface type according to the number of power consumption states. When the number of the power consumption states is greater than two, determining that the type of the target interface is P-Channel; and when the number of the power consumption states is less than or equal to two, determining that the type of the target interface is Q-Channel.
S114, acquiring a handshake protocol list, and screening the handshake protocol list through a target interface type to acquire a target handshake protocol corresponding to the target interface type, wherein the handshake protocol list comprises handshake protocols corresponding to the interface types.
Specifically, the handshake protocol list includes handshake protocols corresponding to each interface type, and the controller screens the handshake protocol list through the target interface type to obtain a target handshake protocol corresponding to the target interface type, i.e., the P-Channel interface type corresponds to the P-Channel interface protocol, and the Q-Channel interface type corresponds to the Q-Channel interface protocol.
S120, acquiring a state jump request of the slave end, and carrying out state jump of the master end according to the target handshake protocol and the state jump request so as to generate an interrupt signal.
The state jump request is a request generated when the slave sends state jump, the state jump is that the current working state of the slave is inconsistent with the last working state, at the moment, the master can acquire the state jump request of the slave, perform state interaction and generate an interrupt signal after completion.
Fig. 3 is a flowchart of a low power interface control method according to an embodiment of the present invention, and step S120 mainly includes steps S121 to S125 as follows:
s121, acquiring a state jump request of the slave.
S122, when the host receives the state jump request, inquiring a target element value corresponding to the state jump request according to the state jump number group.
Wherein, the state jump array contains a plurality of elements, and the value of each element is 0 or 1,0 represents that the jump is forbidden, and 1 represents that the jump can be realized. When the master receives the state jump request, the target element value corresponding to the state jump request may be queried from the state jump number group. The target element value is 0 or 1, and the master end further determines whether to directly jump or indirectly jump according to the target element value.
S123, judging whether the target element value is 1, if so, executing S124, otherwise, executing S125.
S124, directly performing state jump of the main terminal to generate an interrupt signal.
S125, performing indirect state jump of the master end based on the state jump request to generate an interrupt signal.
Specifically, the main end can detect the state jump request through the hardware module, inquire the target element value corresponding to the state jump request, when the target element value is 1, the state jump can be directly performed, and when the target element value is 0, the indirect state jump of the main end is performed based on the state jump request, namely, the jump hardware between the power consumption states automatically judges whether the direct jump can be performed, and if the direct jump cannot be performed, the indirect jump can be performed, for example, through the state transfer of a third party. After the jump is completed, an interrupt signal can be generated.
Optionally, performing indirect state jump of the master based on the state jump request includes: determining a state to be jumped contained in the state jump request, and setting an indirect jump state and an indirect jump mark for the state to be jumped; and reading the indirect jump mark based on the master terminal so as to jump the master terminal to an indirect jump state.
Specifically, the state jump request includes a current state and a state to be jumped, when the state jump request is made, the master end will determine the state to be jumped included in the state jump request, set an indirect jump state and an indirect jump flag for the state to be jumped, the indirect jump flag may be "ON", and after the indirect jump flag is set, the parameter table prohibits the state of direct jump, and automatically jumps through the "ON" state.
By way of example, when the hardware module of the master detects a state jump request through the state jump number set, the state to be jumped of the current state can be queried and combined, the element value is found to be 0 or 1 in the jump parameter set, and if the element value is 1, the state jump flow is directly performed. If the value is 0, the state to be jumped is set to be the ON state, meanwhile, the indirect jump mark is set, and the jump flow of jumping to the ON state is carried out first. After the process is completed, the jump process from the ON state to the final state is continuously applied. The whole power consumption jump flow can be completely and automatically completed through the hardware module, software participation is not needed at all, and the maximum flexibility and usability are provided. And interface conversion can be automatically carried out according to the protocol, and software is not needed in the interaction process. After the interaction is completed, the module generates interrupt reminding system software.
S130, acquiring a control instruction based on the interrupt signal, and performing interface control according to the control instruction.
Specifically, the interrupt signal is a signal for instructing the user to perform authority control. The controller can acquire a control instruction based on the interrupt signal, wherein the control instruction refers to an instruction for controlling authority input by a user through a user terminal, and the user terminal is connected with the controller. The controller may perform interface control according to the control instruction. The interrupt signal generation mode is completed through state interaction, so that the software can be prevented from participating in a complicated and lengthy handshake process, and the cost of the software is reduced. A change in power consumption state or an interrupt is acquired after handshake is completed, and sufficient control authority can be obtained.
The specific embodiment is as follows: fig. 4 is a schematic diagram of a signal interaction process of a low-power interface control system according to a first embodiment of the present invention, where fig. 4 includes a system signal interaction process when the interface types are Q-Channel and P-Channel, and fig. 4 includes a signal interaction schematic diagram among a system master control device (controller), a master device (master end), and a slave end (slave end).
According to the technical scheme, the target handshake protocol is determined through the configuration parameters of the low-power interface, the state jump request is sent to the main terminal when the power consumption state of the main terminal is changed, so that the main terminal performs state jump according to the target handshake protocol and the state jump request, and the hardware module generates an interrupt signal to remind software, so that interface control is realized, the software can be prevented from participating in a complicated and lengthy handshake process, the cost of the software is reduced, the whole power consumption jump process is realized through the hardware module, the software participation is not needed, and the maximum flexibility and usability are provided.
Example two
Fig. 5 is a flowchart of a low power interface control method according to a second embodiment of the present invention, where a process of generating a state jump request is added on the basis of the first embodiment. The specific contents of steps S210 and S260 are substantially the same as steps S110 and S130 in the first embodiment, so that a detailed description is omitted in this embodiment. As shown in fig. 5, the method includes:
s210, acquiring configuration parameters of the slave-end low-power-consumption interface, and determining a target handshake protocol according to the configuration parameters, wherein the target handshake protocol comprises a state jump array.
Optionally, determining the target handshake protocol according to the configuration parameters includes: determining the number of power consumption states according to the configuration parameters; determining a target interface type according to the number of power consumption states, wherein the interface type comprises Q-Channel and P-Channel; and acquiring a handshake protocol list, and screening the handshake protocol list through the target interface type to acquire a target handshake protocol corresponding to the target interface type, wherein the handshake protocol list comprises handshake protocols corresponding to the interface types.
Optionally, determining the number of power consumption states according to the configuration parameter includes: matching the configuration parameters according to the specified fields to obtain target parameters corresponding to the specified fields; the target parameter is extracted as the number of power consumption states.
Optionally, determining the target interface type according to the number of power consumption states includes: judging whether the number of the power consumption states is more than two, if so, determining that the type of the target interface is P-Channel; otherwise, determining the type of the target interface as Q-Channel.
S220, determining the current working state of the slave end, and determining the last working state adjacent to the current working state according to the designated period.
And S230, when the slave end judges that the current working state is inconsistent with the previous working state, taking the current working state as a state to be jumped.
S240, generating a state jump request according to the state to be jumped.
Specifically, the slave terminal determines whether the power consumption state is changed according to the current working state of the slave terminal, the slave terminal determines the last working state adjacent to the current working state according to the specified period, when the slave terminal judges that the current working state is inconsistent with the last working state, the slave terminal determines that the power consumption state is changed, and at the moment, the slave terminal generates a state jump request, namely the current working state is used as a state to be jumped, so that the state jump request is generated and sent to the master terminal.
S250, acquiring a state jump request of the slave end, and carrying out state jump of the master end according to the target handshake protocol and the state jump request so as to generate an interrupt signal.
Optionally, performing state skipping of the master according to the target handshake protocol and the state skipping request includes: when the host receives the state jump request, inquiring a target element value corresponding to the state jump request according to the state jump number group; judging whether the target element value is 1, if so, directly performing state jump of the main terminal; otherwise, the indirect state jump of the master terminal is carried out based on the state jump request.
Optionally, performing indirect state jump of the master based on the state jump request includes: determining a state to be jumped contained in the state jump request, and setting an indirect jump state and an indirect jump mark for the state to be jumped; and reading the indirect jump mark based on the master terminal so as to jump the master terminal to an indirect jump state.
And S260, acquiring a control instruction based on the interrupt signal, and performing interface control according to the control instruction.
According to the technical scheme, the target handshake protocol is determined through the configuration parameters of the low-power interface, the state jump request is sent to the main terminal when the power consumption state of the main terminal is changed, so that the main terminal performs state jump according to the target handshake protocol and the state jump request, and the hardware module generates an interrupt signal to remind software, so that interface control is realized, the software can be prevented from participating in a complicated and lengthy handshake process, the cost of the software is reduced, the whole power consumption jump process is realized through the hardware module, the software participation is not needed, and the maximum flexibility and usability are provided.
Example III
Fig. 6 is a schematic structural diagram of a low power interface control device according to a third embodiment of the present invention. As shown in fig. 6, the apparatus includes:
a target handshake protocol determining module 310, configured to obtain a configuration parameter of the slave low-power interface, and determine a target handshake protocol according to the configuration parameter, where the target handshake protocol includes a state hop array;
the interrupt signal generation module 320 is configured to obtain a state jump request of the slave, and perform state jump of the master according to the target handshake protocol and the state jump request, so as to generate an interrupt signal;
the interface control module 330 is configured to obtain a control instruction based on the interrupt signal, and perform interface control according to the control instruction.
Optionally, the target handshake protocol determining module 310 specifically includes: a power consumption state number determining unit configured to: determining the number of power consumption states according to the configuration parameters; a target interface type determining unit configured to: determining a target interface type according to the number of power consumption states, wherein the interface type comprises Q-Channel and P-Channel; and acquiring a handshake protocol list, and screening the handshake protocol list through the target interface type to acquire a target handshake protocol corresponding to the target interface type, wherein the handshake protocol list comprises handshake protocols corresponding to the interface types.
Optionally, the power consumption state number determining unit is specifically configured to: matching the configuration parameters according to the specified fields to obtain target parameters corresponding to the specified fields; the target parameter is extracted as the number of power consumption states.
Optionally, the target interface type determining unit is specifically configured to: judging whether the number of the power consumption states is more than two, if so, determining that the type of the target interface is P-Channel; otherwise, determining the type of the target interface as Q-Channel.
Optionally, the apparatus further comprises: a state jump request generation module, configured to: before acquiring a state jump request of a slave end, determining the current working state of the slave end, and determining the last working state adjacent to the current working state according to a specified period; when the slave end judges that the current working state is inconsistent with the previous working state, the current working state is taken as a state to be jumped; a state jump request is generated based on the state to be jumped.
Optionally, the interrupt signal generation module 320 specifically includes: a target element value query unit, configured to: when the host receives the state jump request, inquiring a target element value corresponding to the state jump request according to the state jump number group; a target element value judging unit configured to: judging whether the target element value is 1; the direct jump unit is used for directly carrying out state jump of the main end when the target element value is 1; and the indirect jump unit is used for carrying out indirect state jump of the main end based on the state jump request when the target element value is not 1.
Optionally, performing indirect state jump of the master based on the state jump request includes: determining a state to be jumped contained in the state jump request, and setting an indirect jump state and an indirect jump mark for the state to be jumped; and reading the indirect jump mark based on the master terminal so as to jump the master terminal to an indirect jump state.
According to the technical scheme, the target handshake protocol is determined through the configuration parameters of the low-power interface, the state jump request is sent to the main terminal when the power consumption state of the main terminal is changed, so that the main terminal performs state jump according to the target handshake protocol and the state jump request, and the hardware module generates an interrupt signal to remind software, so that interface control is realized, the software can be prevented from participating in a complicated and lengthy handshake process, the cost of the software is reduced, the whole power consumption jump process is realized through the hardware module, the software participation is not needed, and the maximum flexibility and usability are provided.
The low-power interface control device provided by the embodiment of the invention can execute the low-power interface control method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example IV
Fig. 7 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 7, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as a low power interface control method. Namely: acquiring configuration parameters of a slave-end low-power interface, and determining a target handshake protocol according to the configuration parameters, wherein the target handshake protocol comprises a state jump array; acquiring a state jump request of a slave end, and carrying out state jump of a master end according to a target handshake protocol and the state jump request so as to generate an interrupt signal; and acquiring a control instruction based on the interrupt signal, and performing interface control according to the control instruction.
In some embodiments, a low power interface control method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of a low power interface control method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform a low power interface control method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present invention may be performed in parallel, sequentially, or in a different order, so long as the desired results of the technical solution of the present invention are achieved, and the present invention is not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims (10)

1. A low power interface control method, comprising:
acquiring configuration parameters of a slave-end low-power interface, and determining a target handshake protocol according to the configuration parameters, wherein the target handshake protocol comprises a state jump array;
acquiring a state jump request of a slave end, and carrying out state jump of a master end according to the target handshake protocol and the state jump request so as to generate an interrupt signal;
and acquiring a control instruction based on the interrupt signal, and performing interface control according to the control instruction.
2. The method of claim 1, wherein said determining a target handshake protocol according to said configuration parameters comprises:
determining the number of power consumption states according to the configuration parameters;
determining a target interface type according to the number of power consumption states, wherein the interface type comprises Q-Channel and P-Channel;
and acquiring a handshake protocol list, and screening the handshake protocol list through the target interface type to acquire a target handshake protocol corresponding to the target interface type, wherein the handshake protocol list comprises handshake protocols corresponding to the interface types.
3. The method of claim 2, wherein said determining the number of power consumption states from the configuration parameters comprises:
matching the configuration parameters according to the specified fields to obtain target parameters corresponding to the specified fields;
and extracting the target parameter as the number of power consumption states.
4. The method of claim 2, wherein the determining a target interface type from the number of power consumption states comprises:
judging whether the number of the power consumption states is more than two, if so, determining that the type of the target interface is P-Channel;
otherwise, determining the type of the target interface as Q-Channel.
5. The method of claim 1, further comprising, prior to the obtaining the state jump request from the slave:
determining the current working state of a slave end, and determining the last working state adjacent to the current working state according to a specified period;
when the slave end judges that the current working state is inconsistent with the last working state, the current working state is used as a state to be jumped;
and generating the state jump request according to the state to be jumped.
6. The method of claim 5, wherein the performing the state jump of the master according to the target handshake protocol and the state jump request comprises:
when the master receives a state jump request, inquiring a target element value corresponding to the state jump request according to the state jump number group;
judging whether the target element value is 1, if so, directly performing state jump of the main terminal;
otherwise, the indirect state jump of the master terminal is carried out based on the state jump request.
7. The method of claim 6, wherein the performing the indirect state jump at the master based on the state jump request comprises:
determining a state to be jumped contained in the state jump request, and setting an indirect jump state and an indirect jump mark for the state to be jumped;
and reading the indirect jump mark based on the master terminal so as to jump the master terminal to the indirect jump state.
8. A low power interface control apparatus, comprising:
the device comprises a target handshake protocol determining module, a state jump module and a state jump module, wherein the target handshake protocol determining module is used for acquiring configuration parameters of a slave-end low-power interface and determining a target handshake protocol according to the configuration parameters;
the interrupt signal generation module is used for acquiring a state jump request of the slave end, and carrying out state jump of the master end according to the target handshake protocol and the state jump request so as to generate an interrupt signal;
and the interface control module is used for acquiring a control instruction based on the interrupt signal and performing interface control according to the control instruction.
9. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
10. A computer storage medium storing computer instructions for causing a processor to perform the method of any one of claims 1-7 when executed.
CN202311391068.2A 2023-10-25 2023-10-25 Low-power interface control method, device, equipment and storage medium Pending CN117271398A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311391068.2A CN117271398A (en) 2023-10-25 2023-10-25 Low-power interface control method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311391068.2A CN117271398A (en) 2023-10-25 2023-10-25 Low-power interface control method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN117271398A true CN117271398A (en) 2023-12-22

Family

ID=89208937

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311391068.2A Pending CN117271398A (en) 2023-10-25 2023-10-25 Low-power interface control method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN117271398A (en)

Similar Documents

Publication Publication Date Title
EP3519917B1 (en) Prioritized sequencing of device inrush current
US9477293B2 (en) Embedded controller for power-saving and method thereof
CN114564435A (en) Inter-core communication method, device and medium for heterogeneous multi-core chip
CN115955518A (en) Communication conversion method, device and storage medium for communication between master equipment and slave equipment
WO2024113767A1 (en) Power-on method and power-on apparatus for smart network interface cards
CN115484233B (en) Method, device, equipment and medium for forwarding link aggregation message in digital communication chip
CN117271398A (en) Low-power interface control method, device, equipment and storage medium
CN116243978A (en) Data protocol method, device, medium and training system in distributed training
CN116301676A (en) Printing equipment connection method, device, equipment and storage medium
CN116126092A (en) Clock supply method, system, server and storage medium
CN114707651A (en) Topology selection method, device, equipment and medium for protocol operation
CN115061976A (en) Address configuration method, device, carrier board, core board, server and medium
CN113766488A (en) Data transmission method and electronic equipment
CN106776035B (en) Method and system for realizing cross-system multi-document algorithm docking and request heterogeneous system
CN107977294B (en) Method and device for monitoring temperature of electronic element
CN117312100B (en) Power consumption adjustment method, system, device, equipment and computer storage medium
CN117033029A (en) Data transmission method, device, equipment and medium
CN116306407B (en) Verification method, device, equipment and storage medium of Network On Chip (NOC)
US12032708B2 (en) Remote access method, electronic device, and storage medium
CN117573170A (en) CPLD updating method and device, electronic equipment and storage medium
US20210349516A1 (en) Energy saving device and method for saving energy in data center
CN117370209A (en) Application program performance test method, device, medium and electronic equipment
CN117651078A (en) Data transmission method and device, electronic equipment and storage medium
CN116880787A (en) Printer management method and device, electronic equipment and storage medium
CN117439975A (en) Address determination method and device for equipment mainboard, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination