[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdU5N6dBKgDudod+0cHumAreHCHgi1+xGqXtvpkiLNz0Q@mail.gmail.com>
Date: Wed, 30 Sep 2020 17:54:15 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
"open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jan Kundrát <jan.kundrat@...net.cz>,
Mark Brown <broonie@...nel.org>,
linux-spi <linux-spi@...r.kernel.org>
Subject: Re: [PATCH] serial: max310x: rework RX interrupt handling
On Wed, Sep 30, 2020 at 5:50 PM Thomas Petazzoni
<thomas.petazzoni@...tlin.com> wrote:
> On Wed, 30 Sep 2020 17:24:48 +0300
> Andy Shevchenko <andy.shevchenko@...il.com> wrote:
> > > On a Microchip SAMA5D3 platform that is receiving 20 bytes every 16ms
> > > over one MAX310X UART, this patch has allowed to reduce the CPU
> > > consumption of the interrupt handler thread from ~25% to 6-7%.
> >
> > Was it always like this?
>
> As far as I can see, yes. I guess you were thinking about a Fixes: tag
> perhaps? I don't think a Fixes: tag really applies here, as we're not
> fixing a performance regression.
Thanks for elaboration.
...
> > > + /* Reset FIFOs*/
> >
> > Add a space before the asterisk.
>
> Indeed. Let me know if a v2 is needed, or if this small typo can be
> fixed when applying.
Greg usually doesn't touch commits, so v2 would be better.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists