From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6195FC88CB6 for ; Tue, 13 Jun 2023 10:30:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=IVljTfeohWB2WeFUoPanMZ2h2jZKsGC1gQeqM/uaC3I=; b=4g4YBfie5XPe9i KYT2iUpo1esoG6Lnyqds+6DSSP7jRjr3YDDrVbBLWPdjq3fQTm+YWMkM1kN1qmDf4Lt3ERhoF+QNc /uZSig2j4yJ78bqXgxn17FQQVkCkm0sl2djhCbJozq9LZERZD1FTBzB+KyBgYO2U/sTRrIcDyWR/b QcceycJQ++bpdEwnXDSzik4gha1+XI5IeIH4ILr2sYOyatBE9uGrOXXlX0hBYJ3AABsUbXjNFJSsD VDb3Y0NlhEZGu+7UFBq3uGItrSn87ti+J1PP8ybK0shQ0hiB7bajueLcyk3iBAcPpSPaBMrw1OUl2 75y0m4YV3zEVBO+Rzt9A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1q91HS-007euB-1D; Tue, 13 Jun 2023 10:29:42 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1q91HQ-007etU-0m for linux-arm-kernel@lists.infradead.org; Tue, 13 Jun 2023 10:29:41 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B9BD563481; Tue, 13 Jun 2023 10:29:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A4FA7C4339B; Tue, 13 Jun 2023 10:29:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1686652179; bh=GKjykxi8jkpJPrEh4DwtTX4rkA8LohqIze6xn3gvCgg=; h=Date:From:To:List-Id:Cc:Subject:References:In-Reply-To:From; b=KrHiw4yGlWzLr+Y0L8kgwzDfaDjiz6V36vUT6Iu3GS3yBWOvnqdGIc8k+ZAazWNdw GiVI06RIJFsN4Cup5bm6FxEhcEKNjFziI0RZfXPo5HB4xmvglnOW3wvtexlp5N6s1n e1Ep8Orhyb6ZT7tsfJeR+35txiJzQfFBl+Ccx3mU= Date: Tue, 13 Jun 2023 12:29:36 +0200 From: Greg KH To: Jacky Huang Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, lee@kernel.org, mturquette@baylibre.com, sboyd@kernel.org, p.zabel@pengutronix.de, jirislaby@kernel.org, tmaimon77@gmail.com, catalin.marinas@arm.com, will@kernel.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-serial@vger.kernel.org, arnd@arndb.de, soc@kernel.org, schung@nuvoton.com, mjchen@nuvoton.com, Jacky Huang Subject: Re: [PATCH v14 1/1] tty: serial: Add Nuvoton ma35d1 serial driver support Message-ID: <2023061325-distant-gaffe-8871@gregkh> References: <20230612025355.547871-1-ychuang570808@gmail.com> <20230612025355.547871-2-ychuang570808@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230612025355.547871-2-ychuang570808@gmail.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230613_032940_324592_2D07BFEC X-CRM114-Status: GOOD ( 10.75 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Jun 12, 2023 at 02:53:55AM +0000, Jacky Huang wrote: > From: Jacky Huang > > This adds UART and console driver for Nuvoton ma35d1 Soc. > It supports full-duplex communication, FIFO control, and > hardware flow control. You don't specify here what your tty device name is going to be, why? It's not written anywhere, is that intentional? Same for your tty major/minor, what numbers are you using that might also be in use by a different device in the system? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel