From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Jon Ringle" <jon@ringle.org>
Cc: gregkh@linuxfoundation.org, jslaby@suse.cz,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
"Jon Ringle" <jringle@gridpoint.com>
Subject: Re: [PATCH] RFC: WIP: sc16is7xx [v0.4]
Date: Mon, 10 Mar 2014 20:14:36 +0400 [thread overview]
Message-ID: <1394468076.709210210@f170.i.mail.ru> (raw)
In-Reply-To: <alpine.DEB.2.02.1403100744230.23103@jringle-ubuntu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1929 bytes --]
ÐонеделÑник, 10 маÑÑа 2014, 7:50 -04:00 Ð¾Ñ Jon Ringle <jon@ringle.org>:
>
> On Mon, 10 Mar 2014, Alexander Shiyan wrote:
>
> > ÐонеделÑник, 10 маÑÑа 2014, 2:26 -04:00 Ð¾Ñ jon@ringle.org:
> > > From: Jon Ringle <jringle@gridpoint.com>
> > ...
> > > +config SERIAL_SC16IS7XX
> > > + tristate "SC16IS7xx RS485 serial support"
> > > + select SERIAL_CORE
> > > + default n
> > > + help
> > > + This selects support for SC16IS7xx for use as a RS485 serial port
> >
> > Documentation says:
> > The SC16IS740/750/760 is a slave I²C-bus/SPI interface to a single-channel
> > high performance UART.
> > ...
> > The SC16IS740/750/760 also provides additional advanced features such
> > as auto hardware and software flow control, automatic RS-485 support...
> >
> > So why do you position this chip as RS485 only? Automatic direction for
> > RS485 is just a feature as an addition for standart UART.
>
> You're right. This is just how we are using the chip in our board. Would a
> configuration flag in platform_data make sense to use the auto rs485
> direction?
You don't need a flag, just use IOCTLs.
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/drivers/tty/serial/max310x.c?id=55367c620aed6bc27a82bb1763366931d7f2ee66
> Any thoughts as to the latency issue I report?
I do not understand why you chose the sccnxp driver as a template.
Use as a template max310x driver from linux-next branch.
I'm sure it will be better.
About latency.
I'm not exactly understand the problem, but I can say the following:
Since you're using the I2C bus, maximum UART daudrate can be
predicted from the I2C bus bandwidth.
Count how many I2C clocks spent on reception and transmission
of one byte through UART.
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-03-10 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 6:26 jon
2014-03-10 7:02 ` Alexander Shiyan
2014-03-10 11:50 ` Jon Ringle
2014-03-10 14:20 ` One Thousand Gnomes
2014-03-10 16:14 ` Alexander Shiyan [this message]
2014-03-11 18:20 ` Jon Ringle
2014-03-11 18:44 ` Jon Ringle
2014-03-10 14:17 ` One Thousand Gnomes
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=1394468076.709210210@f170.i.mail.ru \
--to=shc_work@mail.ru \
--cc=gregkh@linuxfoundation.org \
--cc=jon@ringle.org \
--cc=jringle@gridpoint.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®