From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Matwey V. Kornilov" <matwey@sai.msu.ru>
Cc: gregkh@linuxfoundation.org, jslaby@suse.com,
peter@hurleysoftware.com, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v3 5/5] tty: Add software emulated RS485 support for 8250
Date: Tue, 17 Nov 2015 10:24:42 +0100 [thread overview]
Message-ID: <20151117092442.GL22022@pengutronix.de> (raw)
In-Reply-To: <1447338836-8785-6-git-send-email-matwey@sai.msu.ru>
Hello,
On Thu, Nov 12, 2015 at 05:33:56PM +0300, Matwey V. Kornilov wrote:
> +static void serial8250_start_tx(struct uart_port *port)
> +{
> + struct uart_8250_port *up = up_to_u8250p(port);
> + __u32 delay;
> +
> + serial8250_rpm_get_tx(up);
> +
> + if (timer_pending(&up->rs485_start_tx_timer))
> + return;
I think this is wrong (or at least suboptimal). The .start_tx callback
can be called even if transmission is already ongoing. In this case you
don't want to restart the rs485_start_tx_timer.
> + if ((delay = serial8250_rs485_start_tx(up))) {
> + mod_timer(&up->rs485_start_tx_timer, jiffies + delay * HZ / 1000);
> + } else {
> + __start_tx(port);
> + }
> +}
> +
> [...]
> diff --git a/include/linux/serial_8250.h b/include/linux/serial_8250.h
> index faa0e03..c4905e7 100644
> --- a/include/linux/serial_8250.h
> +++ b/include/linux/serial_8250.h
> @@ -86,6 +86,8 @@ struct uart_8250_ops {
> struct uart_8250_port {
> struct uart_port port;
> struct timer_list timer; /* "no irq" timer */
> + struct timer_list rs485_start_tx_timer; /* "rs485 start tx" timer */
> + struct timer_list rs485_stop_tx_timer; /* "rs485 stop tx" timer */
Do you really need two timers here? At each point in time there should
only be at most one of them active.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-11-17 9:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 14:33 [PATCH v3 0/5] tty: Introduce software RS485 direction control support Matwey V. Kornilov
2015-11-12 14:33 ` [PATCH v3 1/5] tty: Introduce UART_CAP_HW485 Matwey V. Kornilov
2015-11-12 14:33 ` [PATCH v3 2/5] tty: Introduce SER_RS485_SOFTWARE read-only flag for struct serial_rs485 Matwey V. Kornilov
2015-11-12 19:57 ` One Thousand Gnomes
2015-11-12 20:22 ` Peter Hurley
2015-11-13 0:41 ` Andy Shevchenko
2015-11-13 1:11 ` Peter Hurley
2015-11-13 1:26 ` Andy Shevchenko
2015-11-13 1:55 ` Peter Hurley
2015-11-14 15:25 ` One Thousand Gnomes
2015-11-16 19:18 ` Peter Hurley
2015-11-17 8:20 ` Matwey V. Kornilov
2015-11-18 18:33 ` Peter Hurley
2015-11-18 19:39 ` Matwey V. Kornilov
2015-11-18 19:49 ` Matwey V. Kornilov
2015-12-02 23:20 ` Peter Hurley
2015-12-03 5:50 ` Matwey V. Kornilov
2015-12-03 14:41 ` Peter Hurley
2015-12-03 17:29 ` Matwey V. Kornilov
2015-12-03 19:45 ` Peter Hurley
2015-12-04 17:50 ` Matwey V. Kornilov
2015-11-13 20:03 ` Matwey V. Kornilov
2015-11-12 14:33 ` [PATCH v3 3/5] tty: Implement default fallback serial8250_rs485_config Matwey V. Kornilov
2015-11-12 14:33 ` [PATCH v3 4/5] tty: Move serial8250_stop_rx in front of serial8250_start_tx Matwey V. Kornilov
2015-11-12 14:33 ` [PATCH v3 5/5] tty: Add software emulated RS485 support for 8250 Matwey V. Kornilov
2015-11-12 14:48 ` Andy Shevchenko
2015-11-17 9:24 ` Uwe Kleine-König [this message]
2015-11-17 10:25 ` Matwey V. Kornilov
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=20151117092442.GL22022@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--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 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).