From: Esben Haabendal <esben@geanix.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] serial: imx: Introduce timeout when waiting on transmitter empty
Date: Mon, 08 Apr 2024 10:56:16 +0200 [thread overview]
Message-ID: <87ttkckzbj.fsf@geanix.com> (raw)
In-Reply-To: <CAOMZO5Axz7un+9H2uEoQtE0=pYNC0hEyZiNobrSi2m0ajj8N+g@mail.gmail.com> (Fabio Estevam's message of "Fri, 5 Apr 2024 14:38:48 -0300")
Fabio Estevam <festevam@gmail.com> writes:
> On Fri, Apr 5, 2024 at 6:25 AM Esben Haabendal <esben@geanix.com> wrote:
>>
>> By waiting at most 1 second for USR2_TXDC to be set, we avoid a potentital
>
> s/potentital/potential
Thanks, fixing.
> Could you elaborate on this deadlock? Have you seen it in practice?
I cannot say for sure if I have seen it. But in some cases, that is
exactly what you would see. Nothing.
If it would occur during shutdown, the console would simply stop/block,
and you would see nothing.
> Should a Fixes tag be added?
Which commit should I add to that tag? The polling without timeout dates
back to at least 2.6.12-rc2.
/Esben
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-08 8:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 9:25 [PATCH 1/2] serial: imx: Introduce timeout when waiting on transmitter empty Esben Haabendal
2024-04-05 9:49 ` Marc Kleine-Budde
2024-04-05 17:22 ` Esben Haabendal
2024-04-05 17:33 ` Marc Kleine-Budde
2024-04-08 8:57 ` Esben Haabendal
2024-04-05 17:38 ` Fabio Estevam
2024-04-05 19:05 ` Sergey Organov
2024-04-08 8:56 ` Esben Haabendal [this message]
2024-04-10 7:18 ` [PATCH v2] " Esben Haabendal
2024-04-11 12:06 ` Greg Kroah-Hartman
2024-04-11 12:18 ` Esben Haabendal
2024-04-11 12:19 ` [PATCH v3] " Esben Haabendal
2024-05-02 9:14 ` Esben Haabendal
2024-05-04 16:03 ` Greg Kroah-Hartman
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=87ttkckzbj.fsf@geanix.com \
--to=esben@geanix.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).