From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: Wander Lairson Costa <wander@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org
Cc: "Rostislav Lisový" <lisovy@gmail.com>,
"Oliver Hartkopp" <socketcan@hartkopp.net>,
"Jiri Slaby" <jslaby@suse.cz>
Subject: TTY layer discussion about generic FIFO depth and Rx iddle timeout control
Date: Mon, 17 Jan 2022 00:06:31 +0100 [thread overview]
Message-ID: <202201170006.31440.pisa@cmp.felk.cvut.cz> (raw)
Dear Wander and Greg,
[resend on base of email-bot of Greg Kroah-Hartman's inbox]
I have noticed that you have sent enhancements
to the TTY layer.
I have worked on architecture of automotive LIN-bus
support for Linux UARTs. The SocketCAN API was idea
of Oliver Hartkopp and we have designed internals
to implement actual protocol. Rostislav Lisovy
was main author at our university in 2011. The code
has been used and is used by more people and I have
helped its integration to local Volkswagen subsidiary
projects. I have helped to maintain it for years
even that I have actually no use for it or contract.
But is seems usable...
I am not sure if it can reach quality standards
for mainline but I have tried to consolidate
many forks and copies from our original GIT
server which can be found on GitHub and united
project under
https://github.com/lin-bus
Kernel part - slLIN TTY discipline - can be found there
https://github.com/lin-bus/linux-lin/tree/master/sllin
Documentation
https://github.com/lin-bus/linux-lin/wiki/
The main obstacle to have version which can be used
with different UARTs seamlessly is missing internal low
level kernel API which would allow to control Rx trig
level.
I have not checked your changes yet but I would be happy
if some API is available for this control. Please see
issue
https://github.com/lin-bus/linux-lin/issues/13
Please suggest where to discuss the proposal/solutions
or if you plan to implement something like that.
I would be happy to work on that myself or with my students
but I personally do not get to that probably earlier
than in summer. I have to finish project for European Space
Agency at PiKRON company. We have quite lot of work
to switch our Computer Architectures classes and corresponding
QtMips/QtRvSim simulator to RISC-V etc...
Mainlining CTU CAN FD driver has higher priority than LIN for
me as well.
So my actual motivation is to document the need and get some
feedback if some such solution is on the horizon
and what should API look like if I get to it ourselves etc..
Best wishes,
Pavel
--
Pavel Pisa
phone: +420 603531357
e-mail: pisa@cmp.felk.cvut.cz
Department of Control Engineering FEE CVUT
Karlovo namesti 13, 121 35, Prague 2
university: http://dce.fel.cvut.cz/
personal: http://cmp.felk.cvut.cz/~pisa
projects: https://www.openhub.net/accounts/ppisa
CAN related:http://canbus.pages.fel.cvut.cz/
Open Technologies Research Education and Exchange Services
https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home
next reply other threads:[~2022-01-16 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 23:06 Pavel Pisa [this message]
2022-01-17 13:03 ` TTY layer discussion about generic FIFO depth and Rx iddle timeout control Greg Kroah-Hartman
2022-01-19 13:46 ` Pavel Pisa
2022-01-26 8:55 ` Greg Kroah-Hartman
2022-01-26 11:58 ` Wander Costa
2022-01-17 13:26 ` Wander Costa
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=202201170006.31440.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-serial@vger.kernel.org \
--cc=lisovy@gmail.com \
--cc=socketcan@hartkopp.net \
--cc=wander@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).