public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Panin <pazke@donpac.ru>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SIIG 8-port serial boards support
Date: Fri, 17 Feb 2006 14:39:42 +0300	[thread overview]
Message-ID: <20060217113942.GA30787@pazke> (raw)
In-Reply-To: <20060203092435.GA30738@flint.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]

On 034, 02 03, 2006 at 09:24:36 +0000, Russell King wrote:
> On Fri, Feb 03, 2006 at 12:13:08PM +0300, Andrey Panin wrote:
> > On 033, 02 02, 2006 at 08:17:35 +0000, Russell King wrote:
> > > As I've said many a time, we need a generic way to set different hand-
> > > shaking modes.  I've suggested using some spare bits in termios in the
> > > past, but nothing ever came of that - folk lose interest at that point.

No wonder they do. Extra bits are not a problem, but for 8250.c we need some
way to glue subdrivers with serial8250_set_termios(). Callback in uart_port
structure ?

> > IMHO there is no need to userspace visible changes to support RS485 on
> > these cards, because some of them are RS485 only and some have jumpers
> > for individual ports.  There is nothing that userspace can configure.
> > We only need to set two bits in ACR according to card type and jumper
> > settings and UART will drive RS485 transiever transparently.
> 
> In this particular case you may be right, but I'm looking at the bigger
> picture, where plain 16550's may be used for RS485.

Common way to use plain 16550 for RS485 is to wire transiever to the RTS
and force userspace to use RTS/CTS flow control. I doubt there are many 
other sane way to do it.

> There are drivers which want to implement their own private ioctl to
> enable RS485 mode.  What I'm saying is that we should have one solution,
> not multiple solutions to this problem. When we have such a solution,
> your RS485 card will be able to fit into that model.

But it will need a way to pass ACR value anyway :)

-- 
Andrey Panin		| Linux and UNIX system administrator
pazke@donpac.ru		| PGP key: wwwkeys.pgp.net

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-02-17 11:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24  8:25 [PATCH] SIIG 8-port serial boards support Andrey Panin
2006-01-24 21:01 ` Russell King
2006-02-02 10:26   ` Russell King
2006-02-02 13:27     ` Andrey Panin
     [not found]       ` <20060202201734.GA17329@flint.arm.linux.org.uk>
2006-02-03  9:13         ` Andrey Panin
2006-02-03  9:24           ` Russell King
2006-02-17 11:39             ` Andrey Panin [this message]
2006-02-17 20:02               ` Russell King
2006-02-17 20:14                 ` Russell King
2006-02-17 21:27                 ` Paul Fulghum
2006-02-17 21:39                   ` Russell King
2006-02-17 21:52                     ` Paul Fulghum
  -- strict thread matches above, loose matches on Subject: below --
2006-02-17 20:32 Kilau, Scott
2006-02-17 21:26 ` Russell King
2006-02-17 22:25 linux
2006-02-17 22:39 ` Russell King
2006-02-17 23:11   ` Paul Fulghum

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=20060217113942.GA30787@pazke \
    --to=pazke@donpac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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