lkml.org 
[lkml]   [2017]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Directly accessing serial ports from drivers w/o TTYs ?
    From
    Date
    On 26.06.2017 14:51, Alan Cox wrote:

    Hi,

    > You can write your own driver for the physical hardware and claim it in
    > your driver. Shouldn't normally be needed except for bizarre cases when a
    > serial link is used for something very non tty like (eg as GPIO lines).

    In my case, it's not really a serial link, but an backplane w/ FIFOs,
    which looks like a serial ports to the host (AFAIK, historically coming
    from older systems which actually had various serial controllers, eg.
    rs232, rs485/mvb, etc). The backplane seems to simulate the lower
    layers of an mvb network.

    > Otherwise all the low level tty device locking, queues and interfaces
    > assume there is a tty_struct attached to it, so yes you need a tty
    > struct.

    I was thinking about something that looks like serdev from consumer
    side, but instead directly works on struct uart_port, w/o actually
    allocating a tty (and also the funny things like signals, etc).

    > Why do you need to do otherwise ?

    Maybe it could offer better performance ?


    --mtx

    \
     
     \ /
      Last update: 2017-06-29 13:46    [W:9.088 / U:0.144 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site