From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Testing low level UART driver
Date: Thu, 25 Jan 2018 08:34:52 +0100 [thread overview]
Message-ID: <20180125073452.GA4089@kroah.com> (raw)
In-Reply-To: <CAHhAz+gZww1RvwH6E_euagGHqLPAhNZRRZBL_XCeYYnB8nh32Q@mail.gmail.com>
On Thu, Jan 25, 2018 at 12:46:01PM +0530, Muni Sekhar wrote:
> On Wed, Jan 24, 2018 at 8:53 PM, Greg KH <greg@kroah.com> wrote:
> > On Wed, Jan 24, 2018 at 08:43:56PM +0530, Muni Sekhar wrote:
> >> On Wed, Jan 24, 2018 at 6:52 PM, Greg KH <greg@kroah.com> wrote:
> >> > On Wed, Jan 24, 2018 at 06:46:06PM +0530, Muni Sekhar wrote:
> >> >> Hi All,
> >> >>
> >> >> Does Linux kernel tree has any standard utilities to test any low
> >> >> level UART driver?
> >> >
> >> > What do you mean by "low level UART driver"?
> >> bcm63xx_uart.c
> >>
> >> >
> >> > Have you tried one of the many different userspace serial port tools?
> >> I tried only minicom. Could you let me know the best userspace serial
> >> port tools.
> >
> > What doesn't work with minicom? That's a really good tester given that
> > it exercises the tty layer a lot.
>
> I?m trying to record throughput achieved with different baud rates in
> loopback mode. Does minicom support this?
Not that I know of, but it would be pretty simple to write a program to
do that.
good luck!
greg k-h
prev parent reply other threads:[~2018-01-25 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 13:16 Testing low level UART driver Muni Sekhar
2018-01-24 13:22 ` Greg KH
2018-01-24 15:13 ` Muni Sekhar
2018-01-24 15:23 ` Greg KH
2018-01-25 7:16 ` Muni Sekhar
2018-01-25 7:34 ` Greg KH [this message]
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=20180125073452.GA4089@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.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 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.