From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Lennert Buytenhek <buytenh@wantstofly.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: I/O page faults from 8250_mid PCIe UART after TIOCVHANGUP
Date: Mon, 19 Sep 2022 17:12:26 +0300 (EEST) [thread overview]
Message-ID: <db3c5a9-9dc3-e57-d74d-8ee2d4b1a33@linux.intel.com> (raw)
In-Reply-To: <Yyhyxmt+rhxEI0VH@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Mon, 19 Sep 2022, Andy Shevchenko wrote:
> On Thu, Sep 15, 2022 at 07:27:45PM +0300, Ilpo Järvinen wrote:
> > On Wed, 14 Sep 2022, Andy Shevchenko wrote:
> > > On Wed, Sep 14, 2022 at 02:10:44PM +0300, Lennert Buytenhek wrote:
> > > > On Wed, Sep 14, 2022 at 01:09:40PM +0300, Andy Shevchenko wrote:
>
> ...
>
> > - /*
> > - * The above check will only give an accurate result the first time
> > - * the port is opened so this value needs to be preserved.
> > - */
>
> Side note: I haven't got why you removed this comment (it may be some staled
> info, but shouldn't be done in the separate change then?).
I cleaned up this part in v2 (as you probably noticed). I was just an
artifact of how the fix got initially made.
I've also located the place where the comment belongs to. "The above
check" refers to the THRE test. However, I don't fully understand the
comment itself, that is, why the test is claimed to only work for for the
first time. As long as FIFO is cleared beforehand, I think it should work
on other times too.
--
i.
prev parent reply other threads:[~2022-09-19 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 7:15 I/O page faults from 8250_mid PCIe UART after TIOCVHANGUP Lennert Buytenhek
2022-09-14 10:09 ` Andy Shevchenko
2022-09-14 11:10 ` Lennert Buytenhek
2022-09-14 13:06 ` Andy Shevchenko
2022-09-15 16:27 ` Ilpo Järvinen
2022-09-16 11:47 ` Lennert Buytenhek
2022-09-16 12:02 ` Ilpo Järvinen
2022-09-16 13:18 ` Lennert Buytenhek
2022-09-19 13:46 ` Andy Shevchenko
2022-09-19 14:19 ` Ilpo Järvinen
2022-09-19 14:22 ` Lennert Buytenhek
2022-09-19 13:46 ` Andy Shevchenko
2022-09-19 14:12 ` Ilpo Järvinen [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=db3c5a9-9dc3-e57-d74d-8ee2d4b1a33@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=buytenh@wantstofly.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@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 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.