From: Peter Hurley <peter@hurleysoftware.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Russell King <rmk@arm.linux.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Jonathan Corbet <corbet@lwn.net>,
linux-serial@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/9] serial: doc: Document .throttle()
Date: Wed, 16 Mar 2016 09:39:52 -0700 [thread overview]
Message-ID: <56E98C58.1030408@hurleysoftware.com> (raw)
In-Reply-To: <1457968577-22379-4-git-send-email-geert+renesas@glider.be>
On 03/14/2016 08:16 AM, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/serial/driver | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/serial/driver b/Documentation/serial/driver
> index 61d520dea4c6e13a..50f3d94ed50b341e 100644
> --- a/Documentation/serial/driver
> +++ b/Documentation/serial/driver
> @@ -126,6 +126,13 @@ hardware.
> Interrupts: locally disabled.
> This call must not sleep
>
> + throttle(port)
> + Notify the serial driver that input buffers for the line discipline are
> + close to full, and it should somehow signal that no more characters
> + should be sent to the serial port.
> +
> + Locking: none.
While it's true that no _serial_ locking is performed, the tty core
serializes throttle() and unthrottle(), and further guarantees termios
values will not be modified concurrently with throttle()/unthrottle().
> +
> send_xchar(port,ch)
> Transmit a high priority character, even if the port is stopped.
> This is used to implement XON/XOFF flow control and tcflow(). If
>
next prev parent reply other threads:[~2016-03-16 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 15:16 [PATCH 0/9] serial: doc: Low Level Serial API Documentation Improvements Geert Uytterhoeven
2016-03-14 15:16 ` [PATCH 1/9] serial: doc: Un-document non-existing uart_write_console() Geert Uytterhoeven
2016-03-16 16:01 ` Peter Hurley
2016-03-16 16:17 ` Geert Uytterhoeven
2016-03-14 15:16 ` [PATCH 2/9] serial: doc: Un-document obsolete tmpbuf_sem Geert Uytterhoeven
2016-03-16 16:02 ` Peter Hurley
2016-03-14 15:16 ` [PATCH 3/9] serial: doc: Document .throttle() Geert Uytterhoeven
2016-03-16 16:19 ` Geert Uytterhoeven
2016-03-16 16:39 ` Peter Hurley [this message]
2016-03-14 15:16 ` [PATCH 4/9] serial: doc: Document .unthrottle() Geert Uytterhoeven
2016-03-14 15:16 ` [PATCH 5/9] serial: doc: Document .set_ldisc() Geert Uytterhoeven
2016-03-16 16:49 ` Peter Hurley
2016-03-14 15:16 ` [PATCH 6/9] serial: doc: .break_ctl() is called with port->mutex() held Geert Uytterhoeven
2016-03-16 16:46 ` Peter Hurley
2016-03-14 15:16 ` [PATCH 7/9] serial: doc: Spelling s/divsor/divisor/ Geert Uytterhoeven
2016-03-14 15:16 ` [PATCH 8/9] serial: doc: Grammar s/function are/functions are/ Geert Uytterhoeven
2016-03-14 15:16 ` [PATCH 9/9] serial: doc: Correct return type of mctrl_gpio_to_gpiod() Geert Uytterhoeven
2016-03-31 6:59 ` [PATCH 0/9] serial: doc: Low Level Serial API Documentation Improvements Jonathan Corbet
2016-03-31 8:26 ` Geert Uytterhoeven
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=56E98C58.1030408@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=corbet@lwn.net \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).