From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Kent Gibson <warthog618@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-gpio@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [libgpiod v2][PATCH v2 0/2] libgpiod v2: rewrite tests for the C library
Date: Mon, 21 Feb 2022 16:40:53 +0100 [thread overview]
Message-ID: <20220221154055.654819-1-brgl@bgdev.pl> (raw)
This series contains a rework of the line_config interface and a bit patch
that replaces the old test suite for libgpiod v1 based on gpio-mockup with
a one covering around 95% of the libgpiod v2 code based on the upcoming
gpio-sim module.
v1 -> v2:
- drop applied patches
- improve documentation
- skip offsets that are overridden in line_config but not actually requested
Bartosz Golaszewski (2):
line-config: expose the override logic to users
tests: rewrite core C tests using libgpiosim
configure.ac | 8 +-
include/gpiod.h | 509 ++++++++++------
lib/line-config.c | 752 ++++++++++++++---------
tests/Makefile.am | 20 +-
tests/gpiod-test-helpers.c | 49 ++
tests/gpiod-test-helpers.h | 139 +++++
tests/gpiod-test-sim.c | 303 ++++++++++
tests/gpiod-test-sim.h | 42 ++
tests/gpiod-test.c | 233 +-------
tests/gpiod-test.h | 81 +--
tests/gpiosim/gpiosim.c | 1 +
tests/mockup/Makefile.am | 11 -
tests/mockup/gpio-mockup.c | 496 ----------------
tests/mockup/gpio-mockup.h | 36 --
tests/tests-chip.c | 282 ++++-----
tests/tests-edge-event.c | 420 +++++++++++++
tests/tests-event.c | 908 ----------------------------
tests/tests-info-event.c | 301 ++++++++++
tests/tests-line-config.c | 448 ++++++++++++++
tests/tests-line-info.c | 316 ++++++++++
tests/tests-line-request.c | 468 +++++++++++++++
tests/tests-line.c | 1091 ----------------------------------
tests/tests-misc.c | 86 ++-
tests/tests-request-config.c | 90 +++
tools/gpioget.c | 6 +-
tools/gpiomon.c | 6 +-
tools/gpioset.c | 9 +-
27 files changed, 3630 insertions(+), 3481 deletions(-)
create mode 100644 tests/gpiod-test-helpers.c
create mode 100644 tests/gpiod-test-helpers.h
create mode 100644 tests/gpiod-test-sim.c
create mode 100644 tests/gpiod-test-sim.h
delete mode 100644 tests/mockup/Makefile.am
delete mode 100644 tests/mockup/gpio-mockup.c
delete mode 100644 tests/mockup/gpio-mockup.h
create mode 100644 tests/tests-edge-event.c
delete mode 100644 tests/tests-event.c
create mode 100644 tests/tests-info-event.c
create mode 100644 tests/tests-line-config.c
create mode 100644 tests/tests-line-info.c
create mode 100644 tests/tests-line-request.c
delete mode 100644 tests/tests-line.c
create mode 100644 tests/tests-request-config.c
--
2.30.1
next reply other threads:[~2022-02-21 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 15:40 Bartosz Golaszewski [this message]
2022-02-21 15:40 ` [libgpiod v2][PATCH v2 1/2] line-config: expose the override logic to users Bartosz Golaszewski
2022-02-22 11:40 ` Kent Gibson
2022-02-23 11:10 ` Andy Shevchenko
2022-03-02 12:59 ` Bartosz Golaszewski
2022-03-02 14:32 ` Kent Gibson
2022-03-02 15:54 ` Bartosz Golaszewski
2022-02-21 15:40 ` [libgpiod v2][PATCH v2 2/2] tests: rewrite core C tests using libgpiosim Bartosz Golaszewski
2022-02-23 10:18 ` Kent Gibson
2022-02-24 20:33 ` Bartosz Golaszewski
2022-02-24 23:52 ` Kent Gibson
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=20220221154055.654819-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=warthog618@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).