|
From: sonicz <no...@do...> - 2013-12-04 02:48:40
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c&rev=1363228968 Edit Summary: [Linux APP] @@ -1293,10 +1293,9 @@ ===== A Simple Example ===== This example is based on network layer communication APIs defined for bo th Linux application and the bare metal DSP application. ==== Linux APP ==== - simple packet sample packet.c at: - [[http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=b rowse&path=%2Ftrunk%2Fuser%2Fblkfin-apps%2Ficc_utils%2Fexample%2Ftest_ap p%2Fpacket.c&view=markup&revision=10273]] + [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/task/task1.c| A simple packet sample]] ==== DSP Side Bare Metal Application==== dsp side sample task1.c at: [[http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=b rowse&path=%2Ftrunk%2Fuser%2Fblkfin-apps%2Ficc_utils%2Fexample%2Ftask%2F task1.c&view=markup&revision=10173]] |
|
From: sonicz <no...@do...> - 2013-12-04 02:50:44
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c&rev=1386125312 Edit Summary: [Linux APP] @@ -1293,9 +1293,9 @@ ===== A Simple Example ===== This example is based on network layer communication APIs defined for bo th Linux application and the bare metal DSP application. ==== Linux APP ==== - [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/task/task1.c| A simple packet sample]] + [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/test_app/packe t.c| A simple packet sample]] ==== DSP Side Bare Metal Application==== dsp side sample task1.c at: [[http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=b rowse&path=%2Ftrunk%2Fuser%2Fblkfin-apps%2Ficc_utils%2Fexample%2Ftask%2F task1.c&view=markup&revision=10173]] |
|
From: sonicz <no...@do...> - 2013-12-04 02:52:16
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c&rev=1386125507 Edit Summary: [Core 1 Bare Metal Application] @@ -1295,9 +1295,9 @@ ==== Linux APP ==== [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/test_app/packe t.c| A simple packet sample]] ==== Core 1 Bare Metal Application==== - [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/task/task1.c| Core 1 bare metal sample] + [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/task/task1.c| Core 1 bare metal sample]] ==== Link the DSP application ==== The bare metal application should be linked with the dsp bridge library in order to interact with linux application properly. The offset address o f entry main() can be discovered by dsp bridge kernel moduel when loading. |
|
From: steven.miao <no...@do...> - 2016-07-01 03:29:55
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1386125529 Edit Summary: [Dispatch packet] @@ -1389,8 +1389,34 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== + + **icc session layer manage the user space packet send/recv session** + + the sm_session data structure: + + <code> + struct sm_session { + struct list_head rx_messages; /*rx queue sm message*/ + struct list_head tx_messages; + uint32_t n_avail; + uint32_t n_uncompleted; + uint32_t local_ep; + uint32_t remote_ep; /*remote ep*/ + uint32_t type; + pid_t pid; + uint32_t flags; + int (*handle)(struct sm_message *msg, struct sm_session *session); + struct sm_proto *proto_ops; + uint32_t queue_priority; + wait_queue_head_t rx_wait; + } __attribute__((__aligned__(4))); + </code> + + + **message_queue_thread** + **On core running Linux** * To send a packet in application , the packet buffer should be allocated in user space first. Its pointer then is passed to the kernel system call. Kernel code also allocates a buffer in kernel space and copies the user data in. After that, the dsp bridge driver appends a packet ready message with packet address and length to the shared message queue in L2 memory and link the packet buffer to the sent list. |
|
From: steven.miao <no...@do...> - 2016-07-01 03:51:57
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1467344484 Edit Summary: [Dispatch packet] @@ -1390,8 +1390,9 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== + {{:protocols:icc_layer1.png|}} **icc session layer manage the user space packet send/recv session** the sm_session data structure: @@ -1413,11 +1414,14 @@ wait_queue_head_t rx_wait; } __attribute__((__aligned__(4))); </code> + if the icc queue is full, packet send will be blocked on icc queue tx_wait wait queue until the tx queue is not full. - **message_queue_thread** + packet receive will blocked on session's rx_wait queue if there's no available message, until the ipi wait up the icc queue thread to hanle incoming message, receive the message to packet and wakeup the packet recv process sleeping on rx_wait queue. + **message_queue_thread** + kernel thread to handle incoming msg, the remote ipi will wakeup this thread. **On core running Linux** * To send a packet in application , the packet buffer should be allocated in user space first. Its pointer then is passed to the kernel system call. Kernel code also allocates a buffer in kernel space and copies the user data in. After that, the dsp bridge driver appends a packet ready message with packet address and length to the shared message queue in L2 memory and link the packet buffer to the sent list. |
|
From: sonicz <no...@do...> - 2013-12-04 02:51:55
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:ic c&rev=1386125437 Edit Summary: [DSP Side Bare Metal Application] @@ -1294,12 +1294,11 @@ This example is based on network layer communication APIs defined for bo th Linux application and the bare metal DSP application. ==== Linux APP ==== [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/test_app/packe t.c| A simple packet sample]] - ==== DSP Side Bare Metal Application==== - dsp side sample task1.c at: + ==== Core 1 Bare Metal Application==== + [[sfp>openapp/code/HEAD/tree/trunk/apps/icc_utils/example/task/task1.c| Core 1 bare metal sample] - [[http://blackfin.uclinux.org/gf/project/uclinux-dist/scmsvn/?action=b rowse&path=%2Ftrunk%2Fuser%2Fblkfin-apps%2Ficc_utils%2Fexample%2Ftask%2F task1.c&view=markup&revision=10173]] ==== Link the DSP application ==== The bare metal application should be linked with the dsp bridge library in order to interact with linux application properly. The offset address o f entry main() can be discovered by dsp bridge kernel moduel when loading. |
|
From: steven.miao <no...@do...> - 2016-07-01 03:29:35
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1467342757 Edit Summary: [Dispatch packet] @@ -1389,8 +1389,10 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== + + {{:protocols:icc_layer.png|}} **icc session layer manage the user space packet send/recv session** the sm_session data structure: |
|
From: steven.miao <no...@do...> - 2016-07-01 03:41:31
|
New Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc Old Revision: https://docs.blackfin.uclinux.org/doku.php?id=protocols:icc&rev=1467343769 Edit Summary: [Dispatch packet] @@ -1390,9 +1390,8 @@ Bare metal application is loaded by user space loader into core B memory space. The main and disatch entries in application and its dsp_bridge library are figured out by the loader. The loader informs the dsp_driver of these entry address. ==== Dispatch packet ==== - {{:protocols:icc_layer.png|}} **icc session layer manage the user space packet send/recv session** the sm_session data structure: |
