From: Deborah Brouwer <deborahbrouwer3563@gmail.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, jaffe1@gmail.com,
Deborah Brouwer <deborahbrouwer3563@gmail.com>
Subject: [PATCH v4 0/2] cec: expand Timer Programming tests
Date: Mon, 12 Jul 2021 23:09:18 -0700 [thread overview]
Message-ID: <cover.1626155911.git.deborahbrouwer3563@gmail.com> (raw)
This is part of an Outreachy project to expand the testing of
Timer Programming messages as handled by CEC adapters.
Changes since v3:
Patch 1/2: cec: expand Timer Programming tests
- revise error and overlap function names and return values
- use struct tm as a pointer
- increment year only when follower receives set time message
- clear timers in previous year/next year if any
- add helper functions to send and clear timers
- add logical address Backup to device that may pass tests
- add check for standby message received during recording
Patch 2/2: cec-follower: emulate programmed timer recordings
- add check for standby message received during recording
Changes since v2:
Patch 1/2: cec: expand Timer Programming tests
- use 3-character abbreviations for months
- in set_timer tests, simplify the method for finding "tomorrow"
- use fixed dates for timer_error tests
- use full leap-year algorithm
- add source type and recording sequence as ways to compare timers
- add source type and recording sequence to print_timers()
- replace timer field end_time with duration in seconds
- replace timer_duplicate function with std::set::find
- do not truncate overlapped timers, just set them with a warning
Patch 2/2: cec-follower: emulate programmed timer recordings
- new patch
Changes since v1:
- rename functions for clarity
- set most test timers as a function of current time, not fixed times
- use time_t instead of struct tm to hold start/stop times
- use std::set instead of std::list to hold timers
- add repeat timers (recording sequence) emulation
Deborah Brouwer (2):
cec: expand Timer Programming tests
cec-follower: emulate programmed timer recordings
utils/cec-compliance/cec-compliance.cpp | 1 +
utils/cec-compliance/cec-compliance.h | 1 +
utils/cec-compliance/cec-test.cpp | 424 +++++++++++++++++++-----
utils/cec-follower/cec-follower.cpp | 59 ++++
utils/cec-follower/cec-follower.h | 44 +++
utils/cec-follower/cec-processing.cpp | 65 ++++
utils/cec-follower/cec-tuner.cpp | 295 +++++++++++++++--
7 files changed, 788 insertions(+), 101 deletions(-)
--
2.25.1
next reply other threads:[~2021-07-13 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 6:09 Deborah Brouwer [this message]
2021-07-13 6:09 ` [PATCH v4 1/2] cec: expand Timer Programming tests Deborah Brouwer
2021-07-13 6:09 ` [PATCH v4 2/2] cec-follower: emulate programmed timer recordings Deborah Brouwer
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=cover.1626155911.git.deborahbrouwer3563@gmail.com \
--to=deborahbrouwer3563@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=jaffe1@gmail.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox