All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Alexandre Coffignal <alexandre.coffignal@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] assert RTS signal during transmit in EIA-485 half duplex mode for 16550A compatible controllers.
Date: Thu, 21 Jan 2010 11:21:56 +0100	[thread overview]
Message-ID: <4B582AC4.5030104@domain.hid> (raw)
In-Reply-To: <4B58233A.4070708@domain.hid>

Alexandre Coffignal wrote:
> Hello,
> 
> Thanks you for your response.
> 
> I used this patch to communicate with a slave equipment in rs485 (modbus
> protocol). The data is transmitted over a 2-wire twisted pair bus.
> Master initiates all communication activity, by sending data. To do this
> it must set RTS line to high state during all it's transmission. Before
> slave answer, master must lower the RTS line.

Will the slave wait on the deassertion of RTS? Or what will happen if
RTS is still high and the slave starts its answer?

> 
> my slave equipment answer in less than 200us, so i must know when xmit
> is completing to lower the RTS line
> 
> An extension to RTSER_RTIOC_WAIT_EVENT may be a good solution but do you
> know if an extension to RTSER_RTIOC_WAIT_EVENT can guarantee this timing?
> 

Given a proper platform (check its capabilities with the latency or the
irqbench test), yes. It's a myth that such things can only be done in
kernel space.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2010-01-21 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 14:29 [Xenomai-core] [PATCH] assert RTS signal during transmit in EIA-485 half duplex mode for 16550A compatible controllers Alexandre Coffignal
2010-01-21  8:57 ` Jan Kiszka
2010-01-21  9:49   ` Alexandre Coffignal
2010-01-21 10:21     ` Jan Kiszka [this message]
2010-01-21 10:36       ` Alexandre Coffignal
2010-01-21 11:18         ` Jan Kiszka

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=4B582AC4.5030104@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=alexandre.coffignal@domain.hid \
    --cc=xenomai@xenomai.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.