]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
dt_bindings: rs485: Correct delay values
authorLino Sanfilippo <l.sanfilippo@kunbus.com>
Sun, 10 Jul 2022 16:44:40 +0000 (18:44 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 14 Dec 2024 18:51:29 +0000 (19:51 +0100)
commite9583ac849452f94522e43e4d9f65854d432fb25
treec8065dedc4d8028555f93218bae5d6dfb6ec2440
parentad4dfa7ea7f5f7e9a3c78627cfc749bc7005ca7a
dt_bindings: rs485: Correct delay values

[ Upstream commit 885dcb08c93d75b784468e65fd4f1f82d5313061 ]

Currently the documentation claims that a maximum of 1000 msecs is allowed
for RTS delays. However nothing actually checks the values read from device
tree/ACPI and so it is possible to set much higher values.

There is already a maximum of 100 ms enforced for RTS delays that are set
via the UART TIOCSRS485 ioctl. To be consistent with that use the same
limit for DT/ACPI values.

Although this change is visible to userspace the risk of breaking anything
when reducing the max delays from 1000 to 100 ms should be very low, since
100 ms is already a very high maximum for delays that are usually rather in
the usecs range.

Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Lino Sanfilippo <l.sanfilippo@kunbus.com>
Link: https://lore.kernel.org/r/20220710164442.2958979-7-LinoSanfilippo@gmx.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Stable-dep-of: 12b3642b6c24 ("dt-bindings: serial: rs485: Fix rs485-rts-delay property")
Signed-off-by: Sasha Levin <sashal@kernel.org>
Documentation/devicetree/bindings/serial/rs485.yaml