From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Lino Sanfilippo" <l.sanfilippo@kunbus.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
u.kleine-koenig@pengutronix.de, shawnguo@kernel.org,
s.hauer@pengutronix.de, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, cniedermaier@dh-electronics.com,
hugo@hugovil.com, m.brock@vanmierlo.com,
LKML <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
Lukas Wunner <lukas@wunner.de>,
p.rosenberger@kunbus.com, stable@vger.kernel.org
Subject: Re: [PATCH v7 6/7] serial: omap: do not override settings for RS485 support
Date: Fri, 5 Jan 2024 13:42:41 +0100 [thread overview]
Message-ID: <a41ae447-565a-4db3-96ff-30aef6455a7c@gmx.de> (raw)
In-Reply-To: <c88034d4-cb5-b64e-7a76-194ef35f28@linux.intel.com>
On 03.01.24 at 12:36, Ilpo Järvinen wrote:
> On Wed, 3 Jan 2024, Lino Sanfilippo wrote:
>
>> The drivers RS485 support is deactivated if there is no RTS GPIO available.
>> This is done by nullifying the ports rs485_supported struct. After that
>> however the settings in serial_omap_rs485_supported are assigned to the
>> same structure unconditionally, which results in an unintended reactivation
>> of RS485 support.
>>
>> Fix this by moving the assignment to the beginning of
>> serial_omap_probe_rs485() and thus before uart_get_rs485_mode() gets
>> called.
>
> This doesn't seem to accurately reflect what the problem is (which you
> correctly described in the paragraph above this). The problem doesn't seem
> to have anything to do with the placement of uart_get_rs485_mode() call
> but the if (IS_ERR(up->rts_gpiod)) block that clears rs485_supported?
>
Right, this should be "...Fix this by moving the assignment to the beginning of
serial_omap_probe_rs485() and thus before the check for the RTS GPIO."
I will correct this.
> A future work item that came to my mind while reviewing this: I suppose
> uart_disable_rs485_support() could be added into core which memsets
> rs485_supported and rs485 to zero so this driver could just call it.
>
Yes, and the ar933x driver could use that as well.
Regards,
Lino
next prev parent reply other threads:[~2024-01-05 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 6:18 [PATCH v7 0/7] Fixes and improvements for RS485 Lino Sanfilippo
2024-01-03 6:18 ` [PATCH v7 1/7] serial: Do not hold the port lock when setting rx-during-tx GPIO Lino Sanfilippo
2024-01-03 11:10 ` Ilpo Järvinen
2024-01-05 10:44 ` Lino Sanfilippo
2024-01-03 6:18 ` [PATCH v7 2/7] serial: core: set missing supported flag for RX during TX GPIO Lino Sanfilippo
2024-01-03 6:18 ` [PATCH v7 3/7] serial: core: fix sanitizing check for RTS settings Lino Sanfilippo
2024-01-03 6:18 ` [PATCH v7 4/7] serial: core: make sure RS485 cannot be enabled when it is not supported Lino Sanfilippo
2024-01-03 6:18 ` [PATCH v7 5/7] serial: core, imx: do not set RS485 enabled if " Lino Sanfilippo
2024-01-03 11:19 ` Ilpo Järvinen
2024-01-03 6:18 ` [PATCH v7 6/7] serial: omap: do not override settings for RS485 support Lino Sanfilippo
2024-01-03 11:36 ` Ilpo Järvinen
2024-01-05 12:42 ` Lino Sanfilippo [this message]
2024-01-03 6:18 ` [PATCH v7 7/7] serial: 8250_exar: Set missing rs485_supported flag Lino Sanfilippo
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=a41ae447-565a-4db3-96ff-30aef6455a7c@gmx.de \
--to=linosanfilippo@gmx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=cniedermaier@dh-electronics.com \
--cc=gregkh@linuxfoundation.org \
--cc=hugo@hugovil.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=m.brock@vanmierlo.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=p.rosenberger@kunbus.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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
all inboxes | Powered by JetHome®