linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>
Cc: "Matwey V. Kornilov" <matwey@sai.msu.ru>,
	Heiko Schocher <hs@denx.de>,
	Giulio Benetti <giulio.benetti@micronovasrl.com>,
	Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
	Stefan Wahren <wahrenst@gmx.net>,
	Matthias Brugger <mbrugger@suse.com>,
	Martin Sperl <kernel@martin.sperl.org>,
	linux-serial@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org
Subject: [PATCH 0/8] rs485 support for Raspberry Pi aux uart
Date: Fri, 28 Feb 2020 14:31:00 +0100	[thread overview]
Message-ID: <cover.1582895077.git.lukas@wunner.de> (raw)

The objective of this series is to add rs485 support for the
Raspberry Pi auxiliary uart (patch [6/8] and [7/8]).

But I'm taking the opportunity to improve rs485 support for any
8250-compatible uart:

* rs485 devicetree properties support (patch [2/8]).
* rs485 serial console support (patch [8/8]).
* various fixes and cleanups.

Please review and test.  Thanks!


Lukas Wunner (8):
  serial: 8250: Don't touch RTS modem control while in rs485 mode
  serial: 8250: Support rs485 devicetree properties
  serial: 8250: Deduplicate ->rs485_config() callback
  serial: 8250: Sanitize rs485 config harder
  serial: 8250: Deduplicate rs485 active_timer assignment
  serial: 8250: Generalize rs485 software emulation
  serial: 8250_bcm2835aux: Support rs485 software emulation
  serial: 8250: Support console on software emulated rs485 ports

 drivers/tty/serial/8250/8250.h            |   4 +-
 drivers/tty/serial/8250/8250_bcm2835aux.c |  62 ++++++++-
 drivers/tty/serial/8250/8250_core.c       |   6 +-
 drivers/tty/serial/8250/8250_of.c         |  39 +-----
 drivers/tty/serial/8250/8250_omap.c       |  34 +----
 drivers/tty/serial/8250/8250_port.c       | 157 +++++++++++++++++-----
 include/linux/serial_8250.h               |   3 +
 7 files changed, 204 insertions(+), 101 deletions(-)

-- 
2.24.0


             reply	other threads:[~2020-02-28 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 13:31 Lukas Wunner [this message]
2020-02-28 13:31 ` [PATCH 1/8] serial: 8250: Don't touch RTS modem control while in rs485 mode Lukas Wunner
2020-02-28 13:31 ` [PATCH 2/8] serial: 8250: Support rs485 devicetree properties Lukas Wunner
2020-02-28 13:31 ` [PATCH 3/8] serial: 8250: Deduplicate ->rs485_config() callback Lukas Wunner
2020-02-28 13:31 ` [PATCH 4/8] serial: 8250: Sanitize rs485 config harder Lukas Wunner
2020-02-28 13:31 ` [PATCH 5/8] serial: 8250: Deduplicate rs485 active_timer assignment Lukas Wunner
2020-02-28 13:31 ` [PATCH 6/8] serial: 8250: Generalize rs485 software emulation Lukas Wunner
2020-02-28 13:31 ` [PATCH 7/8] serial: 8250_bcm2835aux: Support " Lukas Wunner
2020-02-28 13:31 ` [PATCH 8/8] serial: 8250: Support console on software emulated rs485 ports Lukas Wunner

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=cover.1582895077.git.lukas@wunner.de \
    --to=lukas@wunner.de \
    --cc=giulio.benetti@micronovasrl.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hs@denx.de \
    --cc=jslaby@suse.com \
    --cc=kernel@martin.sperl.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=matwey@sai.msu.ru \
    --cc=mbrugger@suse.com \
    --cc=nsaenzjulienne@suse.de \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wahrenst@gmx.net \
    /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).