public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@misterjones.org>
To: Enric Balletbo i Serra <eballetbo@gmail.com>
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] omap3: igep3: Fix IGEP module second MMC channel power supply.
Date: Mon, 10 Jan 2011 15:18:10 +0100	[thread overview]
Message-ID: <2a90cfc8fdf83d0adb67c16d2be97784@localhost> (raw)
In-Reply-To: <1294665974-10590-3-git-send-email-eballetbo@gmail.com>


On Mon, 10 Jan 2011 14:26:13 +0100, Enric Balletbo i Serra
<eballetbo@gmail.com> wrote:
> The second MMC channel (used by the WLAN/BT module) is not linked to
> power regulator. This causes the WLAN/BT module to fail being detected
if
> CONFIG_REGULATOR_DUMMY is not set.
> 
> This patch adds the two regulators that actually feed the WLAN/BT module
> (1v8 from the TWL4030 VIO LDO, and a fixed 3v3). With that patch, the
> second channel is properly detected.
> 
> Also change vmmc1 to use symbolic names instead of direct device
> reference.
> 
> Signed-off-by: Enric Balletbo i Serra <eballetbo@gmail.com>

Acked-by: Marc Zyngier <maz@misterjones.org>
-- 
Who you jivin' with that Cosmik Debris?

  reply	other threads:[~2011-01-10 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 13:26 [PATCH 0/3] IGEP board changes for .38 merge window Enric Balletbo i Serra
2011-01-10 13:26 ` [PATCH 1/3] omap3: igep3: Add USB EHCI support for IGEP module Enric Balletbo i Serra
2011-01-10 13:26 ` [PATCH 2/3] omap3: igep3: Fix IGEP module second MMC channel power supply Enric Balletbo i Serra
2011-01-10 14:18   ` Marc Zyngier [this message]
2011-01-10 13:26 ` [PATCH 3/3] omap3: igep2: Add keypad support Enric Balletbo i Serra
2011-01-10 22:38 ` [PATCH 0/3] IGEP board changes for .38 merge window 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=2a90cfc8fdf83d0adb67c16d2be97784@localhost \
    --to=maz@misterjones.org \
    --cc=eballetbo@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /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