From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Judith Mendez <jm@ti.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@baylibre.com>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH RFC 0/2] Introduce PRU UART driver
Date: Fri, 2 May 2025 12:51:17 +0300 [thread overview]
Message-ID: <aBSVld3HKL_M1agq@smile.fi.intel.com> (raw)
In-Reply-To: <406ae5d2-9a4a-47be-9663-d746d9661f1f@ti.com>
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
next prev parent reply other threads:[~2025-05-02 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 0:31 [PATCH RFC 0/2] Introduce PRU UART driver Judith Mendez
2025-05-01 0:31 ` [PATCH RFC 1/2] dt-bindings: serial: add binding documentation for TI PRUSS UART Judith Mendez
2025-05-01 0:31 ` [PATCH RFC 2/2] serial: 8250: Add PRUSS UART driver Judith Mendez
2025-05-01 16:28 ` Andrew Davis
2025-05-08 22:11 ` Judith Mendez
2025-05-02 9:50 ` Andy Shevchenko
2025-05-08 22:09 ` Judith Mendez
2025-05-09 11:43 ` Andy Shevchenko
2025-05-13 0:06 ` Judith Mendez
2025-05-01 5:18 ` [PATCH RFC 0/2] Introduce PRU " Greg Kroah-Hartman
2025-05-01 14:47 ` Judith Mendez
2025-05-02 9:51 ` Andy Shevchenko [this message]
2025-05-02 22:07 ` Judith Mendez
2025-05-02 9:38 ` Andy Shevchenko
2025-05-07 16:31 ` Judith Mendez
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=aBSVld3HKL_M1agq@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hnagalla@ti.com \
--cc=jirislaby@kernel.org \
--cc=jm@ti.com \
--cc=khilman@baylibre.com \
--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