From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Judith Mendez <jm@ti.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
Jiri Slaby <jirislaby@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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: Thu, 1 May 2025 07:18:27 +0200 [thread overview]
Message-ID: <2025050103-graduate-anteater-e6f6@gregkh> (raw)
In-Reply-To: <20250501003113.1609342-1-jm@ti.com>
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?
thanks,
greg k-h
next prev parent reply other threads:[~2025-05-01 5:20 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 ` Greg Kroah-Hartman [this message]
2025-05-01 14:47 ` [PATCH RFC 0/2] Introduce PRU " Judith Mendez
2025-05-02 9:51 ` Andy Shevchenko
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=2025050103-graduate-anteater-e6f6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--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