Lino Sanfilippo 885dcb08c9 dt_bindings: rs485: Correct delay values ... 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>		2022-07-14 16:34:24 +02:00
..
bindings	dt_bindings: rs485: Correct delay values	2022-07-14 16:34:24 +02:00
changesets.rst	docs: dt: Make 'Devicetree' wording more consistent	2021-03-27 12:58:04 -06:00
dynamic-resolution-notes.rst	docs: dt: Make 'Devicetree' wording more consistent	2021-03-27 12:58:04 -06:00
index.rst	docs: dt: Add DT API documentation	2021-03-27 12:59:03 -06:00
kernel-api.rst	docs: dt: Add DT API documentation	2021-03-27 12:59:03 -06:00
of_unittest.rst	of: unittest: add program to process EXPECT messages	2022-02-28 15:20:32 -06:00
overlay-notes.rst	of: overlay: rework overlay apply and remove kfree()s	2022-04-25 10:56:11 -05:00
usage-model.rst	docs: dt: Make 'Devicetree' wording more consistent	2021-03-27 12:58:04 -06:00