[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBSVld3HKL_M1agq@smile.fi.intel.com>
Date: Fri, 2 May 2025 12:51:17 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Judith Mendez <jm@...com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Kevin Hilman <khilman@...libre.com>,
Jiri Slaby <jirislaby@...nel.org>, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, Hari Nagalla <hnagalla@...com>
Subject: Re: [PATCH RFC 0/2] Introduce PRU UART driver
On Thu, May 01, 2025 at 09:47:34AM -0500, Judith Mendez wrote:
> On 5/1/25 12:18 AM, Greg Kroah-Hartman wrote:
> > On Wed, Apr 30, 2025 at 07:31:11PM -0500, Judith Mendez wrote:
> > > This patch series is sent as an RFC to get some initial comments
> > > on the PRU UART driver.
> > >
> > > The ICSSM modules on am64x SoC and the PRUSS module on am62 SoC or am335x
> > > SoCs have a UART sub-module. This patch series introduces the driver and the
> > > corresponding binding documentation for this sub-module.
> > >
> > > The DTS patches for adding PRU nodes and enabling PRU UART will be added
> > > in a later v1 version of the series if accepted.
> > >
> > > This driver has been previously tested on the following boards:
> > > am64x SK, am62x SK, and am335x SK boards.
> >
> > Why is this "RFC"? What needs to be done to make it something that you
> > actually feel works properly and should be merged?
>
> Nothing needs to be done IMO, the only reason it was sent as an RFC is
> to get initial thoughts/issues that anyone might have with the driver
> before sending v1.
>
> If none, I will go ahead and send v1. Thanks for your attention Greg.
I have tons of comments, please read my replies before sending a v1.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists