From: Deborah Brouwer <deborahbrouwer3563@gmail.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, Deborah Brouwer <deborahbrouwer3563@gmail.com>
Subject: [PATCH v3 0/2] cec-follower: increase accuracy Audio Rate Control
Date: Mon, 26 Apr 2021 20:29:46 -0700 [thread overview]
Message-ID: <cover.1619492378.git.deborahbrouwer3563@gmail.com> (raw)
Changes since v2:
* Patch 1:
cec-follower: increase precision of Audio Rate Control active sensing
* Add the unit (nanoseconds) as a suffix to the define name.
* Write the defined value as a multiplication of seconds times
nsecs_per_sec.
* Add ULL to help cast the expression to an unsigned long long.
* Note: for the sake of clarity in the diff, a blank line before
the if statement is missing but it is subsequently added by Patch 2.
* Patch 2:
cec-follower: detect the cessation of Audio Rate Control messages
* Remove double negative in comment.
* Extend comment to specify (i.e. state.last_aud_rate_rx_ts != 0).
* Make warning message more succinct.
Changes since v1:
* Patch 1: cec-follower: increase precision of Audio Rate Control active sensing
* new patch
*Patch 2:
* Keep the aud_rate_msg_interval_check in processMsg to avoid missing
late messages that arrive between periodic interval checks.
* Swap arguments so that struct node appears first.
* Add blank line for readability.
Deborah Brouwer (2):
cec-follower: increase precision of Audio Rate Control active sensing
cec-follower: detect the cessation of Audio Rate Control messages
utils/cec-follower/cec-processing.cpp | 30 ++++++++++++++++-----------
1 file changed, 18 insertions(+), 12 deletions(-)
--
2.17.1
next reply other threads:[~2021-04-27 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 3:29 Deborah Brouwer [this message]
2021-04-27 3:29 ` [PATCH v3 1/2] cec-follower: increase precision of Audio Rate Control active sensing Deborah Brouwer
2021-04-27 3:29 ` [PATCH v3 2/2] cec-follower: detect the cessation of Audio Rate Control messages 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.1619492378.git.deborahbrouwer3563@gmail.com \
--to=deborahbrouwer3563@gmail.com \
--cc=hverkuil@xs4all.nl \
--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).