public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alan Cox <alan@linux.intel.com>,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, qi.wang@intel.com,
	yong.y.wang@intel.com, joel.clark@intel.com,
	kok.howg.ewe@intel.com
Subject: Re: [PATCH 2/2] pch_uart: Delete modem status interrupt enable code
Date: Thu, 10 Nov 2011 11:11:22 +0900	[thread overview]
Message-ID: <4EBB32CA.5020206@dsn.lapis-semi.com> (raw)
In-Reply-To: <20111102110055.153d06c6@lxorguk.ukuu.org.uk>

Hi Alan,

(2011/11/02 20:00), Alan Cox wrote:
>> Called ".get_mctrl" function, other software can know incoming carrier
>> detection.
>> Or you mean a uart driver must detect incoming carrier with interrupt ?
>
> If a user opens a tty port which has no carrier signal then the open is
> supposed to block until the carrier is raised unless either clocal
> termios or O_NDELAY open flags are set.
>
> That usually means you need to take the carrier raise interrupt in order
> to wake out of open in this case.
>

I understand.
We need to add modem status interrupt processing.

Thanks,
-- 
tomoya
ROHM Co., Ltd.

  reply	other threads:[~2011-11-10  2:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27  6:45 [PATCH 1/2] pch_uart: Fix hw-flow control issue Tomoya MORINAGA
2011-10-27  6:45 ` [PATCH 2/2] pch_uart: Delete modem status interrupt enable code Tomoya MORINAGA
2011-11-01 12:57   ` Alan Cox
2011-11-02  5:52     ` Tomoya MORINAGA
2011-11-02 11:00       ` Alan Cox
2011-11-10  2:11         ` Tomoya MORINAGA [this message]
2011-11-01 12:55 ` [PATCH 1/2] pch_uart: Fix hw-flow control issue Alan Cox

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=4EBB32CA.5020206@dsn.lapis-semi.com \
    --to=tomoya-linux@dsn.lapis-semi.com \
    --cc=alan@linux.intel.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=joel.clark@intel.com \
    --cc=kok.howg.ewe@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=qi.wang@intel.com \
    --cc=yong.y.wang@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox