From: Greg KH <gregkh@linuxfoundation.org>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: jirislaby@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, ilpo.jarvinen@linux.intel.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
l.sanfilippo@kunbus.com, lukas@wunner.de,
p.rosenberger@kunbus.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/6] serial: Do not hold the port lock when setting rx-during-tx GPIO
Date: Fri, 29 Sep 2023 07:50:32 +0200 [thread overview]
Message-ID: <2023092906-untainted-entangled-4d17@gregkh> (raw)
In-Reply-To: <20230928221246.13689-2-LinoSanfilippo@gmx.de>
On Fri, Sep 29, 2023 at 12:12:41AM +0200, Lino Sanfilippo wrote:
> From: Lino Sanfilippo <l.sanfilippo@kunbus.com>
>
> Both the imx and stm32 driver set the rx-during-tx GPIO in the
> rs485_config() function by means of gpiod_set_value(). Since rs485_config()
> is called with the port lock held, this can be an problem in case that
> setting the GPIO line can sleep (e.g. if a GPIO expander is used which is
> connected via SPI or I2C).
>
> Avoid this issue by setting the GPIO outside of the port lock in the serial
> core and by using gpiod_set_value_cansleep() instead of gpiod_set_value().
>
> Since now both the term and the rx-during-tx GPIO are set within the serial
> core use a common function uart_set_rs485_gpios() to set both.
>
> With moving it into the serial core setting the rx-during-tx GPIO is now
> automatically done for all drivers that support such a GPIO.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Lino Sanfilippo <l.sanfilippo@kunbus.com>
You cc: stable on many of these, but do not provide a "Fixes:" tag
showing just how far back they should go. Can you do that so that we
have a hint as to what to do here?
thanks,
greg k-h
next prev parent reply other threads:[~2023-09-29 5:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 22:12 [PATCH 0/6] Fixes and improvements for RS485 Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 1/6] serial: Do not hold the port lock when setting rx-during-tx GPIO Lino Sanfilippo
2023-09-29 5:50 ` Greg KH [this message]
2023-09-29 12:21 ` Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 2/6] serial: amba-pl011: get rid of useless wrapper pl011_get_rs485_mode() Lino Sanfilippo
2023-09-28 22:33 ` Lukas Wunner
2023-09-28 22:12 ` [PATCH 3/6] serial: core: set missing supported flag for RX during TX GPIO Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 4/6] serial: core: fix sanitizing check for RTS settings Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 5/6] serial: core: make sure RS485 is cannot be enabled when it is not supported Lino Sanfilippo
2023-09-29 12:17 ` Hugo Villeneuve
2023-09-29 12:25 ` Lino Sanfilippo
2023-09-28 22:12 ` [PATCH 6/6] serial: imx: do not set RS485 enabled if " Lino Sanfilippo
2023-09-29 5:51 ` Greg KH
2023-09-29 12:22 ` Lino Sanfilippo
2023-09-29 6:39 ` Uwe Kleine-König
2023-09-29 13:46 ` Lino Sanfilippo
2023-09-29 15:44 ` Uwe Kleine-König
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=2023092906-untainted-entangled-4d17@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=LinoSanfilippo@gmx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.rosenberger@kunbus.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
/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).