From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christian Melki <christian.melki@ericsson.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: 8250.c: Generic support for RTS disabling once shiftreg and fifo is empty. (low latency RS485 etc).
Date: Fri, 27 Apr 2012 10:02:07 +0100 [thread overview]
Message-ID: <20120427100207.48c04654@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1346E68D3A5B2043907CF4BF466383411A07E01021@ESESSCMS0353.eemea.ericsson.se>
On Fri, 27 Apr 2012 08:23:23 +0200
Christian Melki <christian.melki@ericsson.com> wrote:
> Hi.
>
> I have written a patch for 8250.c that introduces a new ioctl to tell the uart driver to shift disable RTS when uart has been completely emptied.
> This idea is to set the ioctl once the master is finished and wants to shift the bus.
> We needed this to be in the kernel since we have very little time to shift RTS according to the implemented protocol on top of RS485.
>
> Is there any interest in the community for such a behavior?
We have a set of RS485 ioctls that provide a standard interface for
assisting RS485 handling. The interface should probably use those if
possible.
> The patch is a little ugly right now. It busywaits a maximum amount of time for the shift register to become empty. I don't know how to do it without introducing a latency that is more than our max RTS time shift requirement (50us). I think it could be useful with a generic 8250.c support for this.
We've hit the same hardware limit in a couple of other places where you
end up having to spin on the last byte. I don't think it's a problem
providing it is only triggered when trying to do the RS485 bits with that
feature.
Alan
next prev parent reply other threads:[~2012-04-27 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 6:23 8250.c: Generic support for RTS disabling once shiftreg and fifo is empty. (low latency RS485 etc) Christian Melki
2012-04-27 9:02 ` Alan Cox [this message]
2012-04-30 7:05 ` Christian Melki
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=20120427100207.48c04654@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=christian.melki@ericsson.com \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox