Kernel Newbies archive mirror
 help / color / mirror / Atom feed
From: Ayush Singh <ayushdevel1325@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Getting help in writing tty driver
Date: Fri, 7 Jul 2023 16:37:53 +0530	[thread overview]
Message-ID: <CA+Yfj7sQfcKxTkhCzcY1D4y=aTJvL6Ui+mDC7Q52fjrMU2F2GA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1617 bytes --]

Hello everyone, I am working on a Google Summer of Code 2023 project [1]
under BeagleBoard.or. In this project, I have to write a Linux driver that
exposes `dev/ttyMCU0` (or something else) which can be accessed as a Serial
tty by MCUmgr [2]. This then sends the data and gets the response from the
CC1352 processor in BeagelPlay [3], which runs Zephyr over HDLC UART (the
data for this tty port has a particular HDLC address).

However, all the resources I could find seem to use deprecated or old APIs
(like `alloc_tty_driver` instead of `tty_alloc_driver`). After some trial
and error, I was able to transfer the data written to `ttyMCU0` to CC1352
using `write` in `tty_operations`. However, I am stumped on how to send
data to tty from the driver so that the userspace application can read it
(like using `cat`). Supposedly it should be done using
`tty_insert_flip_char` but the signature for this function in the tutorials
and the one present at `tty_flip.h` is quite different and does not seem to
work for me. Also, there seems to be something about the Echo flag but not
sure what all that is.

Finally, I am not sure I understand the relationship between tty port, tty
device, and tty driver either so it would be great if someone can guide me
to resources related to tty. I think a simple tty echo driver should allow
me to get the hang of what I am supposed to do.

Ayush

[1]: https://elinux.org/BeagleBoard/GSoC/2023_Proposal/AyushSingh
[2]: https://github.com/apache/mynewt-mcumgr
[3]: https://beagleboard.org/play
[4]:
https://git.beagleboard.org/gsoc/greybus/beagleplay-greybus-driver/-/tree/develop

[-- Attachment #1.2: Type: text/html, Size: 2056 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2023-07-07 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 11:07 Ayush Singh [this message]
2023-07-07 12:04 ` Getting help in writing tty driver Greg KH

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='CA+Yfj7sQfcKxTkhCzcY1D4y=aTJvL6Ui+mDC7Q52fjrMU2F2GA@mail.gmail.com' \
    --to=ayushdevel1325@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).