TWI376114B - Methods and systems for synchronous execution of commands across a communication link - Google Patents

Description

1376114 d) IX. Description of the Invention [Technical Field] The present invention relates to a method and system for synchronously executing commands on a communication link. In particular, the present invention relates to a method and system for simultaneously executing commands on a Mobile Display Digital Interface (MDDI) link. [Prior Art] In the field of interconnect technology, there is a growing need for data transfer rates, particularly with video displays. The demand for related data transmission rates continues to grow. The Action Display Digital Interface (MDDI) is a cost-effective, low-power transfer mechanism that enables very high-speed data transfer on short-range communication links between the host and the user. MDDI requires only four cable-plus power supplies for bidirectional data transfer with a maximum bandwidth of up to 3.2 Gbits per second. In an application, MDDI increases the reliability and power consumption of a covered phone by significantly reducing the number of wires that traverse the handset hub to interconnect the digital baseband controller with a liquid crystal (LCD) display and/or camera. . This reduction in wiring also allows handset manufacturers to reduce development costs by simplifying the design of flip-top or slide-type phones. A typical MDDI interconnect includes an MDDI controller that connects a controller that is an MDDI link master to another MDDI link client controller via an MDDI link. In connection with a baseband processor to a device such as a camera module, the interface is also typically used to relay commands from the processor to the device. For example, Pathfinder is a device interface developed by Qualcomm, -4- (2) (2) 1376114, which has an integrated MDDI host core that can be used to interface via MDDI. A baseband processor (with an MDDI client core) and a device such as a camera. Commands sent by the baseband processor through MDDI usually do not require synchronization. However, for example, when controlling the camera, some of the commands issued by the baseband processor require precise synchronization at the camera. For example, a flash sync is required for a flash to accurately coincide with the opening of the camera shutter. However, typically, the message sent by the baseband processor through the MDDI link causes a delay, and the delay depends on the use of the link and cannot be accurately estimated. 6 Therefore, to achieve synchronization at the camera. In contrast, synchronizing commands at the processor while attempting to compensate for delays via the link is not a reliable solution. Accordingly, what is needed is a method and system for synchronizing the execution of commands transmitted by a baseband processor to a device such as a camera via an MDDI link. SUMMARY OF THE INVENTION The present invention is directed to a method and system for synchronously executing commands on a communication link. In particular, the invention relates to a method and system for simultaneously executing commands on a Mobile Display Digital Interface (MDDI) link. In one aspect, a method for synchronously executing a plurality of commands generated by a first module and executed at a second module is provided, wherein the first module and the second module are connected via a communication chain Road to communication. The method includes generating a command at a first module, transmitting the commands to the second module over the communication link, and causing execution time of the commands at the second module

-5- (3) 1376114 " An independent event is associated. When the independent event is detected, the commands are executed synchronously at the second mode group. In another aspect, the method may be specifically applied to control a camera's baseband processor through a camera module interface, wherein the baseband processor and camera module interface are via an MD DI link. Come and connect. An example of a baseband mobile station data machine (MSM) processor that controls the camera through the Pathfinder camera module interface. A specific built-in mechanism within the camera module interface that enables the φ elastic implementation of the above method is also provided. Further embodiments, features, and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, will be described in detail with reference to the accompanying drawings. Example. The disclosed embodiments are merely illustrative of the invention. The scope of the present invention is not limited to the disclosed embodiments. The invention is defined by the scope of the appended claims. The embodiments described, and the "one embodiment," "the embodiment", "an example embodiment" and the like as referred to in the specification, may include a particular feature and structure. ' or feature, but each embodiment does not necessarily include the feature, structure, or feature. Moreover, such terms do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or feature is recited in connection with an embodiment, the feature, structure, or feature of the invention may be considered to be associated with other embodiments, whether or not explicitly recited. 4) (4) 1376114 is within the knowledge of those skilled in the art. Embodiments of the invention may be practiced in hardware, firmware, software, or any combination thereof. Embodiments of the invention may also be implemented as instructions stored on a machine readable medium, which may be read and executed by one or more processors. A machine readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, machine readable media may include read only memory (ROM): random access memory (RAM): disk storage media; optical storage media; flash memory devices; electrical, optical 'acoustic or other forms. Propagation signals (eg, carrier waves, infrared signals, digital signals, etc.), as well as other signals. In addition, firmware, software, programs, and instructions may be described herein as performing specific actions. However, it should be appreciated that such a description is merely for convenience, and such an action is actually caused by a computing device, processor, controller, or other device that executes firmware, software, programs, or instructions. Action Display Digital Interface (MDDI) The Mobile Digital Interface (MDDI) is a cost-effective, low-power transfer mechanism that enables very high-speed serial data to be transferred to short-range communication between the host and the user. On the link. The following section will present an example of MDDI for the camera module included in the top cover mobile phone. However, any module having equivalent functionality to the camera module can be readily substituted and used in embodiments of the present invention, as will be apparent to those skilled in the art. (5) 1376114 Further, in accordance with embodiments of the present invention, several types can benefit from the use of the present invention. For example, the host can be a portable computer in the form of a handheld, mobile computing device. One of the main material assistant (PDA), a paging device, or the public. Alternatively, the host can be a device such as a portable DVD or CD player. In addition, the host can exist as a host device or control element in a variety of industrialized products, high speed communication links. For example, the host can be used to transfer data from a video recording device to a high rate, or for presentation to a high resolution large screen transfer data computing system and/or Bluetooth node. · Electrical appliances for refrigerators, when operating on the Internet, can have improved display capabilities, or when (host) is in other places in the cabinet, can (customer) with a small keyboard or scanner (customer says, Xi The skilled artisan will appreciate that various data electronic devices and appliances can be used to renovate old i MDDI customers with new or existing connectors or cables with limited high data rate information. One of the devices that can be included in the MDDI host for presenting or presenting information from the user to the host. The laptop, or the like, can also be a multi-person wireless telephone or data modem portable entertainment. Or introduce the installation 'or a game machine widely used or planned business because the customer wants and the host to improve the response to the storage-based customer At a high rate, remember from the video, such as the on-board inventory or the road or Bluetooth connection mode included in other home devices, the electronic computer or control system can reduce the wiring requirements for the indoor display. It is generally more specialized in terms of the use of this interface and the use of wires that can be used in a number of ways. At the same time, the information is now available to the end user. For example, a microdisplay that is incorporated into -8 - (6) (6) 1376114 goggles or glasses, a projection device built into a hat or helmet, built into a car, such as in a window or wiper. Small screen or holographic components, or a variety of speakers, headphones, or sound systems for high-quality sound and music. Other presentation devices include projectors or projection devices that are used to present conference or movie and television images. Another example would be the use of a touch pad or a sensitive device, a voice recognition input device, a security scanner, etc., which can be requested to differ from the touch or sound from the user. The "input" transfers a large amount of information from the device or system user. In addition, computer docking stations and car or desk kits and stands for wireless phones can be used as interface devices to end users or other devices and devices, and use customers (such as mouse output) Or input device) or host to assist with data transfer, especially in the case of high speed networks. However, it will be readily apparent to those skilled in the art that the present invention is not limited to these devices, and there are many other devices on the market that are suggested for use, regardless of the point of view of storage and shipping or the viewpoint displayed during playback. They are all intended to provide high quality images and sounds for end users. The present invention is useful in increasing the throughput of various components or devices to provide the high data rate required to achieve the desired user experience. 1A is a diagram of a digital data device interface 100 coupled to a digital device 150 and a peripheral device 180. Digital device I 50 may include, but is not limited to, a cellular telephone, a personal data assistant, a smart phone, or a personal computer. In general, digital device 150 may include any type of digital device that is used as a processing unit for processing digital instructions and digital display data. Digital installation

