linux-kernel - Re: [PATCH v2 0/2] ARM: dts: rockchip: pull up cts lines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2685164.GZh6IdR1jF@phil>
Date:	Thu, 03 Sep 2015 21:03:15 +0200
From:	Heiko Stuebner <heiko@...ech.de>
To:	Alexandru M Stan <amstan@...omium.org>
Cc:	Romain Perier <romain.perier@...il.com>,
	FUKAUMI Naoki <naobsd@...il.com>,
	Neil Hendin <nhendin@...omium.org>,
	Douglas Anderson <dianders@...omium.org>,
	Jeffy Chen <jeffy.chen@...k-chips.com>,
	Caesar Wang <wxt@...k-chips.com>, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 0/2] ARM: dts: rockchip: pull up cts lines

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/