From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] device_drivers/uart01: Add uart01 test
Date: Tue, 31 Mar 2020 20:08:16 +0200 [thread overview]
Message-ID: <20200331180816.GE2900@yuki.lan> (raw)
In-Reply-To: <20200330152122.GA2699@yuki.lan>
Hi!
> > Thank you porting the serialcheck.c into LTP
> > I am sorry to find the serialcheck have not LOOPBACK mode support
> > the LOOPBACK mode is a better test than HW flow , because most machine's
> > uart have not connect the Rx & TX
> > in LOOPBACK mode. we test the uart port directly, So we can test one uart
> > port Rx and Tx functions at the same time .
> > here is the diff serialcheck with loopback patch
> > So I'd prefer use loopback mode test the uart in case.
> > $ diff serialcheck.c serialcheck-with-loopback.c
>
> Thanks for the hint, I had no idea that subset serial port hardware has
> a loopback test that could be enabled in modem control register which is
> meant for testing. I will have a closer look tomorrow.
If I understand this properly if we set a bit in the modem control
register we will test mostly the circuits between CPU and UART
controller which is better than nothing, but we are not really testing
if the port speed was set correctly since the data are just being copied
between registers in the UART controller, so it does not make sense to
change the speed in this mode. Or am I mistaken?
Also it does not seem to work for me and I've tried with both serial
ports on my desktop PC as well as with USB-to-Serial dongle. I can set
the bit just fine but loopback does not work.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-03-31 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:47 [LTP] [PATCH 0/2] [RFC] Add needs_devices && basic uart test Cyril Hrubis
2020-03-27 13:47 ` [LTP] [PATCH 1/2] tst_test: Add support for needs_devices Cyril Hrubis
2020-03-27 13:47 ` [LTP] [PATCH 2/2] device_drivers/uart01: Add uart01 test Cyril Hrubis
2020-03-27 15:11 ` Petr Vorel
2020-03-28 8:27 ` Cixi Geng
2020-03-30 15:21 ` Cyril Hrubis
2020-03-31 18:08 ` Cyril Hrubis [this message]
2020-04-01 11:57 ` Cixi Geng
2020-04-01 13:12 ` Cyril Hrubis
2020-04-02 1:30 ` Cixi Geng
2020-04-02 9:31 ` Cyril Hrubis
2020-04-02 11:16 ` Cixi Geng
2020-04-02 11:23 ` Cyril Hrubis
2020-04-03 1:50 ` Cixi Geng
2020-04-08 4:15 ` Cixi Geng
2020-04-08 14:18 ` Cyril Hrubis
2020-05-11 9:12 ` Cixi Geng
2020-05-11 9:37 ` Cyril Hrubis
2020-05-12 2:32 ` Cixi Geng
-- strict thread matches above, loose matches on Subject: below --
2020-06-23 11:28 [LTP] [PATCH 0/2] [RFC] Device discovery & UART test Cyril Hrubis
2020-06-23 11:28 ` [LTP] [PATCH 2/2] device_drivers/uart01: Add uart01 test Cyril Hrubis
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=20200331180816.GE2900@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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