-9 - (7) (7) 1376114 Set 1 50 includes a system controller 1 60 and a link controller 1 70. Peripheral device 180 can include, but is not limited to, a camera, a bar code reader, an image scanner, an audio device, and a sensor. In general, peripheral device 180 can include any type of audio, video or image capture and display device in which digital display data is exchanged between peripheral devices and processing units. Peripheral device 80 includes a control block 190. For example, when peripheral device 180 is a camera, control block 190 can include, but is not limited to, lens control, flash or white LED control and shutter control. The digital display data may include digital data representing audio, video and multimedia data. The digital data interface device 1 transfers data at a high rate on a communication link 105. In one example, an MDDI communication link can be used that supports bidirectional data transfer with a maximum bandwidth of 3.2 Gbits per second. Data transfer at other high rates above or below the rate of this example can be supported, depending on the communication link. The digital data interface device 100 includes a message interpreter module 1 , a content module 1 20 , a control module I 30 , and a link controller 140 . A link controller 14A located within the digital data interface 100, and a link controller 170 located within the digital device 150 establish a communication link 〇5. Link controller 140 and link controller 1 70 may be MDDI link controllers. The Video Electronics Standards Association ("VESA") MDDI standard, which is hereby incorporated as a reference, describes the requirements for high-speed digital packet interfaces, while the high-speed digital packet interface allows portable devices to transfer digital devices from small portable devices. Image to a larger external display. MDDI will be suitable for connecting -10- (8) (8) 1376114 portable computing 'communication and entertainment devices' small connector systems and thin flexible cables to emerging products such as wearable microdisplays. MDDI also includes information on how to simplify the connection between the host processor and the display to reduce costs and increase the reliability of these connections. The link controller 140 and the link controller 170 establish a communication path 105° according to the VESA MDDI standard. US Patent No. 6,760,772, the patent name is a high-speed data signal transmission protocol and interface generation and implementation (Generating and Implementing a Communication Protocol and Interface for High Data Rate Signal Transfer), issued to the inventor. Zou et al., July 6, 2004 ("772 Patent"), which describes a data interface whose use is linked together to form a communication protocol. For displaying data, the digital data is transferred between the host and the client on the communication path. Embodiments of the invention taught in the '772 patent are related to the MDDI interface signal protocol being used by a link controller, such as link controllers 140 and 170, which are organized to generate, transmit, and form a communication protocol with reception. The packet is formed into one or more types of data packets, and at least one link controller is present in the host device and coupled to the client via a communication path (eg, communication path I 05 ). The interface provides a cost-effective 'low-power, two-way, and high-speed data transfer mechanism for short-range "serial" data links that are suitable for implementation with small connectors and thin flexible cables. Embodiments of controllers 140 and 170 establish communication paths 1〇5 in accordance with the teachings of the '772 patent. The “7 72 Patent” is hereby incorporated as a reference in its entirety. (9) 1376114 'In other embodiments, both link controllers 140 and 1 70 may be USB link controllers or both may include a controller (eg, 'MDDI Link Controller') and Another type of keying controller ' (for example, a combination of USB link controllers) Alternatively, the link controllers 1 40 and 170 may include a controller (eg, an MD DI link controller) A combination of a single link for exchanging an endorsement message between the digital data interface 100 and the digital device 150. In addition, the link controllers φ 40 and 170 can support other types of interfaces, such as Ethernet or RS-232 serial port interface. Other interfaces may also be supported, as will be familiar to those skilled in the art in light of the teachings herein. In the digital data interface device 100, the message interpreter module 110 receives a command from the system controller 160 via the communication chain 105 and generates a response message to the system controller 160, interpreting the command message, and Route the information content of the commands to the appropriate modules in the digital data interface device. The φ content module 120 receives the data from the peripheral device 180 through the communication link 105, stores the data, and transfers the data to the system controller 160. The control module 130 receives the information from the message interpreter. And arrange the information to the routing of the control block 180 of the peripheral device 180. The control module 130 can also receive information from the control block 190 and schedule the information to the message interpreter module 110. FIG. 1 is a block diagram showing an example environment in which an MDDI interface is used. In the example of Figure 1, the MDDI is used to interconnect the modules across the -12-(10) (10) 1376114 hinge of the flip-phone 1〇〇. The lower cover portion 102 of the clamshell phone 100 includes a mobile station data unit (MSM) baseband chip 104. The MSM 104 is a digital baseband processor. The upper cover portion 114 of the clamshell phone 100 includes a liquid crystal display (LCD) module and a camera module interface 118. Still referring to Figure 1 'MDDI Link Connection Camera Module Interface H8 to MSM 104 » Typically MDDI Link Controller is integrated into each of Camera Module Interface 118 and MSM 104. In the example of FIG. 1, MDDI host controller 122 is integrated into camera module interface 18 while MDDI client controller 106 is present on the MSM side of the MDDI link. Typically, the MDDI host is the primary controller for the MDDI link. In the example of Figure 1, pixel data from camera module interface 1 18 is received and formatted into MDDI packets by MDDI host controller 122 before the pixel data is transferred to the MDDI link. The MDDI client controller receives the MDDI packets and reconverts them into pixel data in the same format as that produced by camera module I 18 . The pixel data is then sent to the appropriate block of MSM 104 for processing. The MDDI link 112 connects the LCD module 116 to the MSM 104. In the example of FIG. 1, the MDDI link 112 interconnect is integrated into the MDDI host controller 108 in the MSm 104 and the MDDI client controller 120 integrated into the LCD module 116. In the example of Figure 1, the image material generated by the graphics controller of the MSM 104 is received by the MDDI host controller 108 and formatted into MDDI packets before it is transmitted onto the MDDI link 112. The MDDI client controller 120 receives the MDDI packets and converts them into image data for use by the L C D module 116. -13- (11) (11) 1376114 Typically, the image data is buffered using a frame buffer before being used to update the LCD display. MSM to Camera Module Interface Communication Figure 2 is a block diagram illustrating an MDDI link interconnect 200 in accordance with the example of Figure 1. The MDDI link interconnect 200 includes an MDDI client 106 that is integrated into the baseband MSM processor, and an MDDI host 122 that is integrated into the camera module interface 118, while the MDDI client 106 and the MDDI host 122 pass through the MDDI link 110. And connected. Camera module 2 is coupled to camera module interface 1 18 by one or more interfaces. Therefore, the camera module interface 1 18 provides an interface between the baseband M S Μ processor and the camera module. For example, the camera module interface 118 can be a Pathfinder camera interface developed by Qualcomm. In addition to the MDDI host core 122, the camera module interface 118 includes a camera message interpreter 02, a camera control block 2〇4, and a video front end block 206», as shown in FIG. 2, and several interfaces are connected to the data bus. Various blocks of the camera module interface. Through the scratchpad access message interface 210, the Camera Message Interpreter (CMI) 02 receives the data and control signals embedded in the reverse register access packet from the MSM. The CMI 202 decodes the received signal from the MSM and uses the configuration interface 2 1 2 and 2 1 4 of the MDDI host I 22 or camera control block 24 to execute the corresponding command (scratchpad read and hold) Write to the memory). In addition, through the scratchpad access message interface 21, -14- (12) 1376114 CMI 2 02 sends the acknowledgement (for the scratchpad write command) or the login (read command) back to the MDDI host core. 122, while the MDDI core forwards its trunk to the MSM. A camera control block (CCB) 204 is provided to the camera register to execute commands received at the CMI 202. The CCB 204 includes sub-modules (not shown in Figure 2), and the sub-modules include a control temporary block, a main control port, a lens control block, a shutter control unit, and a flash control block. The Control Register block contains a register for the lens control, shutter control block, and flash control block. The main control block provides an interface between the CMI 202 and the camera 208. The mirror, shutter control, and flash control block are used as the focal shutter and flash controller for the camera module. The camera control block of the camera module interface is further described in Figure 3. The video front end block (VFE) 206 is located in the frame of the camera 208 through the parallel interface 216, stores the frames, and then transfers the frames to the MDDI host core 122 through the frame interface 2. As described above, communication between the MSM processor module interface 1 8 is accomplished through the MDDI link. Typically, commands from the MSM to the group interface are encapsulated at the MDDI client 106 at the MDDI package and decapsulated at the MDDI host 122. For example, commands from the camera module interface include MDDI host configuration commands, memory access commands, and camera control commands. The CMI 202 decodes the command received from the M SM according to the Command ID field in the header, and the ID also represents the scratchpad temporary host access block of the scratchpad block associated with the command. The block connector head control, reference receiver 18 will be temporarily commanded with the MSM machine in the camera module. Base address -15- (13) 1376114

