All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francisco Alecrim <alecrim@gmail.com>
To: linux-omap@vger.kernel.org
Cc: Francisco Alecrim <francisco.alecrim@openbossa.org>,
	Francisco Alecrim <alecrim@gmail.com>
Subject: [PATCH] n8x0_defconfig: active cbus, retu-wd and omap-wd
Date: Wed,  6 Jan 2010 22:20:00 -0400	[thread overview]
Message-ID: <1262830800-30192-1-git-send-email-alecrim@gmail.com> (raw)

From: Francisco Alecrim <francisco.alecrim@openbossa.org>

It's critical for correct n8x0 operation. Device turn power-off after some
seconds without these options.

Signed-off-by: Francisco Alecrim <alecrim@gmail.com>
---
 arch/arm/configs/n8x0_defconfig |   26 +++++++++++++++++++++++++-
 1 files changed, 25 insertions(+), 1 deletions(-)

diff --git a/arch/arm/configs/n8x0_defconfig b/arch/arm/configs/n8x0_defconfig
index e6f667c..66b1d3f 100644
--- a/arch/arm/configs/n8x0_defconfig
+++ b/arch/arm/configs/n8x0_defconfig
@@ -661,7 +661,19 @@ CONFIG_GPIOLIB=y
 # CONFIG_HWMON is not set
 # CONFIG_THERMAL is not set
 # CONFIG_THERMAL_HWMON is not set
-# CONFIG_WATCHDOG is not set
+CONFIG_WATCHDOG=y
+# CONFIG_WATCHDOG_NOWAYOUT is not set
+
+#
+# Watchdog Device Drivers
+#
+# CONFIG_SOFT_WATCHDOG is not set
+CONFIG_OMAP_WATCHDOG=y
+
+#
+# USB-based Watchdog Cards
+#
+# CONFIG_USBPCWATCHDOG is not set
 CONFIG_SSB_POSSIBLE=y
 
 #
@@ -851,6 +863,18 @@ CONFIG_RTC_LIB=y
 # CONFIG_STAGING is not set
 
 #
+# CBUS support
+#
+CONFIG_CBUS=y
+# CONFIG_CBUS_TAHVO is not set
+CONFIG_CBUS_RETU=y
+# CONFIG_CBUS_RETU_USER is not set
+# CONFIG_CBUS_RETU_POWERBUTTON is not set
+# CONFIG_CBUS_RETU_RTC is not set
+CONFIG_CBUS_RETU_WDT=y
+# CONFIG_CBUS_RETU_HEADSET is not set
+
+#
 # File systems
 #
 # CONFIG_EXT2_FS is not set
-- 
1.6.3.3


             reply	other threads:[~2010-01-07  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07  2:20 Francisco Alecrim [this message]
2010-01-11 22:42 ` [APPLIED] [PATCH] n8x0_defconfig: active cbus, retu-wd and omap-wd Tony Lindgren

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=1262830800-30192-1-git-send-email-alecrim@gmail.com \
    --to=alecrim@gmail.com \
    --cc=francisco.alecrim@openbossa.org \
    --cc=linux-omap@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.