Re: [PATCH v3 1/4] dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] dt-bindings: soc: ti: unresolved maintainer objection to
  ti,proxy-id
--

commit 3553d71ec015a9aca0d29d3d396108a6a975a8a8
Author: Moteen Shah <m-shah@ti.com>

dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf

This commit adds the Device Tree binding schema for the Texas Instruments
TDA54 SoC MCU domain System Control Module configuration register region.

> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml b/Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml
> new file mode 100644
> index 0000000000000..111cbb739b5f1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml
> @@ -0,0 +1,78 @@

[ ... ]

> +  ti,proxy-id:
> +    $ref: /schemas/types.yaml#/definitions/uint32
> +    minimum: 0
> +    maximum: 7
> +    description:
> +      Proxy region (0-7) through which this node's clients access
> +      claimable registers and their fault status registers.
> +
> +  "#clock-cells":
> +    const: 1
> +    description:
> +      The cell selects the ePWM time-base clock gate. Values 0 to 12 select
> +      ehrpwm_tbclk0 to ehrpwm_tbclk12, i.e. the gate for ePWM instance N is
> +      specifier N.
> +
> +required:
> +  - compatible
> +  - reg
> +  - ti,proxy-id

[Severity: Medium]
As reported by Krzysztof Kozlowski on v2 [1], is the required custom
ti,proxy-id property still needed here?

The proxy selection does not vary per board for this single device (or
would be implied by the compatible string), and selecting a proxy region
for register access arbitration duplicates the standard access-controllers
binding.

[1] https://lore.kernel.org/r/20261028-inventive-screeching-bettong-9f4240@quoll

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261112081047.1550471-1-m-shah@ti.com?part=1