Received-SPF: pass (google.com: domain of linux-kernel+bounces-40597-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Message-ID: <098216ce-50b3-43e4-ad1a-42228c58b761@gmx.de>
Date: Fri, 26 Jan 2024 20:58:47 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v5 2/6] serial: 8250: Support separate rs485 rx-enable
 GPIO
Content-Language: en-US
To: Farouk Bouabid <farouk.bouabid@theobroma-systems.com>,
 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
 Jiri Slaby <jirislaby@kernel.org>, Rob Herring <robh+dt@kernel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
 Conor Dooley <conor+dt@kernel.org>, Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>, linux-kernel@vger.kernel.org,
 linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
 linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org,
 quentin.schulz@theobroma-systems.com,
 Heiko Stuebner <heiko.stuebner@cherry.de>
References: <20240126-dev-rx-enable-v5-0-5d934eda05ca@theobroma-systems.com>
 <20240126-dev-rx-enable-v5-2-5d934eda05ca@theobroma-systems.com>
From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
In-Reply-To: <20240126-dev-rx-enable-v5-2-5d934eda05ca@theobroma-systems.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
UI-OutboundReport: notjunk:1;M01:P0:gDeFAUjQu88=;LyErTh1wbmp4ZgUkN2hipgHtJip
 Doasra58RavpqzDzDkRpATvXg2UWTEIs8FY3wGifrBGjoG8OZ7XWkAWj7S7d/CqD8+XJozQgg
 GXbN1lSKKAMwvlFtJwrC+mFYX8f9AMByLl2inW33lRUHV9zt/ozkAczOIukrBYMdJzhUfK8bL
 EIGpYZwCLKi0NxwE8nq/9OkiEXlqk0+paRlr8cewb4fRcpOIan4Anozb6PqsnRgPM7QcZM1w5
 phyRqULFK7WdO06b0nSRXe8Z69HjxoqSFMIDRgm7ZqOg/KsAzJwjqvNSNTa8A4WjuHRUWZVKo
 c9TO5w3UiF/SWoftSN1wEIps/d5YTOJK5ouPrcGnKItZgekoSQO0Z5q2ZX9i7UoEClgtz9sMF
 M7KlxJ6CU7jSybRv7cdD+jrEFeYH4TnHVhHqOxpmEmyCw1K2h9QtRzGbZPIMxOGkjVI9avub4
 XPM72OdUCP/zGxht5V6HyqM5VnyXRG/FKVkLjgIMs5E934N0qA6sCIsR68mnHe59QVZSFLSBD
 y4JQlMFaKZXKTyK5oKXiwFZ3z21/pzKdYxP/bjUhhR8tZl2Iw1tiRXSmUShk3VGHgy/6a3Sqo
 RrvNboGzXBaKmIGtWy+0pFe/Vf6zw+DqHQ9DeMI/hKuUtUQzdeXJDkD2xoPe96RBFtsaFOKsf
 Yu1eHFHcKnaYFfZ8Mb1pEmUTA3pxvgARx+kYLJcV44D6tr+oVHzAc1D0QezjC+PLc+7yXAw+k
 G8JHOYNegYJQvUWoE+gaYbLp8iuUTJdGnbMza8NU1YRui2utEERA+ahnOvfgMNDHBL0vjhVVz
 B4Qls2sbQGt/NGT3zpmWbYlj7mVj+Bi6Xcil1giY1tGYTc4ZKebGHZYJPk5sApQEJRazuVwRw
 pwm/TpmUMJawXcDQ7pUOztJSnzRN4QDqO3ZRdvZ7D4al6Lh+479MaZHfTDUiC0zzObA4F5qDd
 SW2XOQ==


Hi,

On 26.01.24 18:27, Farouk Bouabid wrote:
> From: Heiko Stuebner <heiko.stuebner@cherry.de>
>
> The RE signal is used to control the duplex mode of transmissions,
> aka receiving data while sending in full duplex mode, while stopping
> receiving data in half-duplex mode.
>
> On a number of boards the !RE signal is tied to ground so reception
> is always enabled except if the UART allows disabling the receiver.
> This can be taken advantage of to implement half-duplex mode - like
> done on 8250_bcm2835aux.
>
> Another solution is to tie !RE to RTS always forcing half-duplex mode.
>
> And finally there is the option to control the RE signal separately,
> like done here by introducing a new rs485-specific gpio that can be
> set depending on the RX_DURING_TX setting in the common em485 callbacks.
>

we just added the rx_during_tx_gpio to the serial core.
Why cant you use this GPIO for your purpose?

Regards,
Lino