From: Nishanth Menon <nm@ti.com>
To: Udit Kumar <u-kumar1@ti.com>
Cc: <catalin.marinas@arm.com>, <will@kernel.org>, <vigneshr@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <quic_bjorande@quicinc.com>,
<arnd@arndb.de>, <krzysztof.kozlowski@linaro.org>,
<konrad.dybcio@linaro.org>, <geert+renesas@glider.be>,
<neil.armstrong@linaro.org>, <nfraprado@collabora.com>,
<broonie@kernel.org>, <rafal@milecki.pl>
Subject: Re: [PATCH] arm64: defconfig: Enable K3 RTI Watchdog
Date: Wed, 21 Jun 2023 00:15:44 -0500 [thread overview]
Message-ID: <20230621051544.mvxz5hjxhi37eakw@precinct> (raw)
In-Reply-To: <20230621051358.3905149-1-u-kumar1@ti.com>
On 10:43-20230621, Udit Kumar wrote:
> K3 Family has RTI watchdog. This patch is
For the benefit of others, please provide context of what K3 and RTI
watchdog is.
> needed to enable WDT functions.
Why not a module?
Also please indicate specific products that can benefit with the change.
>
> Signed-off-by: Udit Kumar <u-kumar1@ti.com>
> ---
> arch/arm64/configs/defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 57c6b7bb88d4..4567645abe35 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -686,6 +686,7 @@ CONFIG_UNIPHIER_WATCHDOG=y
> CONFIG_PM8916_WATCHDOG=m
> CONFIG_BCM2835_WDT=y
> CONFIG_BCM7038_WDT=m
> +CONFIG_K3_RTI_WATCHDOG=y
> CONFIG_MFD_ALTERA_SYSMGR=y
> CONFIG_MFD_BD9571MWV=y
> CONFIG_MFD_AXP20X_I2C=y
> --
> 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:[~2023-06-21 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 5:13 [PATCH] arm64: defconfig: Enable K3 RTI Watchdog Udit Kumar
2023-06-21 5:15 ` Nishanth Menon [this message]
2023-06-21 5:29 ` Kumar, Udit
2023-06-21 5:36 ` Nishanth Menon
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=20230621051544.mvxz5hjxhi37eakw@precinct \
--to=nm@ti.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=quic_bjorande@quicinc.com \
--cc=rafal@milecki.pl \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=will@kernel.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