From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-serial@vger.kernel.org,
"Greg KH" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Lukas Wunner" <lukas@wunner.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Vicente Bergas" <vicencb@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Johan Hovold" <johan@kernel.org>,
heiko@sntech.de, giulio.benetti@micronovasrl.com,
"Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
devicetree@vger.kernel.org, "Rob Herring" <robh@kernel.org>
Subject: [PATCH v4 06/13] dt_bindings: rs485: Add receiver enable polarity
Date: Mon, 25 Apr 2022 17:34:03 +0300 [thread overview]
Message-ID: <20220425143410.12703-7-ilpo.jarvinen@linux.intel.com> (raw)
In-Reply-To: <20220425143410.12703-1-ilpo.jarvinen@linux.intel.com>
Add polarity property for receiver enable. Some UARTs have separate
enable pins for tx (RTS or DE) and rx (RE). As most RS485 transceivers
have !RE pin, the default is active low in contrast to
rs485-rts-active-low that defaults to active high.
Cc: devicetree@vger.kernel.org
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
---
Documentation/devicetree/bindings/serial/rs485.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/rs485.yaml b/Documentation/devicetree/bindings/serial/rs485.yaml
index 0c9fa694f85c..f2c9c9fe6aa7 100644
--- a/Documentation/devicetree/bindings/serial/rs485.yaml
+++ b/Documentation/devicetree/bindings/serial/rs485.yaml
@@ -33,6 +33,11 @@ properties:
description: drive RTS low when sending (default is high).
$ref: /schemas/types.yaml#/definitions/flag
+ rs485-rx-active-high:
+ description: Polarity of receiver enable signal (when separate from RTS).
+ True indicates active high (default is low).
+ $ref: /schemas/types.yaml#/definitions/flag
+
linux,rs485-enabled-at-boot-time:
description: enables the rs485 feature at boot time. It can be disabled
later with proper ioctl.
--
2.30.2
next prev parent reply other threads:[~2022-04-25 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 14:33 [PATCH v4 00/13] Add RS485 support to DW UART Ilpo Järvinen
2022-04-25 14:33 ` [PATCH v4 01/13] serial: Store character timing information to uart_port Ilpo Järvinen
2022-04-25 14:33 ` [PATCH v4 02/13] serial: 8250: use THRE & __stop_tx also with DMA Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 03/13] serial: 8250: Handle UART without interrupt on TEMT Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 04/13] serial: 8250_dwlib: RS485 HW half & full duplex support Ilpo Järvinen
2022-04-26 11:29 ` Greg KH
2022-09-20 11:37 ` Lukas Wunner
2022-09-20 12:01 ` Ilpo Järvinen
2022-09-20 12:10 ` Lukas Wunner
2022-04-25 14:34 ` [PATCH v4 05/13] serial: 8250_dwlib: Implement SW half " Ilpo Järvinen
2022-04-25 14:34 ` Ilpo Järvinen [this message]
2022-04-25 14:34 ` [PATCH v4 07/13] ACPI / property: Document RS485 _DSD properties Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 08/13] serial: termbits: ADDRB to indicate 9th bit addressing mode Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 09/13] serial: General support for multipoint addresses Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 10/13] serial: 8250: make saved LSR larger Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 11/13] serial: 8250: create lsr_save_mask Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 12/13] serial: 8250_lpss: Use 32-bit reads Ilpo Järvinen
2022-04-25 14:34 ` [PATCH v4 13/13] serial: 8250_dwlib: Support for 9th bit multipoint addressing Ilpo Järvinen
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=20220425143410.12703-7-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=giulio.benetti@micronovasrl.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko@sntech.de \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).