JPH0991157A - Task-device driver communication control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To surely perform communication between the plural tasks of the equal priority and a device driver at high speed. SOLUTION: The 1st task investigates the state of a 2nd task occupation flag 2 by turning on a 1st task occupation flag 1 and when the 2nd task occupation flag 2 is turned on, control authority is applied to the other task by turning off the 1st task occupation flag. When the 2nd task occupation flag is turned off, the 1st task writes data in a data table and updates a task write pointer. When all the data are completely written in the data table, the 1st task occupation flag 1 is turned off, and the control authority of its own central processing unit is abandoned. A DSP driver reads data from a transmission data table until the contents of the write pointer get equal with the contents of a read pointer.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a task-device driver communication control method for controlling communication between a device driver and a plurality of tasks having the same priority, and can be applied to, for example, a call processing module in a mobile phone. It is a thing.

[0002]

2. Description of the Related Art In recent years, in a wireless terminal such as a mobile phone, a digital signal processor (referred to as DSP in the following description) is used for digital processing of voice and the like in order to improve the processing capacity and downsizing of the terminal. , DSP is appropriately accessed from a predetermined call control task according to the call processing stage.

Conventionally, in a parallel processing system such as a mobile phone, a call control task (application task) is a DSP.
The following processing was performed when transmitting data to the driver (device driver). Here, the task means a parallel processing unit that is a scheduling target of the central processing unit, and generally, a task, a thread,
This is called a process. A device driver is a program for controlling peripheral devices in response to input / output requests issued by application tasks.It is composed of data and subroutines, constitutes an interface between application tasks and peripheral devices, and is a peripheral device. Is a task or handler that receives an interrupt request due to the occurrence of the event and calls an interrupt handler to perform processing.

When the first call control task is executing and the second call control task is waiting for the assignment of the control right of the central processing unit, the first call control task sends data to the DSP driver. Try to send. However, both call control tasks have the same priority.

At this time, the first call control task suspends the operation of the second call control task by raising its own priority. The first call control task with the higher priority sends the data to the DSP driver using mail. Here, mail is a data transmission / reception method between tasks in which transmission data from an arbitrary task is registered in a queue, and the arbitrary task receives data from this queue.

When the data transmission to the DSP driver is completed, the first call control task relinquishes the control right of the central processing unit, so that the second call control task acquires the control right of the central processing unit. , Resume processing.

[0007]

As described above, data is exchanged between tasks using mail even in a call processing farm that is conventionally required for high-speed processing of mobile phones. Since the transmission also considered the data transmission from the tasks with different priorities, the processing became complicated, and the data transmission speed between the application task and the device driver was greatly restricted. Furthermore, by increasing the priority of the task, the processing of other tasks is stopped or the processing speed is decreased, and the processing speed of the entire system is decreased.

Further, when data is transmitted from the application task to the device driver without increasing the priority of the application task, the transmission data may be rewritten by another application task.

The present invention has been made in consideration of the above points, and in a module that requires high-speed processing such as a call processing module of a mobile phone, a plurality of application tasks of the same priority and device drivers Task-device driver that exchanges data (especially, from multiple application tasks with the same priority to the device driver that needs to complete processing at high speed) at high speed and reliably at any time It is intended to provide an inter-communication control method.

[0010]

According to the present invention, there is provided a task for controlling communication between a device driver and a plurality of tasks of the same priority in a parallel processing system including a peripheral device and a device driver corresponding to the peripheral device. The inter-device driver communication control method is characterized by the following.

That is, a table for accumulating transmission data from a plurality of tasks of the same priority to the device driver and / or a plurality of tasks of the device driver to a plurality of tasks of the same priority is provided and the tasks of the plurality of tasks of the same priority are stored. The access request to the table is adjusted by the flag, the task that has acquired the access right writes the data to the table, and then the device driver reads the data from the table,
And / or the device driver writes data to the table and then the task that has acquired the access right reads from the table.

By providing a table for accumulating transmission data, data can be exchanged between a task and a device driver at high speed, and access requests to the table of a plurality of tasks of the same priority can be adjusted by a flag to make the same. In addition to controlling execution of data transmission requests from a plurality of priority tasks to the device driver, execution of a plurality of tasks of the same priority is controlled in data transmission from the device driver to a plurality of tasks of the same priority.

[0013]

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, an embodiment of a task-device driver communication method for transmitting / receiving data between a device driver and a plurality of tasks having the same priority according to the present invention will be described in detail with reference to the drawings. I will describe.

