From: Greg KH <gregkh@linuxfoundation.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-serial@vger.kernel.org, "Jiri Slaby" <jirislaby@kernel.org>,
"Lukas Wunner" <lukas@wunner.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Vicente Bergas" <vicencb@gmail.com>,
"Johan Hovold" <johan@kernel.org>,
heiko@sntech.de, giulio.benetti@micronovasrl.com,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
linux-api@vger.kernel.org
Subject: Re: [PATCH v5 00/10] Add RS485 support to DW UART
Date: Tue, 26 Apr 2022 14:49:00 +0200 [thread overview]
Message-ID: <YmfqPMyYLAXw1BNo@kroah.com> (raw)
In-Reply-To: <20220426122448.38997-1-ilpo.jarvinen@linux.intel.com>
On Tue, Apr 26, 2022 at 03:24:38PM +0300, Ilpo Järvinen wrote:
> This patchset adds RS-485 support to the DW UART driver. The patchset
> has two main parts. The first part adds HW support for RS-485 itself
> in various modes of operation and the second part focuses on enabling
> 9th bit addressing mode that can be used on a multipoint RS-485
> communications line.
>
> To configure multipoint addressing, ADDRB flag is added to termios
> and two new IOCTLs are added into serial core. Lukas Wunner brought up
> during v1 review that if this addressing is only going to be used with
> RS-485, doing it within rs485_config would avoid having to add those
> IOCTLs. There was some counterexample w/o further details mentioned for
> RS-232 usage by Andy Shevchenko. I left the IOCTL approach there but if
> somebody has further input on this, please voice it as it is user-space
> facing API.
>
> I decided to rewrite the UART_CAP_NOTEMT patch from scratch myself
> based on Uwe Kleine-König's earlier suggestion and include it to this
> series. To make waiting for a single character easy and to avoid
> storing it per purpose in the uart drivers, I decided to add
> frame_time into uart_port. It turned out to beneficial also for serial
> core which had to reverse calculate it from uart_port->timeout). I was
> thinking of removing uart_port->timeout entirely and derive the value
> timeout from frame_time and fifosize where needed but I was not sure
> if that's ok to do lockingwise (not that fifosize is a variable that
> is expected to change so maybe I'm just being too cautious).
I've applied the first 4 now, thanks.
greg k-h
prev parent reply other threads:[~2022-04-26 12:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 12:24 [PATCH v5 00/10] Add RS485 support to DW UART Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 01/10] serial: 8250_dwlib: RS485 HW half & full duplex support Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 02/10] serial: 8250_dwlib: Implement SW half " Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 03/10] dt_bindings: rs485: Add receiver enable polarity Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 04/10] ACPI / property: Document RS485 _DSD properties Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 05/10] serial: termbits: ADDRB to indicate 9th bit addressing mode Ilpo Järvinen
2022-04-26 12:52 ` Greg KH
2022-04-26 13:12 ` Ilpo Järvinen
2022-04-26 14:01 ` Ilpo Järvinen
2022-04-26 14:10 ` Greg KH
2022-04-26 16:29 ` Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 06/10] serial: General support for multipoint addresses Ilpo Järvinen
2022-04-26 12:56 ` Greg KH
2022-04-26 13:36 ` Ilpo Järvinen
2022-04-26 13:58 ` Greg KH
2022-04-26 12:24 ` [PATCH v5 07/10] serial: 8250: make saved LSR larger Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 08/10] serial: 8250: create lsr_save_mask Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 09/10] serial: 8250_lpss: Use 32-bit reads Ilpo Järvinen
2022-04-26 12:24 ` [PATCH v5 10/10] serial: 8250_dwlib: Support for 9th bit multipoint addressing Ilpo Järvinen
2022-04-26 12:49 ` Greg KH [this message]
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=YmfqPMyYLAXw1BNo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=giulio.benetti@micronovasrl.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko@sntech.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vicencb@gmail.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