From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH] Revert "serial: max310x: rework RX interrupt handling"
Date: Thu, 18 Feb 2021 07:51:27 +0100 [thread overview]
Message-ID: <20210218075127.5023d878@windsurf.home> (raw)
In-Reply-To: <20210218065553.864bbf0cc2b3d398504c5b95@mail.ru>
Hello,
On Thu, 18 Feb 2021 06:55:53 +0300
Alexander Shiyan <shc_work@mail.ru> wrote:
> I wrote a little inaccurately, I did not mean a physical interface RS-485,
> but rather a time-critical MODBUS protocol. (In our case it used on top on RS-485).
OK, so it's not about 232 vs 485.
> I do not know how best to solve this problem, it may be an additional parameter
> for the devicetree, but in this case it is not clear how to manage it if the
> devicetree is not used ...
No, it cannot be a parameter in the Device Tree, as what we're talking
about is not hardware description, but configuration of the hardware
for particular use cases.
> This could be a Kconfig item (but something's not very good either).
> Probably the best solution is to adapt some kind of IOCTL (or control via SYSFS).
Greg, Jiri, perhaps you could comment on what would be the appropriate
user-space interface to use or add to be able to configure such aspects
of a UART controller ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-02-18 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 8:06 [PATCH] Revert "serial: max310x: rework RX interrupt handling" Alexander Shiyan
2021-02-17 22:53 ` Thomas Petazzoni
2021-02-18 3:55 ` Alexander Shiyan
2021-02-18 6:51 ` Thomas Petazzoni [this message]
2021-02-18 7:11 ` Greg Kroah-Hartman
2021-02-18 7:20 ` Thomas Petazzoni
2021-02-18 8:07 ` Greg Kroah-Hartman
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=20210218075127.5023d878@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@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 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.