Hey. Table 1 below shows the types of MSM commands received by the camera module interface - some command types: Command ID Description 0x00 mddi Host Device Configuration Command 0x40 Camera Interface Control Command 0x60 Lens Control Command 0x80 I2C Command 0x90 Shutter Control Command Ox A0 White LED Control Command OxBO Three-Wire Serial Interface Control Command OxCO PLL" Control Command OxDO-OxFF Reserved Command Table 1

Typically, the MSM command is 12-bit long and can include up to 7 bytes of the scratchpad address specified in the command to be written to the scratchpad. Tables 2 and 3 below show the contents of the shutter and flash control commands. As shown in Table 2, for example, the shutter control commands include a bit group for turning on/off the shutter, a speed for controlling the shutter, or a timing for controlling the timing of the shutter operation. Similarly, the flash control commands shown in Figure 3 include, for example, a byte used to control the intensity of the flash, the duration of the flash, or the number of pulses of the flash. In general, commands sent by the MSM processor do not require synchronization. However, some commands require precise synchronization at the camera, as described in • 16-(14) 1376114. Number of Name Bits Description Bytes 〇TID 8 Transaction ID specified by MSM Byte 1 Count 8 Total number of bytes in this message Byte 2 Command ID 8 Mechanical shutter command ID bit Group 3 read/write/status byte 8-bit 0-read/write, 0 write, 1 read bit 1 -Ack Req ' 0 no-req, 1 req bit 2_ Ack state, 0 no pass/error, 1 Pass/Success Bits 3-7-Reserved Bytes 4 Shutter VSYNC Count 8 8 Bytes, Number of VSYNCs before the Shutter Open Command is Executed 5 Shutter Speed _ High 8 Shutter Speed, High Bytes Byte 6 Shutter speed is low 8 Shutter speed, low byte byte 7 Shutter On/Off 1 〇 - Shutter open 1 - Shutter closed byte 8-11 Reserved 8 Table 2 - Shutter Control Command -17- ( 15) 1376114 Number of Name Bits Description Bytes 〇TID 8 Transaction ID Bytes Specified by MSM] Count 8 Total Number of Bytes in This Message Byte 2 Command ID 8 White LED Control Command ID Byte 3 Read/Write/Status Bytes 8-bit 0-read/write: 0 write, 1 read bit 1-Ack Req : 0 no-r Eq,l req Bit 2 - Ack state: 0 no pass/error, 1 pass/success bit 3-7-retain white LED intensity 8 0x00: 20mA 0x01: 40mA 0x02: 60mA 0x03: 80mA 0x04: 100mA 0x09: 200mA OxOE: 300mA 0x13: 400mA 0x18: 500mA 0xl9-0xFF Reserved byte 4 Red_eye_lower_mode-pulse 8 Red-eye-reduced pulse number before full discharge pulse. For fully discharged pulse waves, this parameter should be set to 0x01. Byte 5 Pulse time period 8 Flash/flash control pulse HCLK unit time period Byte 6 White LED time period 8 0x00·· No change; LED status does not change. 0x01: LED is on for 1 frame time. OxFF: LED is on for 256 frames. Time byte 7 Red_eye_Reducing pulse interval 8 Red_eye_Reducing the interval between pulse waves, HCLK unit byte 8 white light UED bright 8 0x00: white LED off 0x01 = white LED on 0x02 = flash / flash control fully discharged 0x04 = flash / flash red-eye reduction byte 9-11 Reserved 8 Table 3 - White LED / Flash Control Command -18- ( 16) (16) 1376114 Communication from camera module interface to camera module As mentioned above, the camera module interface is used as the interface between the MSM processor and the camera module. The CIM 202 component of the camera module interface interprets the instructions received from the MSM and executes these commands by writing/reading a specific control register in the camera module interface. Figure 3 is a block diagram highlighting the interconnection between the camera module interface Π 8 and the camera module. In Fig. 3, the camera control block 2〇4 of Fig. 4 is exemplified by some of its individual components - lens control, flash control, and main control connection blocks 3 02, 3 04 and 3 1 4 . Other components of camera control block 204 have been omitted. The lens control block 322 is used to control the zoom, focus, and shutter control mechanisms of the camera. For example, lens control block 302 provides a set of enable signals to an external motor driver to move the lens and open/close the shutter. Alternatively, a separate shutter control block can be implemented with a separate shutter control drive. The lens and shutter control block respond to the corresponding control of the CCB 204. Table 4 below illustrates the lens control register associated with controlling the shutter of the camera. Typically, a mechanical shutter drive should return to the buffer of the scratchpad. For example, as shown in Figure 4, the 8-bit scratchpad at position 0x90 controls the particular time when the shutter open command is executed, and the 8-bit register at position Ox 93 controls whether the shutter should be opened or closed. Flash control block 304 is used to control the white LED/flash of the camera. As shown in Figure 3, flash control block 304 communicates with driver 306 to control the LED or xenon tube 3 08. Typically, flash control -19-(17) (17) 1376114 block 3 04 provides a set of enable signals to driver 306 to control the flash operation. Similar to the shutter control block, the flash control block responds to the settings of the flash control register relative to it. Table 5 below illustrates a register associated with controlling the flash of the camera. For example, the flash control register includes a flash current intensity, a flash duration, or a pulse interval between pulses in the red-eye reduction flash mode.

