[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220622154659.8710-6-LinoSanfilippo@gmx.de>
Date: Wed, 22 Jun 2022 17:46:56 +0200
From: Lino Sanfilippo <LinoSanfilippo@....de>
To: gregkh@...uxfoundation.org, jirislaby@...nel.org
Cc: ilpo.jarvinen@...ux.intel.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org,
andriy.shevchenko@...ux.intel.com, vz@...ia.com,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
lukas@...ner.de, p.rosenberger@...bus.com,
Lino Sanfilippo <l.sanfilippo@...bus.com>
Subject: [PATCH 5/8] dt_bindings: rs485: Correct delay values
From: Lino Sanfilippo <l.sanfilippo@...bus.com>
The maximum allowed delay for RTS before and RTS after send is 100 ms.
Adjust the documentation accordingly.
Signed-off-by: Lino Sanfilippo <l.sanfilippo@...bus.com>
---
Documentation/devicetree/bindings/serial/rs485.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/serial/rs485.yaml b/Documentation/devicetree/bindings/serial/rs485.yaml
index f2c9c9fe6aa7..90a1bab40f05 100644
--- a/Documentation/devicetree/bindings/serial/rs485.yaml
+++ b/Documentation/devicetree/bindings/serial/rs485.yaml
@@ -22,12 +22,12 @@ properties:
- description: Delay between rts signal and beginning of data sent in
milliseconds. It corresponds to the delay before sending data.
default: 0
- maximum: 1000
+ maximum: 100
- description: Delay between end of data sent and rts signal in milliseconds.
It corresponds to the delay after sending data and actual release
of the line.
default: 0
- maximum: 1000
+ maximum: 100
rs485-rts-active-low:
description: drive RTS low when sending (default is high).
--
2.36.1
Powered by blists - more mailing lists