All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Michael McAllister" <me@michaelmcallister.org>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: qcom-geni: Set UPSTAT_AUTOCTS for hardware flow control
Date: Thu, 22 Oct 2026 19:42:12 +0000	[thread overview]
Message-ID: <sashiko-outbox-181975@kernel.org> (raw)
In-Reply-To: <179269779969.81501.3877980314174207182.geni-autocts-v2@michaelmcallister.org>

> qcom_geni_serial_set_termios() clears UART_CTS_MASK when CRTSCTS is set,
> enabling hardware CTS flow control. However, it never sets UPSTAT_AUTOCTS,
> so uart_softcts_mode() also selects software-assisted CTS flow control.
> 
> If CTS is deasserted when uart_change_line_settings() samples the modem
> status, serial core sets hw_stopped and stops transmission. The GENI
> driver does not handle CTS-change interrupts, so asserting CTS again does
> not clear hw_stopped or restart the transmitter.
> 
> On a Motorola Moto G10 with WCN3950, this can stall Bluetooth setup in
> tty_wait_until_sent() while qca_setup() closes the serial port. A captured
> stall had one byte left in the software transmit queue, hw_stopped set,
> and CTS asserted, with the UART powered and its interrupt enabled.
> 
> Set UPSTAT_AUTOCTS under the port lock when CRTSCTS is enabled, and clear
> it when CRTSCTS is disabled, to match the hardware configuration.
> 
> Fixes: 8a8a66a1a18a ("tty: serial: qcom_geni_serial: Add support for flow control")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Michael McAllister <me@michaelmcallister.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/179269779969.81501.3877980314174207182.geni-autocts-v2@michaelmcallister.org?part=1


      reply	other threads:[~2026-10-22 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 20:26 [PATCH] serial: qcom-geni: Set UPSTAT_AUTOCTS for hardware flow control Michael McAllister
2026-10-21 20:31 ` sashiko-bot
2026-10-22  3:59 ` Jiri Slaby
2026-10-22 19:36   ` Michael McAllister
2026-10-22 19:36 ` [PATCH v2] " Michael McAllister
2026-10-22 19:42   ` sashiko-bot [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=sashiko-outbox-181975@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=me@michaelmcallister.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.