Lens Control Register Description Bit Field 0x90 Shutter "Wait" period 8-bit 値, number of VSYNC pulses before the shutter open command is executed 0x91 Shutter speed - high byte 8-bit 0x92 shutter speed - low bit Group 8 bit,] ms grained 0x93 Shutter open/close 〇 = Shutter open 1 = Shutter closed Table 4 - Shutter control register -20 (18) 1376114 White LED control register Description Bit field OxAO Current Intensity 8-bit 00h=20mA 01h=40mA 14h=400mA 151>2?11=^Leave OxAl Red_Eye_Low J Mo-type_Pulse wave 8-bit red before the full discharge pulse wave_Eye_reduced pulse wave The number of fully discharged pulse waves, this parameter should be recognized as 0x0] 0xA2 pulse time period 8-bit flash / ΡΘ control pulse wave HCLK unit time period 0xA3 white _LED_ pulse wave _ time period 8 bits The time period of the video frame unit of the fully-discharge pulse wave OOh-Ι box 02h-FFh=increment of the frame time of the 256 frame is 0xA4 red_eye_reducing the pulse interval 8-bit red_eye_reducing the pulse wave Interval, HCLK unit 0xA5 LED on/off register 8 bits 〇〇h=white LED 〇Π = = white LED bright 02h = flash / flash control - full discharge 〇 4h = flash / flash control - red _ eye _ lower table 5 - flash control register - 21 - (19) (19) 1376114 main control The connection block 3 1 0 provides access to the scratchpad of the camera 20 8 . The main control connection block 3 1 0 converts the control data designed for the camera into a 12 C protocol (used by most CMOS and CCD camera modules) or a three-wire serial array used by some CCD sensors. Interface Protocol ^ Typically, the main control interface block 310 reads the sputum that is to be sent to the camera from the corresponding I2C or three-wire control register. Note that Figure 3 also illustrates a set of SYNC signals 312 « SYNC signals 312 from camera 208 to camera interface block 206 that are typically associated with certain events at the camera and can be used as timing signals to enable camera mode The group interface 1 18 is synchronized with the camera module 208. Synchronous execution of instructions on MDDI As mentioned above, some MSM commands require precise synchronization at the camera module interface. However, since the delays via the MDDI link cannot be accurately predicted or predicted, it is not possible to schedule commands at the MSM for accurate synchronization in such a way that they are executed synchronously at the camera module. Therefore, command synchronization needs to be done at the camera module. Thus, a control mechanism is required at the camera module to provide simultaneous execution of two or more camera commands. A method and system for simultaneously executing commands on a communication link will now be provided. Note that in many aspects, while using specific MDDI and/or Pathfinder examples to introduce some of these methods and systems, these methods and systems can be extended to more general contexts, as can be learned by this technique. According to the teachings here. Therefore, the method and system of the present invention are not limited to the synchronization command on the MDDI link, nor are they limited to the context of controlling the camera's baseband processor via the camera module interface. . 4 is a flow diagram 400 of an example of a method of synchronously executing a command over a communication link. Flowchart 400 begins at step 410 by generating a plurality of commands at the first module by the first processor. For example, referring to FIG. 1, step 410 can be accomplished by the baseband MSM processor 104 generating a plurality of camera control commands. Step 420 includes transmitting a plurality of commands from the first module to the second module over the communication link. For example, referring to FIG. 1, step 40 can be accomplished by transmitting a camera control command to the camera module interface 118 via the MDDI link 1 by the baseband MSM processor 104. Note that the commands are transmitted at random times that are typically independent of one another. Step 430 includes receiving commands at the second module and writing the commands to the registers associated with the commands. For example, referring to FIG. 2, step 430 is accomplished by the camera module interface 1 1 8 receiving commands from the MSM 104 and writing the commands to a particular control register of the camera module corresponding to the received command. Step 440 includes scheduling execution of the command at the second module by associating execution of the command at the second module with a separate event at the second module. For example, the command received from the MS processor at camera module interface 1 1 8 is scheduled to be executed when a particular event occurs at the camera module interface. This event is independent of any command that is scheduled for execution. For example, as shown in FIG. 3, an event may be indicated by one of the SYNC signals of SYNC signal 312 received from camera 208 by -23-(21)(21)1376114. Thus, one or more of the commands scheduled for execution can be delayed at the second module. Step 450 includes executing a command when an independent event is detected at the second module. For example, an independent event can be detected via an interrupt triggered when an independent event occurs. Note that a plurality of commands are executed synchronously because their execution time has been associated with the same event. Therefore, the precise simultaneous execution of a plurality of commands can be achieved on the communication link. Note that the method described in Figure 4 is generally applicable to any application requiring precise simultaneous execution of multiple commands over a communication link. Clearly speaking - this method can be applied to the camera module interface communication in the context of MS ,, as will be further described below. For example, the method can be used to synchronize the execution of camera commands generated by the MSM at the camera module interface. These commands may include commands related to flash synchronization, such as, for example, flash and shutter commands. A method and system for specifically applying the method of Figure 4 to the communication between the MSM and the camera module interface will now be provided. For purposes of illustration only, and should not be limited to this particular example, such methods and systems will be described in the context of flash sync (shutter and flash sync) as can be learned by those skilled in the art. Known. The camera module interface includes built-in mechanisms and signals that allow the method of Figure 4 to be implemented in a very flexible manner. These mechanisms and signals will now be described in more detail. A method of using these mechanisms and signals to achieve simultaneous execution of multiple commands in the camera module interface will then be provided. - 24 ** (22) (22) 1376114—Available mechanisms include EPOCH (episode reference time relative to the system) interrupts that can be enabled using the camera interface box of the camera module interface. The EPOCH interrupt can be scheduled to trigger the execution of commands received by the camera message interpretation block of the camera module interface. Thus, an EPOCH interrupt can be associated with multiple MSM commands to simultaneously trigger the execution of these commands. In addition, the EPOCH interrupt can be programmed to trigger the execution of the M SM command based on a particular signal within the camera module interface. For example, an EPOCH interrupt can trigger the execution of an MS 当 command when a particular chirp is received on the SYNC signal received from the camera. The S.YNC signal shown in Figure 3 can include a camera frame buffer timing signal, such as a line or frame sync signal. A line sync signal, such as HSYNC, indicates the beginning of the data line in the frame buffer. The frame sync signal, VSYNC, indicates the start of a new frame in the frame buffer. Therefore, in the frame buffer, the MSM commands can be designed to be synchronized for a specific time. In the example of flash sync, this allows both a framed exposure sensor or a scroll shutter type sensor. In other words, flash sync can be done in one or more complete boxes, or on some lines of only the box. The MSM command additionally includes built-in features that allow for very flexible execution scheduling. For example, some M SM commands include a programmable field of desired execution time that can be programmed to occur during a particular time period after the occurrence of certain events within the camera module interface. For example, the shutter control commands shown in Table 2 include a programmable field (byte 4) indicating the number of VS YN C pulses, and the VSYNC pulse needs to disappear (23) 1376114 ^ Camera Module The time between the time the command was received and the time the command was executed. Similar programmable fields can be found in other MSM commands to allow for very flexible scheduling of these instructions. Therefore, using the built-in mechanism and signal of the camera module interface, the time schedule of multiple MSM commands can be scheduled at the camera to execute synchronously. FIG. 5 illustrates the use of the camera module interface to simultaneously execute multiple MSMs. A flowchart of the method of the command. For purposes of illustration only, the method of FIG. 5 is described in the context of flash and φ steps, but should not be limited to this particular example, as is apparent to those skilled in the art in light of the teachings herein. 0 0 begins at step 510, which includes transmitting a shutter control command from the processor to the camera controller over the communication link. For example, referring to FIG. 2, step 510 can be completed by the MSM processor transmitting a shutter open command to the camera module interface 1] 8 on the MDDI communication link 110. The shutter open command includes the desired execution time as indicated by the V S YNC . pulse wave that needs to pass before the command is executed. #步520 includes transmitting a flash control command from the processor to the camera controller over the communication link. For example, referring to FIG. 2, step 520 can be accomplished by the MS 处理器 processor transmitting a white LED command to the camera module interface 118 on the MDDI link 110. The white LED command can include information about the flash duration and operating mode (flare mode or flash mode), as shown in Figure 3. Depending on the mode of operation, the command will be enabled for many frames or will be more closely coupled to the camera sensor. Step 53 includes associating the shutter and flash control commands with the first and second interrupts, wherein the 'first and second interrupts are synchronized to a common timing -26-(24) (24) 1376114 signal. For example, referring to FIG. 3, the shutter and flash control commands received by camera module interface 可以 8 can be associated with an EPOCH interrupt at camera interface block 206. When received from SYNC signal 312! For a particular pulse, for example, a line sync HSYNC and/or a frame sync VSYNC pulse, the EPOCH interrupt can be further programmed to cause the shutter and flash control commands to be executed. Step 540 includes triggering the first and second interrupts upon detecting a common timing signal, thereby causing the shutter to execute in synchronization with the flash control command. For example, when a frame (VSYNC) signal is received at the camera module interface, an EPOCH interrupt associated with the shutter and the flash control command can be triggered to cause the shutter to execute concurrently with the flash command. In a broader perspective, the method of Figure 5 can be used to synchronize any number of camera control commands generated by the MS and signals received from the camera. The sequential execution of commands in accordance with a particular timing schedule can also be achieved using methods and systems that are substantially similar to those described above. Figure 6 illustrates an example of flash synchronization. More specifically, Figure 6 shows an example synchronization between a scroll shutter and a white LED/flash. In the example of Figure 6, 'desired flash illumination occurs at a particular time instant when all of the lines of the frame are integrated. This can be, for example, a case where a frame exposure type sensor is applied. The vertical axis on the left side of Fig. 6 shows the line of the frame in bold with the brackets in bold, which shows the desired integration time. On the right, the vertical signal shows the frame sync signal VSYNC, which indicates the beginning or end of the frame. Note that not all in the scroll shutter type sensor

