All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	<linux-arm-kernel@lists.infradead.org>,
	Michal Simek <michal.simek@xilinx.com>,
	<linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATH RESEND v2 03/10] tty: xuartps: Always enable transmitter in start_tx
Date: Fri, 20 Nov 2015 08:58:04 -0800	[thread overview]
Message-ID: <20151120165804.GV32017@xsjsorenbubuntu> (raw)
In-Reply-To: <564F4A95.3010303@hurleysoftware.com>

Hi Peter,

On Fri, 2015-11-20 at 11:30AM -0500, Peter Hurley wrote:
> Hi Sören,
> 
> On 11/20/2015 10:28 AM, Sören Brinkmann wrote:
> > On Fri, 2015-11-20 at 07:13AM -0500, Peter Hurley wrote:
> >> On 11/19/2015 03:02 PM, Soren Brinkmann wrote:
> >>> start_tx must start transmitting characters. Regardless of the state of
> >>> the circular buffer, always enable the transmitter hardware.
> >>
> >> Why?
> >>
> >> Does cdns_uart_stop_tx() actually stop the transmitter so that
> >> data remains in the transmitter?
> > 
> > Well, I saw my system freezing and the cause seemed to be that the UART
> > receiver and/or transmitters were disabled while the system was trying
> > to print. Hence, I started questioning all locations touching the
> > transmitter/receiver enable. I read the docs in
> > https://www.kernel.org/doc/Documentation/serial/driver, which simply
> > says "Start transmitting characters." for start_tx(). Hence, I thought,
> > this function is probably supposed to just do that and start the
> > transmitter. I'll test whether this patch can be dropped.
> 
> I don't think that patch would fix any freeze problems, but restarting
> the transmitter even if the circ buffer is empty may be necessary to
> push out remaining data when the port is restarted after being stopped.
> 
> IOW, something like
> 
> 	if (uart_tx_stopped(port))
> 		return;
> 
> 	....
> 
> 
> 	if (uart_circ_empty(&port->state->xmit)
> 		return;

Thanks! I'll change the patch accordingly.

> 
> 
> Below is a (work-in-progress) serial driver validation test for flow
> control handling (it may need some tuning for slow line speeds).
> Usual caveats apply. Takes ~40secs @ 115200.

I'll try to get that running on my system.

	Thanks,
	Sören

WARNING: multiple messages have this Message-ID (diff)
From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	linux-arm-kernel@lists.infradead.org,
	Michal Simek <michal.simek@xilinx.com>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATH RESEND v2 03/10] tty: xuartps: Always enable transmitter in start_tx
Date: Fri, 20 Nov 2015 08:58:04 -0800	[thread overview]
Message-ID: <20151120165804.GV32017@xsjsorenbubuntu> (raw)
In-Reply-To: <564F4A95.3010303@hurleysoftware.com>

Hi Peter,

