[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9cf25a55-9597-74d3-7829-6422c8a5a73c@gmx.de>
Date: Sun, 20 Mar 2022 01:01:08 +0100
From: Lino Sanfilippo <LinoSanfilippo@....de>
To: gregkh@...uxfoundation.org, jirislaby@...nel.org
Cc: u.kleine-koenig@...gutronix.de, linux@...linux.org.uk,
richard.genoud@...il.com, nicolas.ferre@...rochip.com,
alexandre.belloni@...tlin.com, ludovic.desroches@...rochip.com,
shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
festevam@...il.com, linux-imx@....com, mcoquelin.stm32@...il.com,
alexandre.torgue@...s.st.com, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-stm32@...md-mailman.stormreply.com, lukas@...ner.de,
p.rosenberger@...bus.com
Subject: Re: [PATCH v4 1/9] serial: core: move RS485 configuration tasks from
drivers into core
Hi Greg, Jiri,
On 28.02.22 at 03:39, Lino Sanfilippo wrote:
> Several drivers that support setting the RS485 configuration via userspace
> implement one or more of the following tasks:
>
> - in case of an invalid RTS configuration (both RTS after send and RTS on
> send set or both unset) fall back to enable RTS on send and disable RTS
> after send
>
> - nullify the padding field of the returned serial_rs485 struct
>
> - copy the configuration into the uart port struct
>
> - limit RTS delays to 100 ms
>
> Move these tasks into the serial core to make them generic and to provide
> a consistent behaviour among all drivers.
>
is this patch series mergeable now? Or is there anything else to do from my side?
Regards,
Lino
Powered by blists - more mailing lists