Re: [PATCH v10 0/3] Add support to read the watchdog bootstatus from IMEM

[Kathiravan Thirumoorthy]

On 5/13/2026 10:30 AM, Kathiravan Thirumoorthy wrote:
> In Qualcomm IPQ SoCs, if the system is rebooted due to the watchdog
> timeout, there is no way to identify it. Current approach of checking
> the EXPIRED_STATUS in WDT_STS is not working.
>
> To achieve this, if the system is rebooted due to watchdog timeout, the
> information is captured in the IMEM by the bootloader (along with other
> reason codes as well).
>
> This series attempts to address this by adding the support to read the
> IMEM and populate the information via bootstatus sysfs file.
>
> With the CONFIG_WATCHDOG_SYSFS enabled, user can extract the information
> as below:
>
> cat
> /sys/devices/platform/soc@0/f410000.watchdog/watchdog/watchdog0/bootstatus
> 32
>
> Upto V9, this series has changes targeted for both qcom and watchdog
> tree. So V10 was sent with only watchdog changes and it is picked into
> watchdog tree[1]. For the remaining DTS patches, sending it as V10 again
> which needs to be picked via qcom tree.
>
> Since the watchdog changes are not yet reflected in linux-next yet, upon
> merging this before the linux-next gets refreshed, below DT binding
> warning will be seen
>
> arch/arm64/boot/dts/qcom/ipq5424-rdp466.dtb: watchdog@f410000:
> Unevaluated properties are not allowed ('sram' was unexpected)
>          from schema $id:
> http://devicetree.org/schemas/watchdog/qcom-wdt.yaml#
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/log/?h=watchdog-next
>
> Signed-off-by: Kathiravan Thirumoorthy<kathiravan.thirumoorthy@xxxxxxxxxxxxxxxx>

Bjorn, Gentle ping... Can this be picked up for v7.2?