Changeset 539 for trunk/kernel/devices

Timestamp:

Sep 21, 2018, 10:21:42 PM (6 years ago)

Author:

nicolas.van.phan@…

Message:

TTY MUX 4 : Multiplex TTY character sending

Now, when a thread wants to write to a tty,
when the dev_txt_write() or dev_txt_sync_write() are called,
they all call soclib_mtty_aux() with a channel number.
The soclib_mtty_aux() function will write the string char by char,
with each char preceded by the channel number, so that the receiving end
knows to which tty a character is addressed to.

N.B. dev_txt_write() makes *synchronous* writes for the moment
because unlike the vci_tty_tsar, the vci_multi_tty doesn't raise
interrupt except when a new char is received, so we can't use the
interrupt mechanism for writes.

N.B. Now, the TTY DEV threads all write to the same register (WRITE),
but when a thread sends a 2-byte (tty dest. nb. + char), the two must be
send consecutively, without another thread sending a byte in between.
Consequently, a lock has been added to guarantee this atomicity.

Location:

trunk/kernel/devices

Files:

• dev_txt.c (modified) (2 diffs)
• dev_txt.h (modified) (1 diff)

trunk/kernel/devices/dev_txt.c

@@ -173 +173 @@
 #endif
 
+    // get extended pointer on TXT[0] chdev
+    xptr_t dev_xp = chdev_dir.txt_tx[0];
+
+    assert( (dev_xp != XPTR_NULL) , __FUNCTION__ ,
+    "undefined TXT0 chdev descriptor" );
+
+    // get TXTO chdev cluster and local pointer
+    cxy_t    dev_cxy  = GET_CXY( dev_xp );
+    chdev_t * dev_ptr = (chdev_t *)GET_PTR( dev_xp );
+
+    // If we use MTTYs (vci_multi_tty), we perform only sync writes
+    if( dev_ptr->impl == IMPL_TXT_MTY )
+    {
+        // get driver command function
+        dev_aux_t * aux = (dev_aux_t *)hal_remote_lpt( XPTR( dev_cxy , &dev_ptr->aux ) );
+
+        // build arguments structure
+        txt_sync_args_t  args;
+        args.dev_xp = dev_xp;
+        args.buffer = buffer;
+        args.count  = count;
+        args.channel = channel;
+
+        // call driver function
+        aux( &args );
+
+        return 0;
+    }
+
+    // Otherwise, we use vci_tty_tsar so we can use async writes
+    else
+    {
     return dev_txt_access( TXT_WRITE , channel , buffer , count );
+    }
 
 #if DEBUG_DEV_TXT_TX
@@ -238 +271 @@
     args.buffer = buffer;
     args.count  = count;
+    args.channel = 0;
 
     // call driver function

trunk/kernel/devices/dev_txt.h

@@ -106 +106 @@
     char      * buffer;    /*! local pointer on characters array                         */
     uint32_t    count;     /*! number of characters in buffer                            */
+    uint32_t    channel;   /*! channel, aka which tty to write to                        */
 }
 txt_sync_args_t;