Re: [PATCH RFC 4/6] dt-bindings: sram: qcom,imem: add the support for restart reason

[Krzysztof Kozlowski]

On 08/04/2025 10:49, Kathiravan Thirumoorthy wrote:
> In the Qualcomm IPQ SoCs, system restart reason is captured in the IMEM
> location by bootloaders and Linux populates this information to the
> userspace. Add a child node for the restart reason in the IMEM region.
> 
> Signed-off-by: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@xxxxxxxxxxxxxxxx>
> ---
>  .../devicetree/bindings/sram/qcom,imem.yaml        | 24 ++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/sram/qcom,imem.yaml b/Documentation/devicetree/bindings/sram/qcom,imem.yaml
> index dec1b1ee924cf1386f559eb262ea864f2788c165..c3dab5fbc88c1515bfb3585f18aed9e01ae36fe4 100644
> --- a/Documentation/devicetree/bindings/sram/qcom,imem.yaml
> +++ b/Documentation/devicetree/bindings/sram/qcom,imem.yaml
> @@ -56,6 +56,10 @@ patternProperties:
>      $ref: /schemas/remoteproc/qcom,pil-info.yaml#
>      description: Peripheral image loader relocation region
>  
> +  "^restart-reason@[0-9a-f]+$":
> +    $ref: /schemas/watchdog/qcom,restart-reason.yaml#

Just fold it here... but really, there is little point in describing
memory layout of syscon block register by register. What will be next?
Another entry for one more register? And then another? And another? And
every time you will claim "just this one", because you decide not to
provide complete picture when sending bindings for the first time?


Best regards,
Krzysztof