From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] device_drivers/uart01: Add uart01 test
Date: Thu, 2 Apr 2020 11:31:27 +0200 [thread overview]
Message-ID: <20200402093127.GA28452@yuki.lan> (raw)
In-Reply-To: <CAF12kFsFsG6Jk0citiGmicq+dyB90i_cG_bcDAMhHiyVPafRdA@mail.gmail.com>
Hi!
> >Indeed but it does not make sense tu run it with a different baud rates,
> >since the data are not transmitted at all.
> The data exchanged between Tx|Rx and buffer have nothing to do with
> baudrate?
> I think the baudrate is control Tx|Rx send and receive date rate to|from
> buffer.
That's what I'm not sure about, the documentation says that in loopback
mode data written to the port immediatelly appears on the receiving end,
which would mean that the uart speed does not matter at all.
Can you try a quick test? If you measure the time the test spends
writing data in loopback mode for a different uart speeds and they do
not differ the uart speed does not matter.
> >Unfortunately it does not seem to work on my AMD based desktop at all,
> >my guess is that the loopback bit is silently ignored by the hardware.
> >Which means that we cannot enable the test by default in loopback mode
> >after all
> I will test on my laptop and feedback result today, if it does no work , we
> should check the uart driver what different between x86 and arm64.
I bet that this differs chipset by chipset and I do not think there is
anything wrong with the uart driver per se.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-04-02 9:31 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
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 [this message]
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=20200402093127.GA28452@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