From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Li, Jiebing" <jiebing.li@intel.com>
Cc: Pierre Ossman <drzeus@drzeus.cx>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Johnson, Charles F" <charles.f.johnson@intel.com>,
"Zhu, Daniel" <daniel.zhu@intel.com>,
"Yuan, Hang" <hang.yuan@intel.com>,
"Pasrija, Geeta" <geeta.pasrija@intel.com>
Subject: Re: [PATCH 2/2] MMC: MMC/SD/CE-ATA/SDIO driver for Intel Moorestown platform
Date: Thu, 30 Apr 2009 13:11:18 +0100 [thread overview]
Message-ID: <20090430121118.GA22480@srcf.ucam.org> (raw)
In-Reply-To: <95608CFE3D0C064B8468DB61F8403BE029D298B1FF@PDSMSX501.ccr.corp.intel.com>
On Thu, Apr 30, 2009 at 05:19:06PM +0800, Li, Jiebing wrote:
>
> This patch enables support of SDIO bus driver suspend/resume operation and supply sysfs interface for user
> to call suspend/resume selectively.Remind that this function should work together with SDIO device driver's
> suspend/resume function.
We used to have similar functionality in the PCI layer, but it got
removed on the assumption that this kind of thing should be handled by
the drivers being sufficiently intelligent. What's the use case for
this?
> And Moorestown's specific code is added into this patch to enable the second SDIO slot of the host controller.
That should probably be sent as a separate patch.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-04-30 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 9:14 [PATCH 0/2] MMC: MMC/SD/CE-ATA/SDIO driver for Intel Moorestown platform Li, Jiebing
2009-04-30 9:16 ` [PATCH 1/2] " Li, Jiebing
2009-04-30 13:44 ` Alan Cox
2009-05-10 18:29 ` Pierre Ossman
2009-04-30 9:19 ` [PATCH 2/2] " Li, Jiebing
2009-04-30 12:11 ` Matthew Garrett [this message]
2009-05-10 18:42 ` Pierre Ossman
2009-05-20 10:55 ` Li, Jiebing
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=20090430121118.GA22480@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=charles.f.johnson@intel.com \
--cc=daniel.zhu@intel.com \
--cc=drzeus@drzeus.cx \
--cc=geeta.pasrija@intel.com \
--cc=hang.yuan@intel.com \
--cc=jiebing.li@intel.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox