From: Jon Ringle <jon@ringle.org>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: jon@ringle.org, 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 07:50:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1403100744230.23103@jringle-ubuntu> (raw)
In-Reply-To: <1394434945.519725450@f256.i.mail.ru>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1031 bytes --]
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?
Any thoughts as to the latency issue I report?
Thanks.
Regards,
Jon
next prev parent reply other threads:[~2014-03-10 11:50 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 [this message]
2014-03-10 14:20 ` One Thousand Gnomes
2014-03-10 16:14 ` Alexander Shiyan
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=alpine.DEB.2.02.1403100744230.23103@jringle-ubuntu \
--to=jon@ringle.org \
--cc=gregkh@linuxfoundation.org \
--cc=jringle@gridpoint.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=shc_work@mail.ru \
/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®