CN110113209B - MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure - Google Patents
MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure Download PDFInfo
- Publication number
- CN110113209B CN110113209B CN201910382800.7A CN201910382800A CN110113209B CN 110113209 B CN110113209 B CN 110113209B CN 201910382800 A CN201910382800 A CN 201910382800A CN 110113209 B CN110113209 B CN 110113209B
- Authority
- CN
- China
- Prior art keywords
- state
- slave
- selected state
- master device
- slave devices
- 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.)
- Active
Links
Images
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/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4063—Device-to-bus 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
- G06F13/4291—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using a clocked protocol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an equipment communication method and an equipment topological structure based on an MIPI protocol, wherein the method comprises the following steps: connecting a transmitting port of a master device with a plurality of slave devices; configuring a state machine on all slave devices; all slave devices judge whether receiving a receiving end selection command, if so, all the slave devices enter a waiting state from a sharing state; the slave equipment in the waiting state receives the ID matching data packet sent by the master equipment and judges whether the ID matching data packet is matched or not, if yes, the slave equipment enters a selected state from the waiting state, and if not, the slave equipment enters a non-selected state from the waiting state; and the slave equipment in the selected state receives the data and/or the control command sent by the master equipment through the sending port and processes the data and/or the control command. The invention can reduce the development difficulty of the sending port on the main equipment, and the complexity of the connection and the control between the main equipment and the slave equipment, and improve the stability of the system.
Description
Technical Field
The invention relates to the technical field of display, in particular to an MIPI (Mobile industry processor interface) protocol-based inter-device communication method and an MIPI protocol-based inter-device communication topology structure.
Background
With the continuous improvement of living standard, mobile consumer electronics products, such as mobile phones, tablet computers, cameras, etc., are widely used. Display systems in mobile consumer electronics generally include a main device and a display module, where the main device controls the display module to display images. The main device and the display module are usually communicated by using an MIPI protocol, that is, a transmitting port (marked as MIPITX) for transmitting MIPI signals is arranged on the main device, a receiving port (marked as MIPI RX) for receiving the MIPI signals is arranged on the display module, and the transmitting port and the receiving port are connected through Data Lane 0-Data Lane3 and a Clock Lane signal wire.
In a display system, when a host device needs to connect a plurality of display modules, usually, a plurality of MIPITX ports are arranged on the host device, each MIPITX port is correspondingly connected with a display module, or a MIPITX port on the host device is connected with a plurality of display modules, however, the development difficulty of the host device is increased by arranging a plurality of MIPITX ports on the host device, meanwhile, when a plurality of display modules are connected at a MIPITX port for reading data, competition is easily generated, when the competition exists, MIPI connection lines between the host device and all the display modules are controlled by a selector switch, at any moment, at most only MIPI connection lines between one display module and the host device are connected, and in this way, the connection complexity and the control complexity between the host device and the slave device are easily caused, and the instability of the display system is easily caused.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides an equipment communication method and an equipment topological structure based on an MIPI protocol.
In order to achieve the purpose, the invention provides the following technical scheme: an inter-device communication method based on MIPI protocol includes the following steps:
s100, connecting a master device provided with at least one sending port with a plurality of slave devices provided with receiving ports, wherein each sending port is correspondingly connected with the receiving ports of the plurality of slave devices;
s200, configuring state machines on all slave devices connected with a sending port, wherein the state machines comprise a sharing state, a waiting state, a selected state and a non-selected state;
s300, all the slave devices connected with the sending port judge whether receiving end selection commands sent by the master device are received, if yes, all the slave devices enter a waiting state from a sharing state, and the step S400 is executed;
s400, the slave equipment in the waiting state receives an ID matching data packet sent by the master equipment through a sending port, whether the ID matching data packet is matched or not is further judged, if the ID matching data packet is matched, the slave equipment enters a selected state from the waiting state, and the step S500 is executed;
s500, the slave device in the selected state receives the data and/or the control command sent by the master device through the sending port, and processes the data and/or the control command.
Preferably, all the slave devices connected to the transmitting port are initially in the sharing state, and the slave devices in any state enter the sharing state after receiving the receiving end sharing command.
Preferably, the master device transmits data and/or control commands to all slave devices connected to the transmission port through the transmission port when all the slave devices are in the shared state, and the master device does not read data to the slave devices.
Preferably, the receiver selection command and the receiver sharing command are set by an unused code in escape mode entry coding in the MIPI protocol.
Preferably, in step S400, the ID matching packet is generated by encoding a general short write data packet or a general long write data packet in the MIPI protocol.
Preferably, in step S500, the slave device in the selected state further determines whether a receiving end selection command sent by the master device is received, and enters a waiting state from the selected state when the receiving end selection command is received, or the slave device in the selected state determines whether a receiving end sharing command sent by the master device is received, and enters a sharing state from the selected state when the receiving end sharing command is received.
Preferably, in step S400, the slave device whose ID data packet does not match enters a non-selected state from a waiting state, and the slave device in the non-selected state does not receive any data and/or control command except the receiving end selection command and the receiving end sharing command sent by the master device through the sending port;
the slave device in the non-selected state further judges whether a receiving end selection command sent by the master device is received or not, and enters a waiting state from the non-selected state when the receiving end selection command is received, or the slave device in the non-selected state judges whether a receiving end sharing command sent by the master device is received or not, and enters a sharing state from the non-selected state when the receiving end sharing command is received.
The invention also discloses a device topological structure based on the MIPI protocol, which comprises a main device provided with at least one sending port and a plurality of slave devices provided with receiving ports, wherein each sending port is correspondingly connected with the receiving ports of the plurality of slave devices.
Preferably, all the slave devices connected with the sending port are provided with a state machine module for state transition.
Preferably, the master device is further provided with a data packet generation module for generating an ID matching data packet.
Preferably, all the slave devices connected to the sending port are further provided with a matching module for determining whether the ID matching packets are matched.
The invention has the beneficial effects that:
(1) the invention can make one sending port of the main device connect with a plurality of slave devices, can effectively reduce the development difficulty of the sending port on the main device, and reduce the complexity of the connection between the main device and the slave devices, and the main device can broadcast data and/or control commands to all the slave devices when the slave devices are in a sharing state, thereby realizing the effect of global control, and the main device can also independently carry out data mutual transmission with the slave devices in a selected state.
(2) The invention can effectively reduce the control complexity between the master device and the slave device, reduce the power consumption of the system and improve the stability of the system by enabling the slave device in the non-selected state not to receive any data sent by the master device, only receiving the receiving end selection command and the receiving end sharing command sent by the master device and entering the corresponding state according to the corresponding command.
Drawings
FIG. 1 is a schematic flow chart of the method of the present invention;
FIG. 2 is a schematic diagram of the topology of the apparatus of the present invention;
FIG. 3 is a state transition diagram of the present invention;
FIG. 4 is a diagram of the Escape Entry Code when the Escape Mode is used in accordance with the present invention;
FIG. 5 is a diagram of a custom ID match packet format for a generic shortwrite packet;
fig. 6 is a diagram illustrating a structure of a slave reception port.
Detailed Description
The technical solution of the embodiment of the present invention will be clearly and completely described below with reference to the accompanying drawings of the present invention.
As shown in fig. 1, the MIPI protocol-based inter-device communication method disclosed in the present invention includes the following steps:
step S100, connecting a master device provided with at least one sending port with a plurality of slave devices provided with receiving ports, wherein each sending port is correspondingly connected with the receiving ports of the plurality of slave devices;
specifically, as shown in fig. 1 and fig. 2, a plurality of transmitting ports (denoted as MIPITX interfaces) for transmitting MIPI signals are provided on the master device, one or more receiving ports (denoted as MIPI RX interfaces) for receiving MIPI signals are provided on the slave device, and each MIPITX interface on the master device is correspondingly connected to MIPI RX interfaces of a plurality of slave devices. In implementation, the MIPITX interface is connected to the MIPI RX interface through a Data signal transmission line 0(Data Lane0), a Data signal transmission line 1(Data Lane1), a Data signal transmission line 2(Data Lane2), a Data signal transmission line 3(Data Lane3), and a Clock signal transmission line (Clock Lane). Each Data signal transmission line is composed of two transmission lines supporting LVDS (Low-Voltage Differential Signaling), which are respectively denoted as a Dp transmission line and a Dn transmission line, wherein the Data signal transmission line 0 is a bidirectional Data channel, and the MIPITX interface and the MIPI RX interface can transmit Data to each other through the Data signal transmission line 0(Data Lane 0).
In this embodiment, an Application Processor (AP) is preferred by the master device, and a display module is preferred by the slave device, where the display module includes a display screen and a driving chip for driving the display screen to display an image, each MIPITX interface on the Application Processor may be connected to at most MIPI RX interfaces of N driving chips, and N is an integer greater than or equal to 2.
Step S200, configuring state machines on all slave devices connected with a sending port, wherein the state machines comprise a shared state (Share), a waiting state (Wait), a selected state (Hit) and a non-selected state (Miss);
specifically, as shown in fig. 3, a state machine is configured on all the slave devices connected to the transmitting port, the state machine is used for indicating which state the slave device is currently in, the state machine includes a shared state (Share), a waiting state (Wait), a selected state (Hit) and a non-selected state (Miss), and the states can be mutually converted, and different operations can be performed when the slave device is in different states. In specific implementation, after initialization, all slave devices are in a shared state (Share).
When the slave device is in the Share state (Share), the D-PHY (Display Serial Interface Physical Layer) of the receiving port on each slave device is in the STOP state (RX-STOP), and the master device may control the slave device to enter HSDT (High Speed Data Transmission) Mode or Escape Mode. When the slave device enters Escape Mode, the master device may transmit Escape Entry Code to all slave devices connected to the transmit port through the transmit port, and the slave device enters a corresponding Mode according to the Escape Entry Code and performs a corresponding operation. If the Escape Entry Code sent by the master device to the slave device is 01100010, the slave device enters a Reset-Trigger mode, or if the Escape Entry Code is 00011110, the slave device enters an ULPS (Ultra _ Low Power State) mode, or if the Escape Entry Code is 11100001, the slave device enters an LPDT (Low-Power Data Transmission) mode. As shown in fig. 4, the Escape Entry Code further includes a plurality of unused codes, such as binary 00100001, 01011101, etc., which can be customized by the user according to actual requirements, so that the slave device performs corresponding operations when receiving corresponding codes.
In practice, when all the slaves are in the shared state (Share), the master can send data or control commands to all the slaves connected to the send port through the send port, but the master does not read data from the slaves and does not hand over the bus ownership with the slaves, and the master can control all the slaves to perform certain operations in a unified manner.
When the slave device is in a waiting state (Wait), the slave device waits for an ID matching data packet sent by the master device through a sending port connected with the slave device, and the slave device further judges whether the ID matching data packet is matched or not after receiving the ID matching data packet. If the current waiting state (Wait) is matched with the selected state (Hit), the slave device enters the selected state (Hit) from the current waiting state (Wait), otherwise, the slave device enters the unselected state (Miss) from the current waiting state (Wait). In practice, the master device transmits an ID matching packet to the slave device connected to the transmission port via the transmission port in HSDT mode or LPDT mode (LPDT mode is preferred), and the slave device does not process other packets or control commands transmitted by the master device.
When the slave device is in the selected state (Hit), the slave device receives the data and/or control command sent by the master device, and further processes the data or control command accordingly. If the master device reads data from the slave device, the master device needs to transfer bus ownership with the slave device, and after the slave device obtains the bus ownership, the slave device sends corresponding data to the master device, where the data includes a Read reply (Read Response) packet and/or an acknowledgement Error Report (Acknowledge) packet.
When the slave device is in a non-selected state (Miss), the slave device does not perform any processing on data transmitted by the master device and/or control commands other than the receiving-end selection command and the receiving-end sharing command, and does not perform a handover of bus ownership with the master device. In implementation, in order to save power consumption, when the master device and the slave device in the selected state (Hit) enter the HSDT Mode, the slave device in the unselected state (Miss) does not enter the HSDT Mode, does not accept data transmission in the LPDT Mode, receives only the receiving end selection command and the receiving end sharing command in the Escape Mode, and enters the corresponding state according to the corresponding commands.
In specific implementation, the state machine is preferably configured on a Protocol Layer (Protocol Layer) of the slave device.
Step S300, all the slave devices connected with the sending port judge whether receiving end selection commands sent by the master device are received, if yes, all the slave devices enter a waiting state (Wait) by a shared state (Share), and step S400 is executed;
specifically, after system initialization, all slave devices are in a shared state (Share). All the slave devices in the shared state (Share) judge whether receiving end selection commands (RX-Select Trigger Command) sent by the master device through the sending port are received, and the receiving end selection commands are used for enabling the slave devices to enter a waiting state (Wait) from the shared state (Share). If receiving the receiving end selection command, all the slave devices enter a waiting state (Wait) from the sharing state, and all the slave devices entering the waiting state (Wait) further execute step S400. Otherwise, all slave devices continue to maintain the shared state (Share).
In specific implementation, as shown in fig. 4, the receiving end selection command may be defined by an unused Code in the Escape Entry Code in the MIPI protocol, for example, the unused Code 01011101 in the Escape Entry Code is customized as the receiving end selection command, or the unused Code 00100111 in the Escape Entry Code is customized as the receiving end selection command, and in specific implementation, the receiving end selection command may be set according to requirements.
Step S400, the slave device in the waiting state (Wait) receives the ID matching data packet sent by the master device through the sending port, further judges whether the ID matching data packet is matched, if so, the slave device enters a selected state (Hit) from the waiting state (Wait), and executes step S500.
Specifically, all slave devices in the waiting state (Wait) Wait for the ID matching packet transmitted by the master device. And after receiving the ID matching data packet, the slave device further judges whether the ID matching data packet is matched, if so, the slave device enters a selected state (Hit) from a waiting state (Wait), and step S500 is executed. Otherwise, the slave device enters a non-selected state (Miss) from a waiting state (Wait). The slave device in the non-selected state (Miss) does not perform any process on data transmitted from the master device and/or control commands other than the receiver-side selection command and the receiver-side sharing command, and does not perform a handover of bus ownership with the master device. Meanwhile, the slave device in the non-selected state (Miss) also judges whether a receiving end selection command or a receiving end sharing command sent by the master device is received, when the receiving end selection command is received, the slave device enters a waiting state (Wait) from the non-selected state (Miss), and when the receiving end sharing command is received, the slave device enters a sharing state (Share) from the non-selected state (Miss).
In specific implementation, the master device may self-define an ID matching Packet through a general Short Write Packet (Generic Short Write Packet) or a general Long Write Packet (Generic Long Write Packet) in the MIPI protocol, the master device sends the ID matching Packet to the slave device to perform ID matching, and for a matched slave device, the slave device enters a selected state (Hit) from a Wait state (Wait).
In this embodiment, a general short write data packet with two valid parameters is taken as an example, and the ID matching data packet is described in detail. The header of the general short write Data packet with two valid parameters is 0x23, as shown in fig. 5, the format of the Data packet is matched for the custom ID, where the Data ID, that is, the header, is 0x 23; data0 is ID matching Data packet identification code; data1 is the ID Data carried; ECC is a check code. In implementation, both the master device and the slave device agree on the ID matching data packet identifier, and if the agreed ID matching data identifier is 0xF 0. After receiving a universal short write Data packet with a header of 0x23 from a slave device in a waiting state (Wait), judging whether the ID agreed by both parties in the Data0 matches a Data packet identification code, if so, judging whether the ID agreed by both parties matches the Data packet identification code, if so, further judging whether the ID Data (e.g. 0x03) in the Data1 matches the number of the slave device, if so, entering a selected state (Hit) from the slave device, and if not, entering a non-selected state (Miss) from the slave device. If the packet header of the received packet is not 0x23 or the packet header is 0x23 but the ID agreed by both parties in the Data0 does not match the packet identifier, the slave device does not process the packet.
Further, the slave device in the Wait state (Wait) further determines whether a receiver-Share Command (RX-Share Command) sent by the master device is received, and if so, the slave device enters the Share state (Share) from the Wait state (Wait). In implementation, the receiving end sharing command may be defined by an unused Code in the Escape Entry Code in the MIPI protocol, for example, the unused Code 10100000 in the Escape Entry Code is self-defined as the receiving end sharing command, or the unused Code 10101100 in the Escape Entry Code is self-defined as the receiving end sharing command, and in specific implementation, the Code used by the receiving end sharing command is different from the Code used by the receiving end selection command.
Step S500, the slave device in the selected state (Hit) receives the data and/or control command sent by the master device through the sending port, and processes the data and/or control command.
Specifically, when the master device writes data to the slave device in the selected state, the master device encodes the data to be written into a DSI packet, and further sends the DSI packet to the slave device in the selected state (Hit) through a sending port, and the slave device processes the DSI packet and records errors (Error) that may occur; when the master device sends a control command to the slave device in the selected state (Hit), the slave device in the selected state processes the control command; when the master device reads Data from the selected slave device, the master device sends a Read request Data packet to the slave device in the selected state, and further performs bus ownership transfer with the slave device, and after the slave device obtains the bus ownership, the slave device sends Data to the master device through a Data signal line 0(Data Lane0), wherein the Data comprises a Read reply (Read reply) Data packet and/or an acknowledgement Error Report (Acknowledge and Error Report) Data packet. After the data transmission is completed, the D-PHY of the receiving port on the slave device is in a STOP state (TX-STOP), then the receiving port on the slave device performs bus ownership transfer with the transmitting port on the master device, and after the slave device transfers the bus ownership to the master device, the D-PHY of the receiving port enters a STOP state (RX-STOP).
In practice, the Bus ownership handover is performed by the master device through a Bus ownership handover sequence (Bus around Procedure) and the slave device.
Further, the slave device in the selected state (Hit) needs to determine whether a receiver selection Command (RX-Select Trigger Command) or a receiver sharing Command (RX-Share Trigger Command) sent by the master device is received. When receiving the receiving end selection command, the slave device enters a waiting state (Wait) from a selected state (Hit), and when receiving the receiving end sharing command, the slave device enters a sharing state (Share) from the selected state (Hit).
Further, if the master device has a Contention (context) with the slave device in the selected state (Hit), the master device performs processing according to a processing scheme in which the Contention (context) occurs when the master device is connected to a single slave device, and the slave device is still in the selected state (Hit) after the processing is completed. If the slave device in the selected state (Hit) returns to the shared state (Share) due to a system abnormality or the like, the master device controls other devices to return to the shared state through the receiving-end sharing command.
Referring to fig. 2 and fig. 6, the present invention further discloses a device topology based on the MIPI protocol, including a master device provided with at least one transmitting port and a plurality of slave devices provided with receiving ports, where each transmitting port is correspondingly connected to the receiving ports of the plurality of slave devices.
Specifically, the master device is provided with a plurality of transmitting ports (denoted as MIPI TX interfaces) for transmitting MIPI signals, the slave device is provided with one or more receiving ports (denoted as MIPI RX interfaces) for receiving MIPI signals, and each MIPITX interface on the master device is correspondingly connected to the MIPI RX interfaces of the plurality of slave devices. In implementation, the MIPITX interface is connected to the MIPI RX interface through a Data signal transmission line 0(Data Lane0), a Data signal transmission line 1(Data Lane1), a Data signal transmission line 2(Data Lane2), a Data signal transmission line 3(Data Lane3), and a Clock signal transmission line (Clock Lane). Each Data signal transmission line is composed of two transmission lines supporting LVDS (Low-Voltage Differential Signaling), which are respectively denoted as a Dp transmission line and a Dn transmission line, wherein the Data signal transmission line 0 is a bidirectional Data channel, and the MIPITX interface and the MIPI RX interface can transmit Data to each other through the Data signal transmission line 0(Data Lane 0).
In this embodiment, the master device preferably selects an Application Processor (AP), and the slave device preferably selects a display module, where the display module includes a display screen and a driving chip for driving the display screen to display an image, and each MIPITX interface on the Application Processor may be connected to MIPI RX interfaces of N driving chips at most, where N is an integer equal to or greater than 2.
As shown in fig. 6, all the slave devices connected to the transmitting port are further provided with a state machine module, the state machine module is used for indicating what state the slave device is currently in, the state machine includes a shared state (Share), a waiting state (Wait), a selected state (Hit) and a non-selected state (Miss), and the states can be switched to each other, and different operations can be performed when the slave device is in different states. In specific implementation, after initialization, all slave devices are in a shared state (Share). The operations performed when the slave device is in various states are described in detail above.
Further, the host device is further provided with a data Packet generation module, the data Packet generation module is used for generating an ID matching data Packet, and the data Packet generation module can self-define the ID matching data Packet through a general Short Write data Packet (general Short Write Packet) or a general Long Write data Packet (general Long Write Packet) in the MIPI protocol. In this embodiment, a general short write data packet with two valid parameters is taken as an example, and the ID matching data packet is described in detail. The header of the general short write Data packet with two valid parameters is 0x23, as shown in fig. 5, the format of the Data packet is matched for the custom ID, where the Data ID, that is, the header, is 0x 23; data0 is ID matching Data packet identification code; data1 is the ID Data carried; ECC is a check code. In implementation, both the master device and the slave device agree on the ID matching data packet identifier, and if the agreed ID matching data identifier is 0xF 0. After receiving a universal short write Data packet with a header of 0x23 from a slave device in a waiting state (Wait), judging whether the ID agreed by both parties in the Data0 matches a Data packet identification code, if so, judging whether the ID agreed by both parties matches the Data packet identification code, if so, further judging whether the ID Data (e.g. 0x03) in the Data1 matches the number of the slave device, if so, entering a selected state (Hit) from the slave device, and if not, entering a non-selected state (Miss) from the slave device. If the packet header of the received packet is not 0x23 or the packet header is 0x23 but the ID agreed by both parties in the Data0 does not match the packet identifier, the slave device does not process the packet.
Furthermore, all slave devices connected with the sending port are also provided with matching modules, and the matching modules are used for judging whether the ID matching data packets are matched or not. The matching module determines the ID matching packet as described above.
The invention can make one MIPITX port of the main device connect with a plurality of slave devices, which can effectively reduce the development difficulty of the sending interface on the main device and the complexity of the connection between the main device and the slave devices, and the main device can broadcast data and/or control commands to all the slave devices when the slave devices are in a sharing state, which can realize the effect of global control, and the main device can also independently carry out data mutual transmission with the slave devices in a selected state (Hit).
The slave device in the non-selected state (Miss) only receives the receiving end selection command and the receiving end sharing command sent by the master device, enters the corresponding state according to the received command, and does not receive data and other control commands sent by the master device, so that the control complexity between the master device and the slave device can be effectively reduced, the power consumption of a system is reduced, and the stability of the system is improved.
Therefore, the scope of the present invention should not be limited to the disclosure of the embodiments, but includes various alternatives and modifications without departing from the scope of the present invention, which is defined by the claims of the present patent application.
Claims (11)
1. An inter-device communication method based on MIPI protocol is characterized by comprising the following steps:
s100, connecting a master device provided with at least one sending port with a plurality of slave devices provided with receiving ports, wherein each sending port is correspondingly connected with the receiving ports of the plurality of slave devices;
s200, configuring state machines on all slave devices connected with a sending port, wherein the state machines comprise a sharing state, a waiting state, a selected state and a non-selected state;
s300, all the slave devices connected with the sending port judge whether receiving end selection commands sent by the master device are received, if yes, all the slave devices enter a waiting state from a sharing state, and the step S400 is executed;
s400, the slave equipment in the waiting state receives an ID matching data packet sent by the master equipment through a sending port, whether the ID matching data packet is matched or not is further judged, if the ID matching data packet is matched, the slave equipment enters a selected state from the waiting state, and the step S500 is executed;
s500, the slave device in the selected state receives the data and/or the control command sent by the master device through the sending port, and processes the data and/or the control command.
2. The method of claim 1, wherein all slave devices connected to the transmitting port are initially in a shared state, and wherein a slave device in any state enters the shared state after receiving a receive side sharing command.
3. Method according to claim 1 or 2, characterized in that the master device sends data and/or control commands to all slave devices connected to the send port through the send port when all slave devices are in a shared state, and the master device does not read data to the slave devices.
4. The method of claim 2, wherein the receiver select command and the receiver share command are set by an unused code in escape mode entry coding in the MIPI protocol.
5. The method of claim 1, wherein in step S400, the ID matching packet is generated by encoding a general short write data packet or a general long write data packet in MIPI protocol.
6. The method according to claim 1, wherein in step S500, the slave device in the selected state further determines whether a receiver selection command sent by the master device is received and enters a waiting state from the selected state when the receiver selection command is received, or the slave device in the selected state determines whether a receiver sharing command sent by the master device is received and enters a sharing state from the selected state when the receiver sharing command is received.
7. The method according to claim 1, wherein in step S400, the slave device whose ID data packet does not match enters the non-selected state from the waiting state, and the slave device in the non-selected state does not receive any data and/or control command except the receiver selection command and the receiver sharing command sent by the master device through the sending port;
the slave device in the non-selected state further judges whether a receiving end selection command sent by the master device is received or not, and enters a waiting state from the non-selected state when the receiving end selection command is received, or the slave device in the non-selected state judges whether a receiving end sharing command sent by the master device is received or not, and enters a sharing state from the non-selected state when the receiving end sharing command is received.
8. An equipment topology structure for realizing the communication method between the equipments according to any one of claims 1 to 7 based on the MIPI protocol, which is characterized by comprising a master equipment provided with at least one transmitting port and a plurality of slave equipments provided with receiving ports, wherein each transmitting port is correspondingly connected with the receiving ports of the plurality of slave equipments.
9. The device topology of claim 8, wherein all slave devices connected to a transmit port are provided with a state machine module for state transition.
10. The device topology of claim 9, wherein a packet generation module for generating an ID matching packet is further disposed on the master device.
11. The device topology of claim 10, wherein all slave devices connected to the sending port are further provided with a matching module for determining whether ID matching packets match.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910382800.7A CN110113209B (en) | 2019-05-09 | 2019-05-09 | MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910382800.7A CN110113209B (en) | 2019-05-09 | 2019-05-09 | MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110113209A CN110113209A (en) | 2019-08-09 |
| CN110113209B true CN110113209B (en) | 2022-02-15 |
Family
ID=67489006
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910382800.7A Active CN110113209B (en) | 2019-05-09 | 2019-05-09 | MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110113209B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110138761B (en) * | 2019-05-09 | 2021-10-15 | 豪威触控与显示科技(深圳)有限公司 | MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure |
| CN112165544B (en) * | 2020-09-29 | 2021-09-24 | 维沃移动通信有限公司 | Electronic equipment communication control method and device and electronic equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103226536A (en) * | 2012-01-30 | 2013-07-31 | 英飞凌科技股份有限公司 | System and method for a bus interface |
| CN106933770A (en) * | 2015-12-30 | 2017-07-07 | 联发科技（新加坡）私人有限公司 | Data handling system and its operating method and wireless communication unit |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI536862B (en) * | 2012-11-06 | 2016-06-01 | 聯詠科技股份有限公司 | Data transmission system and method |
| US10970243B2 (en) * | 2016-01-29 | 2021-04-06 | Qorvo Us, Inc. | Front end serial bus automatic bus park tri-state activation |
-
2019
- 2019-05-09 CN CN201910382800.7A patent/CN110113209B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103226536A (en) * | 2012-01-30 | 2013-07-31 | 英飞凌科技股份有限公司 | System and method for a bus interface |
| CN106933770A (en) * | 2015-12-30 | 2017-07-07 | 联发科技（新加坡）私人有限公司 | Data handling system and its operating method and wireless communication unit |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110113209A (en) | 2019-08-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI507880B (en) | Data-exchange system and its master device | |
| US20040260851A1 (en) | Data transmission method for microprocessors in a programmable logic controller | |
| CN104205781A (en) | Superspeed inter-chip communications | |
| KR20160077189A (en) | Camera control slave devices with multiple slave device identifiers | |
| KR102032862B1 (en) | Arbitration Signaling within a Multimedia High Definition Link (MHL3) Device | |
| CN107819659B (en) | Intelligent cascade communication network based on SPI | |
| CN104281548A (en) | Method, device and system for data transmission based on AXI bus | |
| CN110113209B (en) | MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure | |
| CN107741915A (en) | A kind of FPGA plate level communicators and communication means based on SDIO interfaces | |
| CN110138761B (en) | MIPI (Mobile industry processor interface) protocol-based inter-device communication method and equipment topological structure | |
| KR20150096495A (en) | Apparatus and method for encoding mdio into sgmii transmissions | |
| CN202694039U (en) | Adapter circuit | |
| KR20060087827A (en) | Sata device having self-test function for oob signaling | |
| CN1316387C (en) | Serial interface bus communication controller | |
| JP2000194649A (en) | Method and apparatus for electronic device connection | |
| CN111884987B (en) | Electronic device and method for electronic device | |
| WO2012071925A1 (en) | Single board communication system and communication method thereof | |
| CN217467655U (en) | Single IO mouth two-way communication structure of singlechip | |
| CN100362502C (en) | Radio transmission system of I2C bus data | |
| CN116684389B (en) | Address automatic allocation method and host, slave and communication equipment with same | |
| CN116185936B (en) | SPI communication data receiving and transmitting abnormity detection control system and detection method | |
| CN210899197U (en) | Single-wire bidirectional communication circuit | |
| CN112882967B (en) | Serial port conversion circuit and debugging method | |
| CN110049367B (en) | Method for transmitting and receiving wireless transmission video signal and controlling bidirectional touch | |
| CN106937070B (en) | Bidirectional control method in FPD-LINK low-voltage differential signal video transmission |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 518063 2405, yuemeite building, No. 1, Gaoxin South seventh Road, high tech Zone community, Yuehai street, Nanshan District, Shenzhen, Guangdong Applicant after: Howell touch and display technology (Shenzhen) Co.,Ltd. Address before: 518000 Room 601, east block, Haibin City, Wenxin 5th Road, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province Applicant before: SHENZHEN JIDISI ELECTRONIC TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |