[Outreachy] Introduction

[Deborah Brouwer <deborahbrouwer3563@gmail.com>]

Hi!
I am Deborah Brouwer, an outreachy internship applicant, from British Columbia,
Canada. I am interested in the project to improve the HDMI CEC compliance tests
and the CEC emulation of the vivid driver.

Following the initial outreachy instructions, I have been able to use the vivid
driver to set up two emulated cec devices and run the cec-compliance test both
with and without the cec-follower.  If I understand correctly, the cec-compliance
test uses the functions available from the linux kernel CEC API, to test whether
a CEC device complies with the CEC specification.  For example, the CEC specification
13.14 (Give Power Device Status) requires that the target device provide its power
status (e.g. standby, fully on) using a power status operand.  However, since the
kernel CEC API does not seem to return the power status, the cec-compliance test
fails. The CEC specification mentions that this might happen because this requirement
was optional in 1.3 and before.

In contrast, the cec-follower will emulate a CEC device that meets the CEC requirements
and returns the recognized power status operand signalling that the device is actually
on. This is why the cec-compliance test passes when the cec-follower is running.

If I am on the right track, I would like to start working on the Audio Rate Control
feature.  Would it be appropriate to start with the todo item of checking and keeping
track that the sending device is setting the audio rate at least every 2 seconds?

Deb