public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jochen Mades <jochen@mades.net>
Cc: linux-serial@vger.kernel.org
Subject: Re: Extending serial port linux driver to toggle RS485 direction pin (GPIO)
Date: Wed, 3 Nov 2021 09:23:54 +0100	[thread overview]
Message-ID: <YYJHGhzdnwlu6y5k@kroah.com> (raw)
In-Reply-To: <527160377.1225435.1635924219001@webmail.strato.com>

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Wed, Nov 03, 2021 at 08:23:38AM +0100, Jochen Mades wrote:
> Hi Greg,
> 
> thanks for your fast reply. I checked the sources you mentioned below, that helps a bit..
> 
> Could you please give me some more background what you mean with your question:
> > You could do much the same in the pl011_rs485_tx_start() function when
> > SER_RS485_RX_DURING_TX and SER_RS485_RTS_ON_SEND are checked, right?
> 
> Is there already a concept for RS485 drivers?

Yes, RS485 drivers control lines like you are looking for in order to
properly handle the protocol requirements.

> ...or where to find "pl011_rs485_tx_start()"?

Look in the kernel source tree for that function, that's in the driver
you were looking to modify, right?

thanks,

greg k-h

  reply	other threads:[~2021-11-03  8:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 17:55 Extending serial port linux driver to toggle RS485 direction pin (GPIO) Jochen
2021-11-02 18:58 ` Greg KH
2021-11-03  7:23   ` Jochen Mades
2021-11-03  8:23     ` Greg KH [this message]
2021-11-16  6:43   ` Jochen Mades
2021-11-16  8:28     ` Greg KH
2021-11-16 11:47       ` Jochen Mades
2021-11-16 14:21         ` Greg KH

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=YYJHGhzdnwlu6y5k@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jochen@mades.net \
    --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