All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subhashini Rao Beerisetty <subhashbeerisetty@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Cc: linux-tty@vger.kernel.org
Subject: tty: uart: custom speed
Date: Mon, 4 Mar 2019 17:42:24 +0530	[thread overview]
Message-ID: <CAPY=qRS8=ohJ-ir7i4KEjw+XkUrwefwUoqqknQ8rOiq-BM8gQw@mail.gmail.com> (raw)

 Hi All,


I’ve an UART ports on Xilinx FPGA board and it gets connected to PC
via PCIe bus. I could not find any kernel serial driver which supports
our hardware so I plan to develop a new driver. I see two approaches
to develop an UART driver i.e. either by using tty_register_driver()
or an uart_register_driver().


Regarding my UART module, it has a counter of 16 bits and runs on a
32Mhz clock. It supports all the standard & non-standard baud’s up to
4Mbps.


If I used struct tty_operations, I noticed that baud rate changing is
done via “.set_termios” API, but this method only supports standard
baud rates. I’d like to know why this API does not support
non-standard baud rates?


Okay, what methods a good driver should implement to support
non-standard baud rates?

Thanks

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

             reply	other threads:[~2019-03-04 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 12:12 Subhashini Rao Beerisetty [this message]
     [not found] <CAPY=qRSrw7JxAbORoUHckxcMRjk16zYP7nc2zakGd411JMjGjA@mail.gmail.com>
     [not found] ` <20190304132302.GA9869@kroah.com>
2019-03-04 14:49   ` tty: uart: custom speed Subhashini Rao Beerisetty
2019-03-04 14:57     ` Greg KH
2019-03-04 15:23       ` Subhashini Rao Beerisetty
2019-03-04 17:16         ` Vladimir Zapolskiy
2019-03-04 18:47         ` Grant Edwards

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='CAPY=qRS8=ohJ-ir7i4KEjw+XkUrwefwUoqqknQ8rOiq-BM8gQw@mail.gmail.com' \
    --to=subhashbeerisetty@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-tty@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 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.