On Fri, 2015-11-20 at 11:30AM -0500, Peter Hurley wrote:
> Hi Sören,
> 
> On 11/20/2015 10:28 AM, Sören Brinkmann wrote:
> > On Fri, 2015-11-20 at 07:13AM -0500, Peter Hurley wrote:
> >> On 11/19/2015 03:02 PM, Soren Brinkmann wrote:
> >>> start_tx must start transmitting characters. Regardless of the state of
> >>> the circular buffer, always enable the transmitter hardware.
> >>
> >> Why?
> >>
> >> Does cdns_uart_stop_tx() actually stop the transmitter so that
> >> data remains in the transmitter?
> > 
> > Well, I saw my system freezing and the cause seemed to be that the UART
> > receiver and/or transmitters were disabled while the system was trying
> > to print. Hence, I started questioning all locations touching the
> > transmitter/receiver enable. I read the docs in
> > https://www.kernel.org/doc/Documentation/serial/driver, which simply
> > says "Start transmitting characters." for start_tx(). Hence, I thought,
> > this function is probably supposed to just do that and start the
> > transmitter. I'll test whether this patch can be dropped.
> 
> I don't think that patch would fix any freeze problems, but restarting
> the transmitter even if the circ buffer is empty may be necessary to
> push out remaining data when the port is restarted after being stopped.
> 
> IOW, something like
> 
> 	if (uart_tx_stopped(port))
> 		return;
> 
> 	....
> 
> 
> 	if (uart_circ_empty(&port->state->xmit)
> 		return;

Thanks! I'll change the patch accordingly.

> 
> 
> Below is a (work-in-progress) serial driver validation test for flow
> control handling (it may need some tuning for slow line speeds).
> Usual caveats apply. Takes ~40secs @ 115200.

I'll try to get that running on my system.

	Thanks,
	Sören

WARNING: multiple messages have this Message-ID (diff)
From: soren.brinkmann@xilinx.com (Sören Brinkmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATH RESEND v2 03/10] tty: xuartps: Always enable transmitter in start_tx
Date: Fri, 20 Nov 2015 08:58:04 -0800	[thread overview]
Message-ID: <20151120165804.GV32017@xsjsorenbubuntu> (raw)
In-Reply-To: <564F4A95.3010303@hurleysoftware.com>

Hi Peter,

On Fri, 2015-11-20 at 11:30AM -0500, Peter Hurley wrote:
> Hi S?ren,
> 
> On 11/20/2015 10:28 AM, S?ren Brinkmann wrote:
> > On Fri, 2015-11-20 at 07:13AM -0500, Peter Hurley wrote:
> >> On 11/19/2015 03:02 PM, Soren Brinkmann wrote:
> >>> start_tx must start transmitting characters. Regardless of the state of
> >>> the circular buffer, always enable the transmitter hardware.
> >>
> >> Why?
> >>
> >> Does cdns_uart_stop_tx() actually stop the transmitter so that
> >> data remains in the transmitter?
> > 
> > Well, I saw my system freezing and the cause seemed to be that the UART
> > receiver and/or transmitters were disabled while the system was trying
> > to print. Hence, I started questioning all locations touching the
> > transmitter/receiver enable. I read the docs in
> > https://www.kernel.org/doc/Documentation/serial/driver, which simply
> > says "Start transmitting characters." for start_tx(). Hence, I thought,
> > this function is probably supposed to just do that and start the
> > transmitter. I'll test whether this patch can be dropped.
> 
> I don't think that patch would fix any freeze problems, but restarting
> the transmitter even if the circ buffer is empty may be necessary to
> push out remaining data when the port is restarted after being stopped.
> 
> IOW, something like
> 
> 	if (uart_tx_stopped(port))
> 		return;
> 
> 	....
> 
> 
> 	if (uart_circ_empty(&port->state->xmit)
> 		return;

Thanks! I'll change the patch accordingly.

> 
> 
> Below is a (work-in-progress) serial driver validation test for flow
> control handling (it may need some tuning for slow line speeds).
> Usual caveats apply. Takes ~40secs @ 115200.

I'll try to get that running on my system.

	Thanks,
	S?ren

  reply	other threads:[~2015-11-20 16:56 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19 20:02 [PATH RESEND v2 00/10] tty: xuartps: Fix lock ups Soren Brinkmann
2015-11-19 20:02 ` Soren Brinkmann
2015-11-19 20:02 ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 01/10] tty: xuartps: Beautify read-modify writes Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 02/10] tty: xuartps: Use spinlock to serialize HW access Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 03/10] tty: xuartps: Always enable transmitter in start_tx Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 23:15   ` Peter Hurley
2015-11-20 12:13   ` Peter Hurley
2015-11-20 12:13     ` Peter Hurley
2015-11-20 15:28     ` Sören Brinkmann
2015-11-20 15:28       ` Sören Brinkmann
2015-11-20 15:28       ` Sören Brinkmann
2015-11-20 16:30       ` Peter Hurley
2015-11-20 16:30         ` Peter Hurley
2015-11-20 16:58         ` Sören Brinkmann [this message]
2015-11-20 16:58           ` Sören Brinkmann
2015-11-20 16:58           ` Sören Brinkmann
2015-11-20 17:16           ` Peter Hurley
2015-11-20 17:16             ` Peter Hurley
2015-11-20 17:29             ` Sören Brinkmann
2015-11-20 17:29               ` Sören Brinkmann
2015-11-20 17:29               ` Sören Brinkmann
2015-11-23  7:05             ` Michal Simek
2015-11-23  7:05               ` Michal Simek
2015-11-23  7:05               ` Michal Simek
2015-11-23 20:00               ` Peter Hurley
2015-11-23 20:00                 ` Peter Hurley
2015-11-24  7:26                 ` Michal Simek
2015-11-24  7:26                   ` Michal Simek
2015-11-24  7:26                   ` Michal Simek
2015-11-20 17:05     ` Sören Brinkmann
2015-11-20 17:05       ` Sören Brinkmann
2015-11-20 17:05       ` Sören Brinkmann
2015-11-20 17:12       ` Peter Hurley
2015-11-20 17:12         ` Peter Hurley
2015-11-19 20:02 ` [PATH RESEND v2 04/10] tty: xuartps: Clear interrupt status register in shutdown Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 05/10] tty: xuartps: Improve startup function Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 06/10] tty: xuartps: Keep lock for whole ISR Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 07/10] tty: xuartps: Acquire port lock for shutdown Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 08/10] tty: xuartps: Move RX path into helper function Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 09/10] tty: xuartps: Only handle RX IRQs when RX is enabled Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02 ` [PATH RESEND v2 10/10] tty: xuartps: Cleanup: Reformat if-else Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann
2015-11-19 20:02   ` Soren Brinkmann

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=20151120165804.GV32017@xsjsorenbubuntu \
    --to=soren.brinkmann@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --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.