Tue, Apr 28, 2026 at 05:49:06PM +0200, ivecera@redhat.com wrote:

Add pin-operstate enum and operstate_on_dpll_get callback to report
the actual hardware status of a pin with respect to its parent DPLL
device. Unlike pin-state (which reflects administrative intent set
by the user), operstate reflects what the hardware is actually doing.

Defined operational states:
 - active: pin is qualified and actively used by the DPLL
 - standby: pin is qualified but not actively used by the DPLL
 - no-signal: pin does not have a valid signal
 - qual-failed: pin signal failed qualification

The operstate is reported inside the pin-parent-device nested
attribute alongside the existing state and phase-offset attributes.

Signed-off-by: Ivan Vecera <ivecera@redhat.com>

Looks great.

Reviewed-by: Jiri Pirko <redacted>

Thanks!