From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH v4 6/8] watchdog: kconfig: Enable designware for rk3399
Date: Thu, 9 Jan 2020 14:22:20 +0530 [thread overview]
Message-ID: <20200109085222.22670-7-jagan@amarulasolutions.com> (raw)
In-Reply-To: <20200109085222.22670-1-jagan@amarulasolutions.com>
Enable designware watchdog driver for rk3399 if WDT defined.
Cc: Marek Vasut <marex@denx.de>
Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
---
Changes for v4:
- This change on top of below series
https://patchwork.ozlabs.org/project/uboot/list/?series=151431
drivers/watchdog/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index bf5612a811..ceefee3a6b 100644
--- a/drivers/watchdog/Kconfig
+++ b/drivers/watchdog/Kconfig
@@ -48,6 +48,7 @@ config ULP_WATCHDOG
config DESIGNWARE_WATCHDOG
bool "Designware watchdog timer support"
select HW_WATCHDOG if !WDT
+ default y if WDT && ROCKCHIP_RK3399
help
Enable this to support Designware Watchdog Timer IP, present e.g.
on Altera SoCFPGA SoCs.
--
2.18.0.321.gffc6fa0e3
next prev parent reply other threads:[~2020-01-09 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 8:52 [PATCH v4 0/8] rk3399: Add redundant boot support Jagan Teki
2020-01-09 8:52 ` [PATCH v4 1/8] rockchip: Add cpu-info Jagan Teki
2020-01-09 8:52 ` [PATCH v4 2/8] rockchip: rk3399: Enable DISPLAY_CPUINFO Jagan Teki
2020-01-09 8:52 ` [PATCH v4 3/8] arm: rockchip: Add common cru.h Jagan Teki
2020-01-09 8:52 ` [PATCH v4 4/8] rockchip: Add common reset cause Jagan Teki
2020-01-09 8:52 ` [PATCH v4 5/8] rockchip: rk3399: Add bootcount support Jagan Teki
2020-01-09 8:52 ` Jagan Teki [this message]
2020-01-17 6:46 ` [PATCH v4 6/8] watchdog: kconfig: Enable designware for rk3399 Kever Yang
2020-01-09 8:52 ` [DO NOT MERGE] [PATCH v4 7/8] roc-rk3399-pc: Enable watchdog Jagan Teki
2020-01-09 8:52 ` [DO NOT MERGE] [PATCH v4 8/8] roc-rk3399-pc: Enable bootcount Jagan Teki
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=20200109085222.22670-7-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
/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