From: Lukas Wunner <lukas@wunner.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Marek Vasut <marex@denx.de>, Jiri Slaby <jirislaby@kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Lino Sanfilippo <LinoSanfilippo@gmx.de>
Subject: Re: [PATCH] serial: stm32: Deassert Transmit Enable on ->rs485_config()
Date: Sat, 17 Sep 2022 16:13:15 +0200 [thread overview]
Message-ID: <20220917141315.GA1584@wunner.de> (raw)
In-Reply-To: <774e5f24-c673-bbd2-08e-403987b63d1b@linux.intel.com>
On Tue, Sep 13, 2022 at 11:24:01AM +0300, Ilpo Järvinen wrote:
> On Sun, 11 Sep 2022, Lukas Wunner wrote:
> > The STM32 USART can control RS-485 Transmit Enable in hardware. Since
> > commit 7df5081cbf5e ("serial: stm32: Add RS485 RTS GPIO control"),
> > it can alternatively be controlled in software. That was done to allow
> > RS-485 even if the RTS pin is unavailable because it's pinmuxed to a
> > different function.
> >
> > However the commit neglected to deassert Transmit Enable upon invocation
> > of the ->rs485_config() callback. Fix it.
> >
> > Avoid forward declarations by moving stm32_usart_tx_empty(),
> > stm32_usart_rs485_rts_enable() and stm32_usart_rs485_rts_disable()
> > further up in the driver.
> >
> > Fixes: 7df5081cbf5e ("serial: stm32: Add RS485 RTS GPIO control")
> > Signed-off-by: Lukas Wunner <lukas@wunner.de>
> > Cc: stable@vger.kernel.org # v5.9+
> > Cc: Marek Vasut <marex@denx.de>
>
> I'd prefer to have those plain function moves to be in a separate patch.
Keeping that in a single patch eases backporting.
Let's see which way Greg prefers.
> Other than that,
>
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Thanks a lot!
Lukas
prev parent reply other threads:[~2022-09-17 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 9:02 [PATCH] serial: stm32: Deassert Transmit Enable on ->rs485_config() Lukas Wunner
2022-09-13 8:24 ` Ilpo Järvinen
2022-09-17 14:13 ` Lukas Wunner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220917141315.GA1584@wunner.de \
--to=lukas@wunner.de \
--cc=LinoSanfilippo@gmx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).