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. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
