From: Russell King <rmk@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: kishore kadiyala <kishore.kadiyala@ti.com>,
linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org,
madhu.cr@ti.com, jarkko.lavinen@nokia.com, paul@pwsan.com,
adrian.hunter@nokia.com
Subject: Re: [PATCH v3 2/5] OMAP4 HSMMC: Adding hsmmc support to board file
Date: Fri, 14 May 2010 23:05:08 +0100 [thread overview]
Message-ID: <20100514220508.GC7185@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20100514215651.GI3428@atomide.com>
On Fri, May 14, 2010 at 02:56:51PM -0700, Tony Lindgren wrote:
> * kishore kadiyala <kishore.kadiyala@ti.com> [100513 13:06]:
> > Support for MMC1 & MMC2 controllers is added to the board file.
> > Also includes configuration of MMC1 Card detect initially.
>
> This patch does not seem to apply, I don't know where you're getting
> the sdp4430_vmmc_supply in this patch?
>
> I suggest you forget about the card detect patches for now and
> first produce a minimal set of patches to get the MMC working
> for board-4430sdp.c. The card detect patches should be applied
> only after board-4430sdp.c works for MMC. And we're running out
> of time for this merge window.
Absolutely - we _really_ _really_ _really_ need to get MMC usable
on the 4430SDP for this merge window - don't care about the card
detection provided the system can find a MMC card which is left
plugged in.
To do this makes the overall 4430SDP more usable than it currently
is with mainline kernels.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2010-05-14 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 20:11 [PATCH v3 2/5] OMAP4 HSMMC: Adding hsmmc support to board file kishore kadiyala
2010-05-14 21:56 ` Tony Lindgren
2010-05-14 22:05 ` Russell King [this message]
2010-05-15 6:11 ` Shilimkar, Santosh
2010-05-15 8:57 ` Shilimkar, Santosh
2010-05-15 17:08 ` kishore kadiyala
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=20100514220508.GC7185@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=adrian.hunter@nokia.com \
--cc=jarkko.lavinen@nokia.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=paul@pwsan.com \
--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 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.