linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Douglas Anderson <dianders@chromium.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH 3/3] serial: qcom-geni: fix receiver enable
Date: Tue, 17 Sep 2024 11:11:45 +0200	[thread overview]
Message-ID: <ZulH0SZJBlgS4teO@hovoldconsulting.com> (raw)
In-Reply-To: <20240916172642.7814-4-johan+linaro@kernel.org>

On Mon, Sep 16, 2024 at 07:26:42PM +0200, Johan Hovold wrote:
> The receiver should be enabled in the startup() callback and there is no
> need to stop it on every termios update.
> 
> Since commit 6f3c3cafb115 ("serial: qcom-geni: disable interrupts during
> console writes") the calls to manipulate the secondary interrupts, which
> were done without holding the port lock, can lead to the receiver being
> left disabled when set_termios() races with the console code (e.g. when
> init opens the tty during boot).
> 
> Fixes: 6f3c3cafb115 ("serial: qcom-geni: disable interrupts during console writes")
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

Turns out the DMA implementation is broken and currently depends on
these bogus calls to stop and restart rx in set_termios().

I won't have time to look at this for a couple of weeks due to
conferences, so please hold off on merging these until I'm back.

Johan

      reply	other threads:[~2024-09-17  9:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16 17:26 [PATCH 0/3] serial: qcom-geni: fix receiver enable Johan Hovold
2024-09-16 17:26 ` [PATCH 1/3] serial: qcom-geni: fix premature " Johan Hovold
2024-09-16 17:26 ` [PATCH 2/3] serial: qcom-geni: fix shutdown race Johan Hovold
2024-09-17 15:13   ` Bartosz Golaszewski
2024-09-16 17:26 ` [PATCH 3/3] serial: qcom-geni: fix receiver enable Johan Hovold
2024-09-17  9:11   ` Johan Hovold [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=ZulH0SZJBlgS4teO@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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).