Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755216AbbL0NnJ (ORCPT ); Sun, 27 Dec 2015 08:43:09 -0500 Received: from mail-ob0-f169.google.com ([209.85.214.169]:33399 "EHLO mail-ob0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754747AbbL0NnI (ORCPT ); Sun, 27 Dec 2015 08:43:08 -0500 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 27 Dec 2015 16:43:07 +0300 Message-ID: Subject: Re: GPIO-driven RTS on TI hardware with 8250_omap driver From: =?UTF-8?B?0JjQu9GM0Y/RgSDQk9Cw0YHQsNC90L7Qsg==?= To: "Matwey V. Kornilov" Cc: Andy Shevchenko , Peter Hurley , Russell King , linux-kernel@vger.kernel.org, linux-arm Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 929 Lines: 22 Hi Matwey, 2015-12-27 16:14 GMT+03:00 Matwey V. Kornilov : > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/