type-c-service/tps6699x: Fix EPR capable flag not being set

[RobertZ2011]

This flag was not being set properly. Also add two more useful fields to PortStatus.

[Copilot]

Pull request overview

This PR fixes PortStatus.epr not being populated when using the TPS6699x Type‑C/PD controller driver, by extracting the EPR-capable bit from the partner’s first received Source PDO (the 5V fixed SPR PDO). It also updates the PortStatus field documentation to describe epr as “port partner is EPR capable”. The intent is to make the EPR capability visible to higher layers that consume PortStatus.

Changes:

• Parse the first received Source PDO as a fixed PDO and use its flags to populate dual_power, unconstrained_power, and the newly-set epr field.
• Update PortStatus.epr doc comment to reflect “port partner is EPR capable”.

Reviewed changes

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

File	Description
type-c-service/src/driver/tps6699x.rs	Sets PortStatus.epr (and refactors related flag extraction) based on the first received fixed Source PDO.
embedded-service/src/type_c/controller.rs	Updates the documentation describing what PortStatus.epr represents.

[asasine]

Use an exhaustive pattern to not forget fields by accident.

let Pdo { a, b, c } = pdo; // note: no `..`. Use `field: _` to intentionally discard one.

[RobertZ2011]

Done, I've also added dual_data and usb_comms_capable to PortStatus to support more functionality for downstream users. The other ignored fields are either irrelevant (current/voltage is already pulled from the PDO), or doesn't strike me as particularly useful.

[asasine]

What about putting the whole PDO in?

[asasine]

The whole PDO would avoid ambiguity with what each field refers to, and would save us from needing to revisit this again for yet-another-field.