From: <Eugen.Hristev@microchip.com>
To: <alexandre.belloni@bootlin.com>, <Ludovic.Desroches@microchip.com>
Cc: <Nicolas.Ferre@microchip.com>, <robh+dt@kernel.org>,
<Claudiu.Beznea@microchip.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<Eugen.Hristev@microchip.com>
Subject: [PATCH 3/3] ARM: configs: at91: enable sama5d4 compatible watchdog
Date: Tue, 11 Feb 2020 08:07:15 +0000 [thread overview]
Message-ID: <1581408369-14469-3-git-send-email-eugen.hristev@microchip.com> (raw)
In-Reply-To: <1581408369-14469-1-git-send-email-eugen.hristev@microchip.com>
From: Eugen Hristev <eugen.hristev@microchip.com>
Enable CONFIG_SAMA5D4_WATCHDOG. This driver is compatible with sam9x60
watchdog timer block.
Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
---
arch/arm/configs/at91_dt_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/at91_dt_defconfig b/arch/arm/configs/at91_dt_defconfig
index f66bb98..4a0ba2a 100644
--- a/arch/arm/configs/at91_dt_defconfig
+++ b/arch/arm/configs/at91_dt_defconfig
@@ -118,6 +118,7 @@ CONFIG_POWER_SUPPLY=y
# CONFIG_HWMON is not set
CONFIG_WATCHDOG=y
CONFIG_AT91SAM9X_WATCHDOG=y
+CONFIG_SAMA5D4_WATCHDOG=y
CONFIG_MFD_ATMEL_FLEXCOM=y
CONFIG_MFD_ATMEL_HLCDC=y
CONFIG_REGULATOR=y
--
2.7.4
next prev parent reply other threads:[~2020-02-11 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 8:07 [PATCH 1/3] ARM: dts: at91: sam9x60: add watchdog node Eugen.Hristev
2020-02-11 8:07 ` [PATCH 2/3] ARM: dts: at91: sam9x60ek: enable " Eugen.Hristev
2020-02-12 11:28 ` Alexandre Belloni
2020-02-11 8:07 ` Eugen.Hristev [this message]
2020-02-12 11:29 ` [PATCH 3/3] ARM: configs: at91: enable sama5d4 compatible watchdog Alexandre Belloni
2020-02-12 11:27 ` [PATCH 1/3] ARM: dts: at91: sam9x60: add watchdog node Alexandre Belloni
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=1581408369-14469-3-git-send-email-eugen.hristev@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).