diff options
| -rw-r--r-- | Documentation/sync_file.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/sync_file.txt b/Documentation/sync_file.txt index eaf8297dbca2..e8e2ebafe5fa 100644 --- a/Documentation/sync_file.txt +++ b/Documentation/sync_file.txt | |||
| @@ -6,8 +6,8 @@ | |||
| 6 | 6 | ||
| 7 | This document serves as a guide for device drivers writers on what the | 7 | This document serves as a guide for device drivers writers on what the |
| 8 | sync_file API is, and how drivers can support it. Sync file is the carrier of | 8 | sync_file API is, and how drivers can support it. Sync file is the carrier of |
| 9 | the fences(struct fence) that needs to synchronized between drivers or across | 9 | the fences(struct fence) that are needed to synchronize between drivers or |
| 10 | process boundaries. | 10 | across process boundaries. |
| 11 | 11 | ||
| 12 | The sync_file API is meant to be used to send and receive fence information | 12 | The sync_file API is meant to be used to send and receive fence information |
| 13 | to/from userspace. It enables userspace to do explicit fencing, where instead | 13 | to/from userspace. It enables userspace to do explicit fencing, where instead |
| @@ -32,7 +32,7 @@ in-fences and out-fences | |||
| 32 | Sync files can go either to or from userspace. When a sync_file is sent from | 32 | Sync files can go either to or from userspace. When a sync_file is sent from |
| 33 | the driver to userspace we call the fences it contains 'out-fences'. They are | 33 | the driver to userspace we call the fences it contains 'out-fences'. They are |
| 34 | related to a buffer that the driver is processing or is going to process, so | 34 | related to a buffer that the driver is processing or is going to process, so |
| 35 | the driver an create out-fence to be able to notify, through fence_signal(), | 35 | the driver creates an out-fence to be able to notify, through fence_signal(), |
| 36 | when it has finished using (or processing) that buffer. Out-fences are fences | 36 | when it has finished using (or processing) that buffer. Out-fences are fences |
| 37 | that the driver creates. | 37 | that the driver creates. |
| 38 | 38 | ||