From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754652AbbICTD3 (ORCPT ); Thu, 3 Sep 2015 15:03:29 -0400 Received: from gloria.sntech.de ([95.129.55.99]:46023 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751332AbbICTD1 (ORCPT ); Thu, 3 Sep 2015 15:03:27 -0400 From: Heiko Stuebner To: Alexandru M Stan Cc: Romain Perier , FUKAUMI Naoki , Neil Hendin , Douglas Anderson , Jeffy Chen , Caesar Wang , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 0/2] ARM: dts: rockchip: pull up cts lines Date: Thu, 03 Sep 2015 21:03:15 +0200 Message-ID: <2685164.GZh6IdR1jF@phil> User-Agent: KMail/4.14.1 (Linux/4.1.0-1-amd64; KDE/4.14.2; x86_64; ; ) In-Reply-To: <1441236479-4941-1-git-send-email-amstan@chromium.org> References: <1441236479-4941-1-git-send-email-amstan@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Alex, Am Mittwoch, 2. September 2015, 16:27:57 schrieb Alexandru M Stan: > The flow control lines from a user accessible UART are optional, > the user might not have anything connected to those pins. > In order to prevent random interrupts happening and noise affecting > the cts pin should be pulled up. > > The only boards affected (that care about uart*_cts ) are the veyron > chromeos devices and the firefly. Veyron already has something like that, > which I now have to remove in the second patch. Firefly uses uart0_cts > for the wifi chip communications, same thing as veyron, so it should be > fine having it. applied both to my dts branch for 4.4 with Doug's Review-tag (Currently only on github and becomes really public after 4.3-rc1) Heiko