public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] device_drivers/uart01: Add uart01 test
Date: Mon, 11 May 2020 11:37:30 +0200	[thread overview]
Message-ID: <20200511093730.GD3070@yuki.lan> (raw)
In-Reply-To: <CAF12kFuJ=bC2ByRN7ihk=CZnA48zVW9KeAoDJO3+VcOJ13C=ug@mail.gmail.com>

Hi!
> I had study the ltp execution framework and found that the LTP
> detection device is
> not suitable for device driver test at present.
> Like the UART test, I want have a auto-detect way to find the device
> needed to test
>  in the current running LtP machines.
> Now I have test the uart case in several sprdtream Soc
> these board  have different /dev/tty* device???and I nedd run in CI
> manual export device puzzled me to do the auto-test-job.
> moreover I wil  porting other device driver testcases in the future.
> So can We expand the LTP detection ?

Sorry I haven't managed to work on this before it was time for LTP
release. I will resume my work on this once LTP is released.

My generall idea is that the LTP framework will get a path to a
directory with scripts that would be evaluated at test runtime and will
return list of devices to test. These scripts will have to be supplied
by the user as managing lab hardware is out of scope of the LTP
framework.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2020-05-11  9:37 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
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 [this message]
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=20200511093730.GD3070@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