From: Jiunn Chang <c0d1n61at3@gmail.com>
To: linux-media@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Cc: hverkuil@xs4all.nl
Subject: [PATCH v2 0/2] cec-compliance: tuner control
Date: Tue, 24 Sep 2019 14:24:43 -0500 [thread overview]
Message-ID: <20190924192445.93575-1-c0d1n61at3@gmail.com> (raw)
In-Reply-To: <20190924141752.5508-1-c0d1n61at3@gmail.com>
This patch series implements analog tuner step increment/decrement as well as performs
cec-compliance tests for: select analog service, give tuner device status, and analog
step increment/decrement. New tests where added for tuner step increment/decrement and
existing tests where refactored for select analog service and give tuner device status.
Changes made since v1:
- Remove redundant error checking
- Add circular wrap logic to tuner step increment/decrement
---
Jiunn Chang (2):
cec-follower: add tuner step increment/decrement
cec-compliance: add/refactor tuner control tests
utils/cec-compliance/cec-test.cpp | 181 +++++++++++++++++++++++-------
utils/cec-follower/cec-tuner.cpp | 47 +++++++-
2 files changed, 184 insertions(+), 44 deletions(-)
--
2.23.0
next prev parent reply other threads:[~2019-09-24 19:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 14:17 [PATCH 0/2] cec-compliance: tuner control Jiunn Chang
2019-09-24 14:17 ` [PATCH 1/2] cec-follower: add tuner step increment/decrement Jiunn Chang
2019-09-24 15:20 ` Hans Verkuil
2019-09-24 14:17 ` [PATCH 2/2] cec-compliance: add/refactor tuner control tests Jiunn Chang
2019-09-24 19:24 ` Jiunn Chang [this message]
2019-09-30 4:30 ` [PATCH v3 0/3] cec-compliance: tuner control Jiunn Chang
2019-10-01 3:18 ` [PATCH v4 " Jiunn Chang
2019-10-03 3:18 ` [PATCH v5 0/2] " Jiunn Chang
2019-10-04 4:05 ` [PATCH v6 0/1] " Jiunn Chang
2019-10-04 4:05 ` [PATCH v6 1/1] Add test for new features in cec-follower Jiunn Chang
2019-10-03 3:18 ` [PATCH v5 1/2] cec-follower: add tuner step increment/decrement Jiunn Chang
2019-10-03 3:18 ` [PATCH v5 2/2] Add test for new features in cec-follower Jiunn Chang
2019-10-03 6:51 ` Hans Verkuil
2019-10-01 3:18 ` [PATCH v4 1/3] cec-follower: fix bugs for tuner emulation Jiunn Chang
2019-10-01 3:18 ` [PATCH v4 2/3] cec-follower: add tuner step increment/decrement Jiunn Chang
2019-10-01 7:12 ` Hans Verkuil
2019-10-01 3:18 ` [PATCH v4 3/3] cec-compliance: add tuner control test Jiunn Chang
2019-10-01 7:51 ` Hans Verkuil
2019-09-30 4:30 ` [PATCH v3 1/3] cec-follower: fix bugs for tuner emulation Jiunn Chang
2019-09-30 9:12 ` Hans Verkuil
2019-09-30 4:30 ` [PATCH v3 2/3] cec-follower: add tuner step increment/decrement Jiunn Chang
2019-09-30 9:35 ` Hans Verkuil
2019-09-30 4:30 ` [PATCH v3 3/3] cec-compliance: refactor tuner control tests Jiunn Chang
2019-09-30 9:43 ` Hans Verkuil
2019-09-24 19:24 ` [PATCH v2 1/2] cec-follower: add tuner step increment/decrement Jiunn Chang
2019-09-24 19:31 ` [Linux-kernel-mentees] " Shuah Khan
2019-09-25 6:54 ` Hans Verkuil
2019-09-25 7:12 ` Hans Verkuil
2019-09-24 19:24 ` [PATCH v2 2/2] cec-compliance: add/refactor tuner control tests Jiunn Chang
2019-09-24 19:44 ` [Linux-kernel-mentees] " Shuah Khan
2019-09-25 7:22 ` Hans Verkuil
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=20190924192445.93575-1-c0d1n61at3@gmail.com \
--to=c0d1n61at3@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).