Re: [PATCH v5 10/14] serial: pic32_uart: Add PIC32 UART driver
From: Sudeep Holla <hidden>
Date: 2016-04-15 17:28:35
Also in:
linux-mips, linux-serial, lkml
Hi Greg, I just noticed this now. I am having similar issue with MPS2 UART driver posted @[1], hence I am asking here to get some clarification myself. Sorry for replying on very old thread. On Thu, Jan 14, 2016 at 1:15 AM, Joshua Henderson [off-list ref] wrote:
From: Andrei Pistirica <redacted> This adds UART and a serial console driver for Microchip PIC32 class devices. Signed-off-by: Andrei Pistirica <redacted> Signed-off-by: Joshua Henderson <redacted> Cc: Ralf Baechle <ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org>
[...]
quoted hunk ↗ jump to hunk
diff --git a/include/uapi/linux/serial_core.h b/include/uapi/linux/serial_core.h index 93ba148..9df0a98 100644 --- a/include/uapi/linux/serial_core.h +++ b/include/uapi/linux/serial_core.h@@ -261,4 +261,7 @@ /* STM32 USART */ #define PORT_STM32 113 +/* Microchip PIC32 UART */ +#define PORT_PIC32 114
This was posted before v4.6-rc1 similar to MPS2 UART and has taken port# 114 for it. However MVEBU UART obtained 114 with v4.6-rc1 And MPS2 UART was assigned 115 when it got revised/reposted. I also see this patch in linux-next with 114 itself as its port number. So the allocation of port number needs to be resolved before it gets merged or it's OK to wait for v4.7-rc1 ? If it's former, can PORT_PIC32 take 116 as the latest post of MPS2 assigned it 115 and I have pulled the same to take it via arm-soc. I am fine with any solution, just want to be notified if I need to take any action. Regards, Sudeep [1] http://www.spinics.net/lists/devicetree/msg120727.html