-27- (25) 1376114 The frame line needs to be integrated at the moment of using the flash. For example, only a few lines of the frame can be exposed at the same time, and the camera establishes a program by reading the most exposed line, starting exposure at the next unexposed line, and repeating the program on the next most exposed line. frame. When each fully exposed line is read, another line is added to the set of columns that have been integrated. Conclusion While the various embodiments of the present invention have been described in the foregoing, it should be understood that Various changes in form and detail may be made by those skilled in the art without departing from the spirit and scope of the invention. Therefore, the breadth and scope of the present invention should not be construed as being limited to any of the above-described representative embodiments. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of the specification, are intended to provide a further explanation of the principles of the invention and The invention can be made and used. Figure 1 illustrates a block diagram of an example environment using an action display digital interface (M D D I ). Figure 1 is a block diagram of a digital data device interface coupled to a digital device and peripheral devices. 2 is a block diagram of an MDDI link interconnection according to an example of using the camera module interface of FIG. 1.

-28- (26) 1376114 — Figure 3 is a block diagram showing the interconnection between the camera module interface and the camera module. Fig. 4 is a flow chart showing a method of synchronously executing a command on a communication link. Figure 5 is a flow chart showing a method of performing simultaneous execution of a shutter and a flash command in a camera controlled by a communication link. Figure 6 illustrates an example of flash synchronization. φ The present invention will be described with reference to the accompanying figures. The figure in which the component first appears is shown by the leftmost digit of the corresponding reference numeral. [Main component symbol description] 100: Digital data device interface 102: Lower cover part 104: Mobile station data machine (MSM) baseband chip • 106: MDDI (Mobile Display Digital Interface) client controller 108: MDDI host controller 1 1 0 : message interpretation module 1 1 2 : MDDI link 1 14 : upper cover part 1 16 : liquid crystal display (LCD) module I 1 8 : camera module interface 1 2 0 : content module 122 : MDDI Host Controller -29- (27) 1376114 — 1 3 Ο : Control Module ' 1 4 Ο : Link Controller 1 5 0 : Digital Device 6 0 : System Controller • 1 7 0 : Link Controller 180 : Peripheral device 1 90: Control block φ 200: MDDI link interconnect 202: Camera message interpreter 2 04: Camera control block 206: Image front end block 208: Camera module 210: Scratch access message interface 2 I 2: Configuration interface 2 1 4 : Configuration interface φ 2 1 6 : Parallel interface 2 1 8 : Frame interface 3 0 2 : Main control connection 埠 block (lens control block) 3 0 4 : Main control connection 埠 block (flash Control block) 3 0 6 : Drive ' 3 0 8: Light-emitting diode or xenon tube 3 1 0 : Main control connection 埠 3 3 2 2 : SY NC signal -30-

