From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>
Cc: 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>,
Guenter Roeck <linux@roeck-us.net>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v4 3/5] dt-bindings: watchdog: qcom-wdt: Document qcom,imem property
Date: Sun, 1 Jun 2025 17:51:29 +0200 [thread overview]
Message-ID: <680316ba-5e28-42f2-9e83-8c48af78b785@kernel.org> (raw)
In-Reply-To: <41ee75df-2244-45ad-956c-e17ea5804dbe@oss.qualcomm.com>
On 28/05/2025 19:16, Konrad Dybcio wrote:
>> Krzysztof, Based on the discussions from the previous versions, I have made the changes. Can you help to guide me on how to handle this? Should I just name the property as "sram" and point to the sub block in the IMEM region like how it is done at [1][2], which is more or like similar to what I have submitted in V1 of this series[3] Or is the current approach acceptable? Or some other way to handle this?
>>
>> [1] https://lore.kernel.org/linux-arm-msm/20250523-topic-ipa_imem-v1-1-b5d536291c7f@oss.qualcomm.com/T/#u
>>
>> [2] https://lore.kernel.org/linux-arm-msm/20250523-topic-ipa_imem-v1-2-b5d536291c7f@oss.qualcomm.com/T/#u
>>
>> [3] https://lore.kernel.org/linux-arm-msm/20250408-wdt_reset_reason-v1-0-e6ec30c2c926@oss.qualcomm.com/
>
> Let's go with desired-value-in-dt here.. I don't trust the firmware
> to never change. `sram` is prooobably fine, let's hear from Krzysztof
>
I propose to go with 'sram' property.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-01 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 8:34 [PATCH v4 0/5] Add support to read the watchdog bootstatus from IMEM Kathiravan Thirumoorthy
2025-05-19 8:34 ` [PATCH v4 1/5] dt-bindings: sram: qcom,imem: Document IPQ5424 compatible Kathiravan Thirumoorthy
2025-05-19 8:34 ` [PATCH v4 2/5] arm64: dts: qcom: ipq5424: Add the IMEM node Kathiravan Thirumoorthy
2025-05-19 8:34 ` [PATCH v4 3/5] dt-bindings: watchdog: qcom-wdt: Document qcom,imem property Kathiravan Thirumoorthy
2025-05-20 7:25 ` Krzysztof Kozlowski
2025-05-20 16:00 ` Konrad Dybcio
2025-05-21 6:53 ` Krzysztof Kozlowski
2025-05-22 15:45 ` Konrad Dybcio
2025-05-23 14:35 ` Kathiravan Thirumoorthy
2025-05-28 17:16 ` Konrad Dybcio
2025-06-01 15:51 ` Krzysztof Kozlowski [this message]
2025-06-02 4:14 ` Kathiravan Thirumoorthy
2025-05-19 8:34 ` [PATCH v4 4/5] watchdog: qcom: add support to get the bootstatus from IMEM Kathiravan Thirumoorthy
2025-05-20 7:28 ` Krzysztof Kozlowski
2025-05-19 8:34 ` [PATCH v4 5/5] arm64: dts: qcom: ipq5424: add support to get watchdog " 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=680316ba-5e28-42f2-9e83-8c48af78b785@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konrad.dybcio@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=quic_rjendra@quicinc.com \
--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