From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: core: Fix missing shutdown and startup for serial base port
Date: Thu, 11 Apr 2024 17:53:28 +0300 [thread overview]
Message-ID: <Zhf5aHnL5mGapB1J@smile.fi.intel.com> (raw)
In-Reply-To: <20240411055848.38190-1-tony@atomide.com>
On Thu, Apr 11, 2024 at 08:58:45AM +0300, Tony Lindgren wrote:
> We are seeing start_tx being called after port shutdown as noted by Jiri.
> This happens because we are missing the startup and shutdown related
> functions for the serial base port.
>
> Let's fix the issue by adding startup and shutdown functions for the
> serial base port to block tx flushing for the serial base port when the
> port is not in use.
I tried to test this on the current max3100.c driver, but this doesn't change
anything to me. The scenario is that:
- load the driver with dyndbg on
- attach device (I have done it via SSDT overlay)
- call `stty -F /dev/ttyMAX0` to see it works
- call `stty -F /dev/ttyMAX0 115200` to setup speed
- test case:
a) run `cat /proc/interrupts > /dev/ttyMAX0`
b) press Ctrl + C
c) (most cases) press Ctrl + C
- repeat the previous step several times
The outcome (with or without this change) is that
- it repeatedly calls start_tx()
- most of the times as you may notice it requires actually to press
Ctrl + C _twice to stop the queueing
The testing environment is the tty-next + this patch.
I admit that max3100 may be buggy, but this change doesn't fix anything for it.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-04-11 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 5:58 [PATCH] serial: core: Fix missing shutdown and startup for serial base port Tony Lindgren
2024-04-11 13:06 ` Andy Shevchenko
2024-04-12 3:45 ` Tony Lindgren
2024-04-11 14:53 ` Andy Shevchenko [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=Zhf5aHnL5mGapB1J@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tony@atomide.com \
/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.