[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YrSU4eL9hgISg3Y1@smile.fi.intel.com>
Date: Thu, 23 Jun 2022 19:29:21 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Lino Sanfilippo <LinoSanfilippo@....de>
Cc: gregkh@...uxfoundation.org, jirislaby@...nel.org,
ilpo.jarvinen@...ux.intel.com, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, 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: Re: [PATCH 5/8] dt_bindings: rs485: Correct delay values
On Wed, Jun 22, 2022 at 05:46:56PM +0200, Lino Sanfilippo wrote:
> 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.
Is it only documentation issue? If the code allows this to be set higher
than 100, we may not change the documentation since this an ABI (from
firmware <--> kernel perspective) we need to support old variants.
If the above is true and limit is dictated by the spec, we may issue a
warning in the code and drop it to the allowed maximum, otherwise we
can't do much here.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists