linux-kernel - Re: [PATCH RFC 0/2] Introduce PRU UART driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025050103-graduate-anteater-e6f6@gregkh>
Date: Thu, 1 May 2025 07:18:27 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Judith Mendez <jm@...com>
Cc: Kevin Hilman <khilman@...libre.com>, Jiri Slaby <jirislaby@...nel.org>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	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 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