From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
bod.linux@nxsw.ie
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 4/4] watchdog: qcom: add support to read the restart reason from IMEM
Date: Sat, 3 May 2025 00:13:29 +0200 [thread overview]
Message-ID: <3333cfa8-381e-4c10-898b-a3c4cf8159e5@oss.qualcomm.com> (raw)
In-Reply-To: <83c427de-c678-4408-9b04-2f3d2eef9fac@oss.qualcomm.com>
On 5/2/25 6:08 PM, Kathiravan Thirumoorthy wrote:
>
> On 5/2/2025 7:03 PM, Guenter Roeck wrote:
>>> static int qcom_wdt_probe(struct platform_device *pdev)
>>> {
>>> struct device *dev = &pdev->dev;
>>> @@ -273,8 +304,13 @@ static int qcom_wdt_probe(struct platform_device *pdev)
>>> wdt->wdd.parent = dev;
>>> wdt->layout = data->offset;
>>> - if (readl(wdt_addr(wdt, WDT_STS)) & 1)
>>> - wdt->wdd.bootstatus = WDIOF_CARDRESET;
>>> + ret = qcom_wdt_get_restart_reason(wdt, data);
>>> + if (ret == -ENODEV) {
>>> + if (readl(wdt_addr(wdt, WDT_STS)) & 1)
>>> + wdt->wdd.bootstatus = WDIOF_CARDRESET;
>>> + } else if (ret) {
>>> + return ret;
>>> + }
>>
>> Seems odd to me that there is now a function qcom_wdt_get_restart_reason()
>> but it doesn't handle all means to get the restart reason. Maybe I missed it,
>> but what is the reason for that ? Why not move reading WDT_STS into
>> qcom_wdt_get_restart_reason() as well ?
>
>
> No specific reason as such. I was little hesitant use "goto" statements and such as. So I thought this would be little cleaner approach. Please let me know if I have consolidate everything under qcom_wdt_get_restart_reason().
You can try grabbing the syscon handle, and if absent, fall back to the
common handling
Konrad
next prev parent reply other threads:[~2025-05-02 22:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 13:17 [PATCH v3 0/4] Add support to read the restart reason from IMEM Kathiravan Thirumoorthy
2025-05-02 13:17 ` [PATCH v3 1/4] dt-bindings: sram: qcom,imem: Document IPQ5424 compatible Kathiravan Thirumoorthy
2025-05-02 13:17 ` [PATCH v3 2/4] arm64: dts: qcom: ipq5424: Add the IMEM node Kathiravan Thirumoorthy
2025-05-02 13:17 ` [PATCH v3 3/4] watchdog: qcom: introduce the device data for IPQ5424 watchdog device Kathiravan Thirumoorthy
2025-05-02 13:36 ` Guenter Roeck
2025-05-02 14:53 ` Dmitry Baryshkov
2025-05-02 16:01 ` Kathiravan Thirumoorthy
2025-05-02 13:17 ` [PATCH v3 4/4] watchdog: qcom: add support to read the restart reason from IMEM Kathiravan Thirumoorthy
2025-05-02 13:33 ` Krzysztof Kozlowski
2025-05-02 16:02 ` Kathiravan Thirumoorthy
2025-05-02 13:33 ` Guenter Roeck
2025-05-02 16:08 ` Kathiravan Thirumoorthy
2025-05-02 22:13 ` Konrad Dybcio [this message]
2025-05-02 14:03 ` Konrad Dybcio
2025-05-02 16:28 ` Kathiravan Thirumoorthy
2025-05-02 22:23 ` Konrad Dybcio
2025-05-06 11:01 ` Kathiravan Thirumoorthy
2025-05-14 13:15 ` Kathiravan Thirumoorthy
2025-05-14 18:05 ` Guenter Roeck
2025-05-16 11:18 ` Konrad Dybcio
2025-05-16 12:52 ` Kathiravan Thirumoorthy
2025-05-16 16:35 ` Konrad Dybcio
2025-05-17 10:41 ` Kathiravan Thirumoorthy
2025-05-02 14:54 ` Dmitry Baryshkov
2025-05-02 16:31 ` Kathiravan Thirumoorthy
2025-08-11 18:40 ` (subset) [PATCH v3 0/4] Add " Bjorn Andersson
2025-08-25 12:11 ` Kathiravan Thirumoorthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3333cfa8-381e-4c10-898b-a3c4cf8159e5@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bod.linux@nxsw.ie \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox