From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: 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: [PATCH 0/4] 8250: DMA Fixes
Date: Mon, 7 Nov 2022 13:50:38 +0200 (EET) [thread overview]
Message-ID: <b66aa1-50ab-ecc-1633-d6e83f5cd925@linux.intel.com> (raw)
In-Reply-To: <Y2js3Xsq1Fmz1mTq@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Mon, 7 Nov 2022, Andy Shevchenko wrote:
> On Mon, Nov 07, 2022 at 01:07:04PM +0200, Ilpo Järvinen wrote:
> > Here are a number of 8250 DMA related fixes. The last one seems the
> > most serious problem able to corrupt the payload ordering.
> >
> > Ilpo Järvinen (4):
> > serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs
>
> 8250_port?
>
> > serial: 8250_lpss: Configure DMA also w/o DMA filter
> > serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake
> > serial: 8250: Flush DMA Rx on RLSI
>
> 8250_port?
Why?
To me this 8250_core/port split is still integral part of the same
8250 even if they're in the end technically loaded into different modules
or the code is in a different file. There's even some trickery to access
internals of the other part to workaround the circular module dependency
logic that would otherwise prevent the split (like we learned not so long
time ago with that setup_irq change).
I can start to use 8250_port if you insist but it seems pointless 5 extra
characters out from a resource that is scarse to begin with, IMHO (the
summary line is not that long).
--
i.
next prev parent reply other threads:[~2022-11-07 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 11:07 [PATCH 0/4] 8250: DMA Fixes Ilpo Järvinen
2022-11-07 11:07 ` [PATCH 1/4] serial: 8250: Fall back to non-DMA Rx if IIR_RDI occurs Ilpo Järvinen
2022-11-07 11:07 ` [PATCH 2/4] serial: 8250_lpss: Configure DMA also w/o DMA filter Ilpo Järvinen
2022-11-07 11:36 ` Andy Shevchenko
2022-11-07 11:07 ` [PATCH 3/4] serial: 8250_lpss: Use 16B DMA burst with Elkhart Lake Ilpo Järvinen
2022-11-07 11:38 ` Andy Shevchenko
2022-11-07 11:07 ` [PATCH 4/4] serial: 8250: Flush DMA Rx on RLSI Ilpo Järvinen
2022-11-07 11:40 ` Andy Shevchenko
2022-11-07 11:32 ` [PATCH 0/4] 8250: DMA Fixes Andy Shevchenko
2022-11-07 11:50 ` Ilpo Järvinen [this message]
2022-11-07 12:03 ` Andy Shevchenko
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=b66aa1-50ab-ecc-1633-d6e83f5cd925@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--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 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).