Claims (1)

1376114 No. 094141291 Special Application Form Chinese t Please replace the patent scope (February 1st, 2011) X. Patent application scope 1. A method for synchronous execution is generated by a first module and executed in a second The method of the plurality of commands at the module, wherein the first module and the second module communicate via a communication link, the method comprising: (a) at the first module by a first processor Generating a plurality of commands » (b) transmitting the plurality of commands from the first module to the second module over the communication link; (c) receiving the commands in the second module, and writing To a register associated with the commands: (d) at the second module by associating execution of the commands with an independent event to schedule the commands at the second group d Execution: and (e) execute the commands when the independent event is detected. 2. The method of claim 1, wherein the communication link represents an action display digital interface (MDDI) link. 3. The method of claim 2, wherein the first module represents a baseband processor and the second module represents a camera module interface. 4. The method of claim 1 is as follows. Wherein the commands are transmitted via the communication link at random times independent of each other. 5. The method of claim 1, wherein the one or more commands of the commands are delayed at the second module prior to execution. 6. The method of claim 1, wherein step (d) comprises causing execution of the commands and an interruption indicating the occurrence of the independent event 123443-1010220.doc 1376114 far year &gt;month&gt; The replacement page is associated. 7. The method of claim 6, wherein the command comprises controlling a shutter control command of a camera and a flash control command, 8. The method of claim 7, wherein the shutter and the The flash control command is executed at a time relative to a timing signal associated with the camera. 9. The method of claim 8, wherein the timing signal represents a frame synchronization signal of a frame buffer associated with the camera. 10. The method of claim 8, wherein the timing signal represents a line sync signal associated with the frame buffer of the camera. 11. A method for performing simultaneous execution of a shutter and a flash command in a camera, wherein the camera is controlled by a processor via a communication link, the method comprising: (a) transmitting the communication Linking a shutter control command from the processor to a camera controller associated with the camera; (b) transmitting a flash control command from the processor to the camera controller via the communication link; Causing the shutter and flash control command at the camera controller with the first and second interrupts, wherein the first and second interrupts are synchronized at the camera controller to a common timing signal; and d) triggering the first and second interrupts when the common timing signal is detected, thereby causing the shutter to be executed in synchronization with the flash control command. 12. The method of claim 11, wherein the communication link represents a Mobile Display Digital Interface (MDDI) link. I23443-I010220.doc 1376114 代年&gt; 替换正换页- I3. The method of claim </ RTI> wherein the processor represents a mobile station data processor (MSM) baseband processor and the camera controls The device represents a Pathfir^: 彳I _ controller. 1. The method of claim 11, wherein the shutter and flash control commands are transmitted at different times via the communication link and wherein the times are independent of each other . The method of claim 2, wherein the shutter control command represents a shutter open command and the flash control command represents a flash illumination command. The method of claim 15, wherein the shutter opening and the flash illumination command are performed synchronously with respect to the timing signal. 17. The method of claim 15, wherein the timing signal represents a frame sync signal of a frame buffer associated with the camera. 18. The method of claim 15, wherein the timing signal generation represents a line sync signal of a frame buffer associated with the camera. The method of claim 17, wherein the shutter The box sync signal with the flash illumination command relative to the frame buffer is turned on to enable full frame exposure of the camera sensor. &quot; 20. The method of claim 18, wherein the shutter is opened and the flash illumination command is performed with respect to the line sync signal of the frame buffer to enable scrolling shutter exposure of the camera sensor . 123443-1010220.doc