[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42864886e6d5cf11b6ab817f57008611@vanmierlo.com>
Date: Fri, 13 Oct 2023 13:17:37 +0200
From: m.brock@...mierlo.com
To: Rob Herring <robh@...nel.org>
Cc: Manikanta Guntupalli <manikanta.guntupalli@....com>, git@....com,
michal.simek@....com, gregkh@...uxfoundation.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
linux-serial@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, jirislaby@...nel.org,
linux-arm-kernel@...ts.infradead.org, radhey.shyam.pandey@....com,
srinivas.goud@....com, shubhrajyoti.datta@....com,
manion05gk@...il.com
Subject: Re: [PATCH V2 1/2] dt-bindings: Add optional gpio property to uartps
node to support rs485
Rob Herring wrote on 2023-10-12 22:51:
>> How about introducing an rs485 generic gpios property instead of xlnx
>> private one? See also rs485-term-gpios and rs485-rx-during-tx-gpios.
>>
>> Also note that every kernel driver expects to use RTS for this
>> purpose.
>> So why not give this driver the option to choose a gpio instead of its
>> native RTS? And from there on use the rts route?
>> What if someone wants to use normal (non-rs485) RTS on a GPIO instead
>> of the native pin?
>>
>> @Rob Herring
>> I am curious to know how the rs485 maintainers look at this.
>
> Ask them.
Funny, your name is the only one listed under the maintainers in
Documentation/devicetree/bindings/serial/rs485.yaml
And there is no mention of (RS-)485 in MAINTAINERS.
> We already have 'rts-gpios'. If that's what's always used, then perhaps
> we should use that in the RS485 case too?
>
> Rob
Sounds like a good idea.
Maarten
Powered by blists - more mailing lists