From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] tty: serial: core: Only invoke ->start_tx() if there is data to send
Date: Thu, 11 Sep 2014 10:03:58 +0200 [thread overview]
Message-ID: <5411576E.204@linutronix.de> (raw)
In-Reply-To: <5410AC1B.9000700@hurleysoftware.com>
On 09/10/2014 09:52 PM, Peter Hurley wrote:
> The serial core can't assume that start_tx() does not need invoking
> because hardware that can stop_tx() with data in the transmitter
> won't restart if the ring buffer is empty but data is still in the
> transmitter. [Note that the 16C950 port type does this in the 8250 driver.]
oh, not sure how I missed this… But now that I look at this, it is also
that ->x_char that could be use for flow control which would have to be
sent even with an empty xmit buffer.
And 8250 in DMA mode does not look at x_char at all. But it would be
better if it would, right? However if the TX side does a 2 KiB transfer
not sure what should be done…
> So this has to be handled in the 8250 driver.
>
> What is the actual issue? Are you trying not to unnecessarily wake
> the omap hardware if runtime-PM is on?
no, it is actually the extra interrupt for no reason that looked like
not needed at all. But I guess it is only during "startup" while the
init-script do fancy things and not during "normal" operations.
> Regards,
> Peter Hurley
Sebastian
next prev parent reply other threads:[~2014-09-11 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 19:33 [RFC PATCH] tty: serial: core: Only invoke ->start_tx() if there is data to send Sebastian Andrzej Siewior
2014-09-10 19:52 ` Peter Hurley
2014-09-11 8:03 ` Sebastian Andrzej Siewior [this message]
2014-09-11 12:48 ` Peter Hurley
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=5411576E.204@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.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 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.