linux-kernel - Re: GPIO-driven RTS on TI hardware with 8250

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEo2pzvg3W9zVyxKMAH0QwfSZLufc76o=DiN5QT0hqcm8cCAFA@mail.gmail.com>
Date:	Sun, 27 Dec 2015 16:43:07 +0300
From:	Ильяс Гасанов 
	<torso.nafi@...il.com>
To:	"Matwey V. Kornilov" <matwey@....msu.ru>
Cc:	Andy Shevchenko <andy.shevchenko@...il.com>,
	Peter Hurley <peter@...leysoftware.com>,
	Russell King <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org,
	linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>
Subject: Re: GPIO-driven RTS on TI hardware with 8250_omap driver

Hi Matwey,

2015-12-27 16:14 GMT+03:00 Matwey V. Kornilov <matwey@....msu.ru>:
> The half of what is described here are implemented in my patches.
> But I cannot understand the other half. Each of six AM335x UARTs has
> RTS/CTS pins which are controlled by pinmux in device tree, no magic
> required here.

The problem here is, the appliance schematics are already designed in
such way that pins which can be configured as "native" RTS are not
used for RS485 control - the ones that are though may only be used as
GPIO flipped by software on transmission start/end for that purpose.
We simply cannot change the schematics on production because of this
issue alone.

Regards,
Ilyas G.
--
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/