Re: [PATCH v8 1/4] dt-bindings: i2c: qcom,i2c-geni: Document multi-owner controller support

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] YAML syntax error in `qcom,qup-multi-owner` description due to missing block scalar indicator.
--

--- Patch [1]: [PATCH v8 1/4] dt-bindings: i2c: qcom,i2c-geni: Document multi-owner controller support ---
commit d38e4d9aefae5285416967f29ecb244ec4f2d7e0
Author: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>

dt-bindings: i2c: qcom,i2c-geni: Document multi-owner controller support

This commit adds a boolean property to the qcom,i2c-geni device tree binding
to describe QUP-based I2C controllers that are shared across multiple system
processors. It notes that the operating system must not assume exclusive
ownership of such controllers or reconfigure associated GPIOs into sleep
states.

> diff --git a/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml b/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
> --- a/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
> +++ b/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
> @@ -60,6 +60,22 @@ properties:
>    power-domains:
>      maxItems: 1
>  
> +  qcom,qup-multi-owner:
> +    type: boolean
> +    description:
> +      Indicates that the QUP-based controller is shared with one or more
> +      other system processors and must not be assumed to have exclusive
> +      ownership by the operating system.
> +
> +      The associated GPIOs must not be reconfigured into a sleep state

[Severity: Low]
Will this description format cause a YAML parsing error during a schema check?

Because the description spans multiple paragraphs separated by blank lines,
it appears to need a block scalar indicator (such as '|' or '>') immediately
following the 'description:' key. 

Without it, a YAML 1.2 parser may treat the blank line as the end of the
scalar and fail to parse the next paragraph, throwing an error when it cannot
find a mapping key for the subsequent text.

> +      during runtime suspend, as doing so may disrupt transactions
> +      initiated by another owner of the controller.
> +
> +      Each owner is responsible for maintaining any resource votes
> +      required for operation of the shared controller (for example clocks,
> +      power domains, interconnect bandwidth, or other platform-specific
> +      resources)
> +
>    reg:
>      maxItems: 1

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260708051023.2872304-1-mukesh.savaliya@oss.qualcomm.com?part=1