From: "Li, Hua Qian" <HuaQian.Li@siemens.com>
To: Nishanth Menon <nm@ti.com>
Cc: "wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"huaqianlee@gmail.com" <huaqianlee@gmail.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"kristo@kernel.org" <kristo@kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"Su, Bao Cheng" <baocheng.su@siemens.com>
Subject: RE: [PATCH v3 2/3] arm64: dts: ti: Add reserved memory for watchdog
Date: Mon, 8 Jan 2024 08:16:15 +0000 [thread overview]
Message-ID: <AS8PR10MB6993F047652F40675BDA689D9F6B2@AS8PR10MB6993.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230714225240.dvlwqaodp2l3cczm@disfigure>
Hi Nishanth,
The maintainers have picked up the driver and bindings, as follows:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29057cc5bddc785ea0a11534d7ad2546fa0872d3
Do you have time to work on the "DONOTMERGE" dts patch?
-----Original Message-----
From: Nishanth Menon <nm@ti.com>
Sent: Saturday, July 15, 2023 6:53 AM
To: Li, Hua Qian (DI FA CTR IPC CN PRC4) <HuaQian.Li@siemens.com>
Cc: wim@linux-watchdog.org; linux@roeck-us.net; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; conor+dt@kernel.org; huaqianlee@gmail.com; vigneshr@ti.com; kristo@kernel.org; linux-watchdog@vger.kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Kiszka, Jan (T CED) <jan.kiszka@siemens.com>; Su, Bao Cheng (DI FA CTR IPC CN PRC4) <baocheng.su@siemens.com>
Subject: Re: [PATCH v3 2/3] arm64: dts: ti: Add reserved memory for watchdog
On 17:51-20230713, huaqian.li@siemens.com wrote:
> From: Li Hua Qian <huaqian.li@siemens.com>
I guess I should be explicit about this: Lets keep this dts patch as "DONOTMERGE" in subject line for driver subsystem maintainer (I don't want a repeat of cpufreq maintainers picking up dts and associated warnings that are now pending fixes), resubmit at next rc1 and I can queue up the dts once the maintainers pick up the driver and bindings.
Ref: https://lore.kernel.org/all/20230714084725.27847-1-krzysztof.kozlowski@linaro.org/
>
> This patch adds a reserved memory for the TI AM65X platform watchdog
> to reserve the specific info, triggering the watchdog reset in last
> boot, to know if the board reboot is due to a watchdog reset.
>
> Signed-off-by: Li Hua Qian <huaqian.li@siemens.com>
> ---
> arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> index e26bd988e522..4bb20d493651 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-iot2050-common.dtsi
> @@ -63,6 +63,12 @@ rtos_ipc_memory_region: ipc-memories@a2000000 {
> alignment = <0x1000>;
> no-map;
> };
> +
> + /* To reserve the power-on(PON) reason for watchdog reset */
> + wdt_reset_memory_region: wdt-memory@a2200000 {
> + reg = <0x00 0xa2200000 0x00 0x1000>;
> + no-map;
> + };
> };
>
> leds {
> @@ -718,3 +724,7 @@ &mcu_r5fss0_core1 {
> <&mcu_r5fss0_core1_memory_region>;
> mboxes = <&mailbox0_cluster1>, <&mbox_mcu_r5fss0_core1>; };
> +
> +&mcu_rti1 {
> + memory-region = <&wdt_reset_memory_region>; };
> --
> 2.34.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-08 8:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 9:51 [PATCH v3 0/3] Add support for WDIOF_CARDRESET on TI AM65x huaqian.li
2023-07-13 9:51 ` [PATCH v3 1/3] dt-bindings: watchdog: ti,rti-wdt: Add support for WDIOF_CARDRESET huaqian.li
2023-07-13 9:59 ` Krzysztof Kozlowski
2023-07-13 9:51 ` [PATCH v3 2/3] arm64: dts: ti: Add reserved memory for watchdog huaqian.li
2023-07-14 22:52 ` Nishanth Menon
2023-07-14 22:52 ` Nishanth Menon
2023-07-14 23:27 ` Guenter Roeck
2023-07-15 5:25 ` Nishanth Menon
2023-07-15 5:25 ` Nishanth Menon
2024-01-08 8:16 ` Li, Hua Qian [this message]
2024-01-08 17:22 ` Nishanth Menon
2023-07-13 9:51 ` [PATCH v3 3/3] watchdog:rit_wdt: Add support for WDIOF_CARDRESET huaqian.li
2023-07-13 17:19 ` Guenter Roeck
2023-07-13 17:21 ` [PATCH v3 0/3] Add support for WDIOF_CARDRESET on TI AM65x Guenter Roeck
2023-07-14 7:00 ` Li, Hua Qian
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=AS8PR10MB6993F047652F40675BDA689D9F6B2@AS8PR10MB6993.EURPRD10.PROD.OUTLOOK.COM \
--to=huaqian.li@siemens.com \
--cc=baocheng.su@siemens.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=huaqianlee@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--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