Messages in this thread | | | Date | Fri, 24 Jul 2009 15:59:35 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH 1/2] MMC Agressive clocking framework v5 |
| |
On Fri, 24 Jul 2009 17:03:01 -0500 "Madhusudhan" <madhu.cr@ti.com> wrote:
> > > -----Original Message----- > > From: Adrian Hunter [mailto:adrian.hunter@nokia.com] > > Sent: Thursday, July 23, 2009 1:16 PM > > To: Linus Walleij > > Cc: Linus Walleij; Andrew Morton; linux-kernel@vger.kernel.org; Pierre > > Ossman; linux-arm-kernel@lists.arm.linux.org.uk; David Vrabel; > > marek.vasut@gmail.com; Madhusudhan Chikkature > > Subject: Re: [PATCH 1/2] MMC Agressive clocking framework v5 > > > > Hi > > > > Have you considered using our enable/disable approach instead? > > > > It is here: > > > > http://groups.google.com/group/linux.kernel/browse_frm/thread/a5caec1de127 > > 4be5/2ba7dee2a187a268 > > > > Perhaps it meets your needs, whereas your patches do not seem > > to cover the functionality we need. > > > > The patch #28 "The omap hsmmc driver code refactoring" in the series does > not seem to apply.
(top-posting repaired - please don't!)
I got one reject when applying that patch, due to mmc-register-mmci-omap-hs-using-platform_driver_probe.patch. It was simple to fix that up.
| |