linguini1 commented on code in PR #18837:
URL: https://github.com/apache/nuttx/pull/18837#discussion_r3191476887


##########
drivers/serial/uart_pl011.c:
##########
@@ -1010,67 +724,42 @@ static int pl011_setup(FAR struct uart_dev_s *dev)
  ***************************************************************************/
 
 /***************************************************************************
- * Name: pl011_earlyserialinit
+ * Name: pl011_dev_init
  *
  * Description:
- *   see nuttx/serial/uart_pl011.h
+ *   Initialize a PL011 device with its configuration settings.
  *
- ***************************************************************************/
-
-void pl011_earlyserialinit(void)
-{
-  /* Enable the console UART.  The other UARTs will be initialized if and
-   * when they are first opened.
-   */
-#ifdef CONSOLE_DEV
-  CONSOLE_DEV.isconsole = true;
-  pl011_setup(&CONSOLE_DEV);
-#endif
-}
-
-/***************************************************************************
- * Name: pl011_serialinit
+ * Arguments:
+ *   - dev      The PL011 device struct to initialize
  *
- * Description:
- *   Register serial console and serial ports.  This assumes that
- *   pl011_earlyserialinit was called previously.
+ * Return:
+ *   The `struct uart_dev_s` for registering this PL011 device, or NULL on
+ *   failure.
  *
  ***************************************************************************/
 
-void pl011_serialinit(void)

Review Comment:
   I'm not sure there's a way around that except by maintaining two interfaces 
for PL011 registration and all the old Kconfig options. Plus, I will have to 
add some refactoring for more granular interrupt management.
   
   Let me brainstorm and get back to you, maybe I can keep the init function 
and still remove the PL011-specific Kconfig functions. The main challenge is 
selection of the base addresses and IRQ numbers.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to