From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mxct.zte.com.cn (mxct.zte.com.cn [183.62.165.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 356F73E51C8; Wed, 13 May 2026 08:52:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=183.62.165.209 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778662370; cv=none; b=Zx22vWPjomCGrHqeDH3XOmZ0mGMRyYXXc3og6jI/cIA8LImy03sxaXucuUV4q3gfckd3jWSK/2148ncB+LambB+5wToOBJcS0gUHUF5J9RSiEtbWSE0vLL/jzlcUHYy4ST1hKqY17sX5k2VlGXs6Xjq8/QUVZO7kVcn32AXrXpA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778662370; c=relaxed/simple; bh=YzWmPufUuxBYwQhgzEoT45s30WChmOdVZQRn6SfYa5w=; h=Message-Id:References:Date:Mime-Version:From:To:Cc:Subject: Content-Type; b=OAdBOzYUT4zicmzcs3+5KXpEzz8MO6U7/7pEDrgOdqjcVh5q1aXP+y+9YoH1GyinlgHY60WT/yDHkuqVCTpNr00s+63waVEQDkn2e/qcrJ1InfMo8Mnrbyg1SG2ornJZsZ0pKdlDnvea3j3FqcKjFpH0Vz7lyoBL3HERxstAtkQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zte.com.cn; spf=pass smtp.mailfrom=zte.com.cn; arc=none smtp.client-ip=183.62.165.209 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zte.com.cn Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zte.com.cn Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4gFnKL53nsz51Sdp; Wed, 13 May 2026 16:52:38 +0800 (CST) Received: (from root@localhost) by mse-fl2.zte.com.cn id 64D8qdE5044241; Wed, 13 May 2026 16:52:39 +0800 (+08) (envelope-from liu.qingtao2@zte.com.cn) Message-Id: <202605130852.64D8qdE5044241@mse-fl2.zte.com.cn> Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl2.zte.com.cn with SMTP id 64D8iPxu027365; Wed, 13 May 2026 16:44:25 +0800 (+08) (envelope-from liu.qingtao2@zte.com.cn) Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid204; Wed, 13 May 2026 16:44:27 +0800 (CST) X-Zmail-TransId: 2aff6a0439eb2c1-f7422 X-Mailer: Zmail v1.0 References: 20260213093334.9217-1-qtliu@mail.ustc.edu.cn,20260213093334.9217-3-qtliu@mail.ustc.edu.cn,2026031201-dense-unrefined-7bf5@gregkh,202605061057582963JK3yxV44CRPCHHVos6kc@zte.com.cn Date: Wed, 13 May 2026 16:44:27 +0800 (CST) Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 From: To: Cc: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: =?UTF-8?B?UmU6IFtQQVRDSCB2MSAyLzJdIExSVyBVQVJUOiBzZXJpYWw6IGFkZCBkcml2ZXIgZm9yIHRoZSBMUlcgVUFSVA==?= Content-Type: text/plain; charset="UTF-8" X-MAIL:mse-fl2.zte.com.cn 64D8qdE5044241 X-MSS: AUDITRELEASE@mse-fl2.zte.com.cn X-TLS: YES X-SPF-DOMAIN: zte.com.cn X-ENVELOPE-SENDER: liu.qingtao2@zte.com.cn X-SPF: None X-SOURCE-IP: 10.5.228.133 unknown Wed, 13 May 2026 16:52:38 +0800 X-Fangmail-Anti-Spam-Filtered: true X-Fangmail-MID-QID: 6A043BD6.001/4gFnKL53nsz51Sdp > On Fri, Feb 13, 2026 at 05:33:34PM +0800, LiuQingtao wrote: > > From: Wenhong Liu > > > > This commit introduces a serial driver for the LRW UART controller > > > > Key features implemented: > > - Support for FIFO mode (16-byte depth) > > - Baud rate configuration > > - Standard asynchronous communication formats: > > * Data bits: 5, 6, 7, 8, 9 bits > > * Parity: odd, even, fixed, none > > * Stop bits: 1 or 2 bits > > - Hardware flow control (RTS/CTS) > > - Multiple interrupt reporting mechanisms > > > > Signed-off-by: Wenhong Liu > > Signed-off-by: Qingtao Liu > > --- > > MAINTAINERS | 3 + > > drivers/tty/serial/Kconfig | 33 + > > drivers/tty/serial/Makefile | 1 + > > drivers/tty/serial/lrw_uart.c | 2822 ++++++++++++++++++++++++++++++ > > This really is a totally new uart? No relation to any existing devices > at all? Why would that be created? > > Anyway, this doesn't seem to build properly, how was it tested? Yes, it`s a new uart for lrx SoC. The lrx SoC with its related docs will be released soon. The uart TX & RX test environment: 1.Kernel: linux-next, commit 4cd074ae20bbcc293bbbce9163abe99d68ae6ae0(Tue May 5 14:57:23 2026 +0200), with CONFIG_SERIAL_LRX_UART and SERIAL_LRX_UART_CONSOLE selected. 2.GCC: 14.1.0. 3.SoC: lrx SoC. > > --- a/include/uapi/linux/serial_core.h > > +++ b/include/uapi/linux/serial_core.h > > @@ -231,6 +231,9 @@ > > /* Sunplus UART */ > > #define PORT_SUNPLUS 123 > > > > +/* LRW UART */ > > +#define PORT_LRW 124 > > Why is this id needed? > > thanks, > > greg k-h Thanks for notice. This id is not needed actually. According to https://lore.kernel.org/all/20231008001804.889727-1-jcmvbkbc@gmail.com/, the specific type of the port is not important to the userspace.