RDKB-65287: Extend return value for unsupported HAL APIs

[biju-vi]

Reason for change: Add new macro for unsupported return type for all platforms
Test Procedure: NA
Risks: Low

Author: biju-vi biju.vijayanindiradevi@sky.uk

[Copilot]

Pull request overview

This PR adds a new unsupported-return status for thermal manager HAL APIs and introduces a CLA workflow for pull request signature checks.

Changes:

• Defines RETURN_UNSUPPORTED for thermal manager API return documentation.
• Documents RETURN_UNSUPPORTED as a possible return value for several thermal manager HAL APIs.
• Adds a GitHub Actions CLA workflow using the central RDK reusable workflow.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
include/platform_hal.h	Adds unsupported return-code macro and updates thermal manager API documentation.
.github/workflows/cla.yml	Adds CLA signature-check workflow for PR and issue-comment events.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[GoutamD2905]

May I know why we need RETURN_UNSUPPORTED?

Is this platform-specific and required only for XB10 and XB9? If so, we should not add it to the generic HAL header. Instead, we should include it only in headers meant for specific platforms meta-layers as patches, and keep the generic headers limited to definitions supported across all Comcast platforms.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[biju-vi]

May I know why we need RETURN_UNSUPPORTED?

Is this platform-specific and required only for XB10 and XB9? If so, we should not add it to the generic HAL header. Instead, we should include it only in headers meant for specific platforms meta-layers as patches, and keep the generic headers limited to definitions supported across all Comcast platforms.

Thermal Manager is going to be an open source code. So any third party who integrates thermal manager might need this return code if a specific HAL API is not supported on their platform

[stn594]

May I know why we need RETURN_UNSUPPORTED?

Is this platform-specific and required only for XB10 and XB9? If so, we should not add it to the generic HAL header. Instead, we should include it only in headers meant for specific platforms meta-layers as patches, and keep the generic headers limited to definitions supported across all Comcast platforms.

@GoutamD2905,

This is not platform specific. If we return RETURN_ERR , then that error code will mislead thermal manager and it will log "error message". That error message will be flooding in xb9 and xb10. So we defined a new UNSUPPORTED macro to distinguish the dummy function.