All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>,
	Mark Hounschell <dmarkh@cfl.rr.com>
Subject: Re: tty  TTY_HUPPED anomaly
Date: Wed, 04 Jan 2012 10:59:35 -0500	[thread overview]
Message-ID: <4F047767.5060708@compro.net> (raw)
In-Reply-To: <20111223204015.541924f2@pyx>

On 12/23/2011 03:40 PM, Alan Cox wrote:
>
>> I turned the TTY_DEBUG_HANGUP and added some additional printks. You see
>> below the first port works just fine but the second fails because
>> something is calling the tty_hangup function around 70usecs after I open
>> the device???
>> What and Why???
>
> The driver will be - and because the carrier dropped and the HUPCL flag
> is set on the port.
>

Thanks Alan,

But what has carrier dropping got to do with an TIOCSETD ioctl. For that 
matter, any operation other than an actual read or write to the port? 
This seems wrong. You've obviously looked at my code being executed. 
What can be done to prevent tty_hangup from being called after opening 
the port? And if this is really supposed to happen, why does it not 
always happen?

Even if the first thing I do after opening the port is to clear HUPCL 
and set CLOCAL, this still randomly happens the first time I open the 
port after booting.

Thanks again for your help
Mark




  reply	other threads:[~2012-01-04 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 14:51 tty TTY_HUPPED anomaly Mark Hounschell
2011-12-23 18:46 ` Mark Hounschell
2011-12-23 20:40   ` Alan Cox
2012-01-04 15:59     ` Mark Hounschell [this message]
2012-01-04 16:27       ` Alan Cox
2012-01-04 18:59         ` Mark Hounschell
2012-01-04 20:28           ` Jiri Slaby
2012-01-04 20:35             ` Mark Hounschell
2012-01-04 20:40               ` Jiri Slaby
2012-01-04 20:50                 ` Mark Hounschell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F047767.5060708@compro.net \
    --to=markh@compro.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dmarkh@cfl.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.