From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751554AbdAYLkJ (ORCPT ); Wed, 25 Jan 2017 06:40:09 -0500 Received: from mail-wm0-f51.google.com ([74.125.82.51]:36851 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751468AbdAYLkG (ORCPT ); Wed, 25 Jan 2017 06:40:06 -0500 Date: Wed, 25 Jan 2017 11:40:02 +0000 From: Peter Griffin To: Lee Jones Cc: gregkh@linuxfoundation.org, jslaby@suse.com, linux-serial@vger.kernel.org, robh+dt@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel@stlinux.com Subject: Re: [STLinux Kernel] [PATCH 8/8] ARM: dts: STiH407-family: Enable HW flow-control Message-ID: <20170125114002.GG5680@griffinp-ThinkPad-X1-Carbon-2nd> References: <20170124134310.27512-1-lee.jones@linaro.org> <20170124134310.27512-9-lee.jones@linaro.org> <20170125105912.GA5680@griffinp-ThinkPad-X1-Carbon-2nd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170125105912.GA5680@griffinp-ThinkPad-X1-Carbon-2nd> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 25 Jan 2017, Peter Griffin wrote: > Hi Lee, > > On Tue, 24 Jan 2017, Lee Jones wrote: > > > Hardware flow-control capability must be specified at a platform > > level in order to inform the ASC driver that the platform is capable > > (i.e. are the lines wired up, etc). STiH4{07,10} devices are indeed > > capable, so let's provide the property. > > > > Signed-off-by: Lee Jones > > --- > > arch/arm/boot/dts/stih407-family.dtsi | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/arch/arm/boot/dts/stih407-family.dtsi b/arch/arm/boot/dts/stih407-family.dtsi > > index 9789978..7ada8ea 100644 > > --- a/arch/arm/boot/dts/stih407-family.dtsi > > +++ b/arch/arm/boot/dts/stih407-family.dtsi > > @@ -226,7 +226,7 @@ > > pinctrl-0 = <&pinctrl_serial0_flowctrl>; > > pinctrl-1 = <&pinctrl_serial0>; > > clocks = <&clk_s_c0_flexgen CLK_EXT2F_A9>; > > - > > + st,hw-flow-control; > > There is a generic serial binding for this already. As this ST property > hasn't been used upstream, it seems like it would be worth dropping it > and switching to the generic uart-has-rtscts one. > > See Documentation/devicetree/bindings/serial/serial.txt > > - uart-has-rtscts: The presence of this property indicates that the > UART has dedicated lines for RTS/CTS hardware flow control, and that > they are available for use (wired and enabled by pinmux configuration). > This depends on both the UART hardware and the board wiring. > Note that this property is mutually-exclusive with "cts-gpios" and > "rts-gpios" above. Thinking some more this generic binding definition is a bit restrictive, particularly the "Note that this property is mutually-exclusive with "cts-gpios" and "rts-gpios"" part. As with this series we will have dynamic on-the-fly changing from hw flow control to gpio control for other configs which the HW IP doesn't support. IMO the uart-has-rtscts definition should be updated to reflect that they can be used together in certain circumstances. regards, Peter.