[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <406ae5d2-9a4a-47be-9663-d746d9661f1f@ti.com>
Date: Thu, 1 May 2025 09:47:34 -0500
From: Judith Mendez <jm@...com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
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
Hi Greg,
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.
~ Judith
Powered by blists - more mailing lists