All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@newflow.co.uk>
To: balbi@ti.com
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: rts-gpio DT binding
Date: Wed, 19 Mar 2014 17:02:56 +0000	[thread overview]
Message-ID: <5329CDC0.6010705@newflow.co.uk> (raw)
In-Reply-To: <20140319145957.GB27752@saruman.home>

On 19/03/14 14:59, Felipe Balbi wrote:
> Hi,
> 
> On Wed, Mar 19, 2014 at 09:15:03AM +0000, Mark Jackson wrote:

[snip]

>>
>> Okay ... it comes back to me now.
>>
>> When using RS485 drivers, we're not actually using RTS as a "Ready
>> To Send", we're really using it as an "enable RS485 driver".
>>
>> I just used the "RTS" mnemonic as "we're now wanting to send some
>> data so please now enable the RS485 driver", rather than the normal
>> "I'm ready for your to send me some data".
>>
>> So it's the opposite function.
>>
>> Maybe it was a poor choice of abbreviation ?
>>
>> As I said before, RS485 drivers might have active or active low
>> enables, so we might need to invert the "RTS" polarity.  This is
>> not handled by the hardware RTS signal.
>>
>> Is that a good enough explanation ?
> 
> fair, but considering you can toggle RTS by hand with writes to MCR
> register, I still don't see the need for remuxing the lines as GPIOs.
> 
> Just don't use auto-RTS and toggle the line by hand with MCR, no ?

TBH I hadn't realised you could do that, so I guess you could.

But my solution seems more flexible as it would allow you to add an RTS
signal to UART0 and UART5 which don't have any hardware handshaking lines.

Mark J.

  reply	other threads:[~2014-03-19 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 16:55 rts-gpio DT binding Felipe Balbi
2014-03-18 17:04 ` Mark Jackson
2014-03-18 17:11   ` Felipe Balbi
2014-03-18 17:18     ` Felipe Balbi
2014-03-18 17:22       ` Felipe Balbi
2014-03-19  9:15     ` Mark Jackson
2014-03-19 14:59       ` Felipe Balbi
2014-03-19 17:02         ` Mark Jackson [this message]
2014-03-19 19:04           ` Felipe Balbi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5329CDC0.6010705@newflow.co.uk \
    --to=mpfj-list@newflow.co.uk \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.