(First Embodiment) In the present embodiment, the present invention is applied to data transmission from a call control task to a DSP driver in a wireless mobile phone.

FIG. 2 shows a concept when the task-device driver communication method of the present embodiment is applied to a wireless mobile phone. The task monitoring program 25 determines the status of the tasks in the system when the running task ends, when the running task relinquishes the control right of a central processing unit (not shown), or when there is an interrupt request. , The control task of the central processing unit is given to the task having the highest priority, and the task is put into the execution state. Call control tasks 21 and 22 have the same priority,
The data is transmitted to the DSP driver 24. The DSP driver 24 receives data from the call control tasks 21 and 22 and controls the DSP. Interface table 2
As shown in FIG. 1, reference numeral 3 includes first and second task transmitting flags 1 and 2, a task write pointer 3, a DSP driver read pointer 4, and a transmission data table 5. The first and second task in-use flags 1 and 2 are in either ON or OFF states, respectively.

In this state, the first call control task 1
Will be described with reference to FIG. 3 when the CPU attempts to transmit data to the DSP driver 24.

The first call control task 21 turns on the first task busy flag 1 to check the state of the second task busy flag 2, and turns on the second task busy flag 2.
In this case, the first task transmitting flag 1 is turned off, the control right of the central processing unit is abandoned by itself, and the task monitoring program 25 gives the control right to other tasks. (Steps 301-304).

When the second task transmitting flag 2 is OFF, the first call control task 21 writes a certain amount of data in the transmission data table 5 and updates the task write pointer 3. Transmission data table 5 for all data
This operation is repeated until it is written in (step 305-
307).

When the first call control task 21 finishes writing all the data in the transmission data table 5, it turns off the first task busy flag 1 and relinquishes the control right of the central processing unit (step 308). ).

As described above, the processing execution of the call control tasks 21 and 22 is controlled by managing the states of the first and second task transmitting flags 1 and 2.

Next, the flow of processing when the DSP driver 24 reads out the data stored in the transmission data table 5 will be described with reference to FIG.

The DSP driver 24 reads a certain amount of data from the transmission data table 5 and the DSP driver read pointer 4 until the contents of the task write pointer 3 and the DSP driver read pointer 4 become equal.
Is repeated until the contents of both pointers 3 and 4 become equal (steps 401 to 40).
3).

By using the transmission data table 5 as described above, the call control task 2 can be executed without using mail.
Data is transmitted from 1 or 22 to the DSP driver 25.

The flow of processing when task dispatch occurs while the first call control task 21 is accessing the transmission data table 5 will be described with reference to FIG.

After the first call control task 21 turns on the first task busy flag 1, task dispatch occurs and the second call control task 22 starts its operation.
The second call control task 22 uses the second task busy flag 2
Is turned on and the state of the first task busy flag 1 is checked (steps 501 to 503).

Since the first task busy flag 1 is ON, the second call control task 22 turns off the second task busy flag 2 to relinquish the control right of the central processing unit. As a result, task dispatch occurs, and the first call control task 21 resumes operation (step 50).
4-506).

Further, before the first call control task 21 is accessing the transmission data table 5, a task dispatch occurs and the second call control task 22 starts its operation and completes the flag check again. The flow of processing when task dispatch occurs will be described with reference to FIG.

After the first call control task 21 turns on the first task busy flag 1, task dispatch occurs, the second task starts operating, and the second call control task 22 Turns on the second task busy flag 2 (steps 601, 602) Immediately after this, task dispatch occurs again and the first task starts operating. When the first call control task 21 finishes the transmission process and relinquishes the control right of the central processing unit, task dispatch is performed and the second call control task 22 starts the operation again. The second call control task 22 checks the first task busy flag 1 and performs subsequent processing (steps 603 to 607).

As described above, the task busy flags 1 and 2 are irrespective of the timing at which the task dispatch occurs.
Can be used to control the processing execution of the call control tasks 21 and 22.

Further, even if the second call control task 22 starts writing in the transmission data table 5 before the DSP driver 24 finishes reading the data written in the transmission data table 5 by the first call control task 21, , The second call control task 22 refers to the task write pointer 3
By writing its own transmission data after the data from the call control task 21, the data is not overwritten.

According to the first embodiment described above, when data is transmitted from the call control task to the DSP driver, the data is transmitted via the transmission data table and the task busy flag is used to execute the processing of the call control task. Since the adjustment is performed, high-speed and reliable data transmission can be performed.

