Documnetation: Define list of CEC Messages Possible For Sink / Source

[sramani-metro]

Task 4

Goal: Set requirements for messages to support,

• Define a list of messages that we require to support
• List out all messages possible, and define a table of possible messages / implemented as part of the support documentation.

Examples

User Commands -Active Source Request -Add/Remove devices -Catalogue of Commands -Dynamic base config change

Acceptance Criteria

• Created support for the messages required to implement (covering main areas).
• Documentation is in place to allow users to understand supported features
• Test to support main features needs to exist.

[Ulrond]

• Evaluate open-source CEC libraries to format CEC messages.
• Write a small CEC message formatted to create messages on demand
• Translation logic to create CEC messages for features like One Touch Play or HDMI hotplug etc. These items where completed as part of #18

[Ulrond]

Next Steps

• Document automatically triggered messages compared to externally stimulated messages.

• Generating the lists from resources on the internet, the spec.

• Cross reference with the capabilities of the main rdk source code

• In a real world setup, what messages are likely to be triggered? New Milestone

  • Discuss with the UI Team if require on messages they expect. New Ticket
  • Trigger all the classic comments in the real world, example results New Ticket

• Review with architecture for MVP Requirements New Ticket

MVP Requirements New Milestone**

[sramani-metro]

Created https://github.com/rdkcentral/rdk-halif-test-hdmi_cec/pull/40 to document all possible end user triggered and automatically triggered messages.

[Ulrond]

Branch is merged