From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Jiri Slaby <jirislaby@kernel.org>, gregkh@linuxfoundation.org
Cc: linux@armlinux.org.uk, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: amba-pl011: add RS485 support
Date: Thu, 17 Jun 2021 18:12:00 +0200 [thread overview]
Message-ID: <98c29d64-3155-4769-8336-413325de4057@gmx.de> (raw)
In-Reply-To: <5f00ff43-9287-4027-7d80-474da957703c@kernel.org>
Hi,
On 16.06.21 at 08:18, Jiri Slaby wrote:
>> + if (port->rs485.delay_rts_before_send)
>> + mdelay(port->rs485.delay_rts_before_send);
>
> This is up to 1 second delay with interrupts disabled. Definitely not nice. 8250 clamps this to 100 ms at least, why did you choose 1000 ms?
>
I got this value from rs485.yaml where the max number for both rts delay before and after send
is specified as 1000ms. I thought to keep it up to the user to choose a sane setting. But yes,
its a very long time with interrupts disabled. I will send an updated version of this patch that
limits both values to 100ms.
os(struct uart_port *port, struct ktermios *termios,
>> unsigned int lcr_h, old_cr;
>> unsigned long flags;
>> unsigned int baud, quot, clkdiv;
>> + unsigned int bits;
>> if (uap->vendor->oversampling)
>> clkdiv = 8;
>> @@ -1968,25 +2049,32 @@ pl011_set_termios(struct uart_port *port, struct ktermios *termios,
>> switch (termios->c_cflag & CSIZE) {
>> case CS5:
>> lcr_h = UART01x_LCRH_WLEN_5;
>> + bits = 7;
>> break;
>> case CS6:
>> lcr_h = UART01x_LCRH_WLEN_6;
>> + bits = 8;
>> break;
>> case CS7:
>> lcr_h = UART01x_LCRH_WLEN_7;
>> + bits = 9;
>> break;
>> default: // CS8
>> lcr_h = UART01x_LCRH_WLEN_8;
>> + bits = 10;
>> break;
>> }
>> - if (termios->c_cflag & CSTOPB)
>> + if (termios->c_cflag & CSTOPB) {
>> lcr_h |= UART01x_LCRH_STP2;
>> + bits++;
>> + }
>> if (termios->c_cflag & PARENB) {
>> lcr_h |= UART01x_LCRH_PEN;
>> if (!(termios->c_cflag & PARODD))
>> lcr_h |= UART01x_LCRH_EPS;
>> if (termios->c_cflag & CMSPAR)
>> lcr_h |= UART011_LCRH_SPS;
>> + bits++;
>> }
>
> You can do simply:
> bits = tty_get_frame_size(termios->c_cflag);
> now:
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h=tty-testing&id=3ec2ff37230e1c961d4b0d0118dd23c46b5bcdbb
Ah thats a nice function, thanks for pointing at it. I will adjust the code accordingly.
>
> thanks,
Thanks for the review!
Regards,
Lino
next prev parent reply other threads:[~2021-06-17 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 13:50 Lino Sanfilippo
2021-06-16 6:18 ` Jiri Slaby
2021-06-16 6:29 ` Greg KH
2021-06-17 16:12 ` Lino Sanfilippo [this message]
2021-06-17 17:44 ` Lino Sanfilippo
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=98c29d64-3155-4769-8336-413325de4057@gmx.de \
--to=linosanfilippo@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.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
all inboxes | Powered by JetHome®