(Second Embodiment) In the present embodiment, the present invention is applied to a call control task D in a wireless mobile phone.
This is applied to data reception from the SP driver.
The other parts than the interface table 4 are the same as those in the first embodiment, and the description thereof will be omitted.

As shown in FIG. 7, the interface table 4 in this embodiment comprises a reception task identification flag 71, a DSP driver write pointer 72, a task read pointer 73, and a reception data table 74. Further, two sets of interface tables 4 are prepared corresponding to the first and second call control tasks. The reception task identification flag 71 in one of the interface tables 4 corresponds to the first call control task and always has a value of "1". Similarly, the reception task identification flag in the other interface table 4 is also included. Reference numeral 71 corresponds to the second call control task and always has a value of "2".

The flow of processing when the DSP driver 24 attempts to transmit data to the first call control task 21 in such a state will be described with reference to FIG.

The DSP driver 24 performs the following processing on the interface table in which the reception task identification flag has a value of "1".

The DSP driver 24 writes a certain amount of transmission data in the reception data table 74 and the DSP.
The process of updating the driver write pointer 72 is repeated until all transmission data is written (steps 801 to 8).
03).

Next, a process in which the first call control task 21 reads the data written in the reception data table 74 in the above process will be described with reference to FIG.

The first call control task 21 performs the following processing on the interface table whose reception task identification flag has a value of "1".

The first call control task 21 has a DSP driver write pointer 72 and a task read pointer 73.
The reading of a certain amount of data from the reception data table 74 and the updating of the task read pointer 73 are repeated until the contents of the above are equal (steps 901 to 903).

As described above, the processing execution of the task can be controlled by the value of the reception task identification flag 71.

According to the second embodiment described above, the DSP
When receiving data from the driver, the data is received via the reception data table, and the access to the reception data table of the call control task is controlled using the task reception flag, so high-speed and reliable data reception can be performed. it can.

(Other Embodiments) In the first and second embodiments, tasks with the same priority (call control task)
Although the task-device driver communication method when the number of tasks is two has been described, the present invention can perform the same processing even when there are three or more tasks of the same priority.

In addition to the DSP driver of the present invention,
Serial (RS232C, RS422, etc.), parallel,
It can also be applied to interface device drivers such as GP-IB and PCMCIA.

Further, the present invention is applicable to a parallel processing system for exchanging data between a device driver and a plurality of tasks having the same priority, such as an electronic exchange and a facsimile, in addition to the wireless mobile phone. Applicable.

[0045]

As described above, according to the present invention,
When exchanging data between a device driver and multiple tasks of the same priority, a table for storing transmission data is provided and access requests to the table of multiple tasks of the same priority are adjusted by flags. Data can be exchanged between a plurality of tasks having the same priority and the device driver at high speed, reliably and easily, and the processing capability of the parallel processing system can be improved at low cost.

[Brief description of drawings]

FIG. 1 is a diagram showing an interface table according to a first embodiment.

FIG. 2 is a diagram showing a concept of the first embodiment.

FIG. 3 is a flowchart showing a data writing process according to the first embodiment.

FIG. 4 is a flowchart showing a data read process according to the first embodiment.

FIG. 5 is an explanatory diagram of an example 1 when a task dispatch is performed in the first embodiment.

FIG. 6 is an explanatory diagram of a second example when a task dispatch is performed in the first embodiment.

FIG. 7 is a diagram showing an interface table according to the second embodiment.

FIG. 8 is a flowchart showing a data write process according to the second embodiment.

FIG. 9 is a flowchart showing a data read process according to the second embodiment.

[Explanation of symbols]

 1, 2 task in-use flag 71 Reception task identification flag 5 Transmission data table 75 Reception data table 21, 22 tasks 24 DSP driver

Claims (1)

[Claims] 1. A task-device driver communication control method for controlling communication between a device driver and a plurality of tasks of the same priority in a parallel processing system comprising a peripheral device and a device driver corresponding to the peripheral device, A table that stores transmission data from multiple tasks with the same priority to the device driver and / or from the device driver to multiple tasks with the same priority is provided, and access requests to the table for multiple tasks with the same priority are issued. Adjusted by the flag, the task that has acquired the access right writes data to and / or reads data from the table, and the device driver reads data from the table and / or data to the table. Between the device driver communication control method - tasks and writes the.