[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0a774c34-e82d-4ff0-aa3f-4f348f4c2296@oss.qualcomm.com>
Date: Thu, 17 Apr 2025 11:49:23 +0530
From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck
<linux@...ck-us.net>,
Rajendra Nayak <quic_rjendra@...cinc.com>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-watchdog@...r.kernel.org
Subject: Re: [PATCH v2 5/5] watchdog: qcom: add support to read the restart
reason from IMEM
On 4/16/2025 8:21 PM, Konrad Dybcio wrote:
>> .max_tick_count = 0xFFFFFU,
>> };
>>
>> +static int qcom_wdt_get_restart_reason(struct qcom_wdt *wdt,
> double space> + const struct qcom_wdt_match_data *data)
>
> Please align this
Ack.
>> +{
>> + struct regmap *imem;
>> + unsigned int val;
>> + int ret;
>> +
>> + imem = syscon_regmap_lookup_by_compatible(data->compatible);
> I still think nvmem could be better here, as it allows to plug in
> more magic values
Sure, I will be on vacation next week. I shall check on how to use nvmem
here once I'm back.
>
> Konrad
Powered by blists - more mailing lists