linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] AM35x: Enable OMAP_MUX in defconfig
Date: Thu, 25 Feb 2010 15:03:13 -0800	[thread overview]
Message-ID: <20100225230313.26233.8965.stgit@baageli.muru.com> (raw)
In-Reply-To: <20100225230116.26233.65157.stgit@baageli.muru.com>

From: Ajay Kumar Gupta <ajay.gupta@ti.com>

Enabling OMAP_MUX in defconfig as it is required for EHCI to work.

Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
 arch/arm/configs/am3517_evm_defconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/arm/configs/am3517_evm_defconfig b/arch/arm/configs/am3517_evm_defconfig
index abe9966..edae1c2 100644
--- a/arch/arm/configs/am3517_evm_defconfig
+++ b/arch/arm/configs/am3517_evm_defconfig
@@ -201,7 +201,7 @@ CONFIG_ARCH_OMAP3=y
 # CONFIG_OMAP_DEBUG_POWERDOMAIN is not set
 # CONFIG_OMAP_DEBUG_CLOCKDOMAIN is not set
 CONFIG_OMAP_RESET_CLOCKS=y
-# CONFIG_OMAP_MUX is not set
+CONFIG_OMAP_MUX=y
 # CONFIG_OMAP_MCBSP is not set
 # CONFIG_OMAP_MBOX_FWK is not set
 # CONFIG_OMAP_MPU_TIMER is not set

  parent reply	other threads:[~2010-02-25 23:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 23:02 [PATCH 0/6] omap i2c init fix and trivial board changes for 2.6.34 Tony Lindgren
2010-02-25 23:03 ` [PATCH 1/6] omap: i2c: Fix muxing for command line enabled bus Tony Lindgren
2010-02-25 23:03 ` [PATCH 2/6] Zoom3: Defconfig update Tony Lindgren
2010-02-25 23:03 ` [PATCH 3/6] AM35x: Add missing GPIO mux config for EHCI port Tony Lindgren
2010-02-25 23:03 ` Tony Lindgren [this message]
2010-02-25 23:03 ` [PATCH 5/6] AM3517 EVM: Enable I2C support Tony Lindgren
2010-02-25 23:03 ` [PATCH 6/6] AM3517EVM : correct typo - tca6416 mispelt as tca6516 Tony Lindgren
2010-02-26 23:36 ` [PATCH 7/6] omap2: Initialize Menelaus and MMC for N8X0 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=20100225230313.26233.8965.stgit@baageli.muru.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).