[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <95608CFE3D0C064B8468DB61F8403BE036C19F9C0D@PDSMSX501.ccr.corp.intel.com>
Date: Mon, 15 Jun 2009 20:05:14 +0800
From: "Li, Jiebing" <jiebing.li@...el.com>
To: Pierre Ossman <pierre@...man.eu>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Johnson, Charles F" <charles.f.johnson@...el.com>,
"Zhu, Daniel" <daniel.zhu@...el.com>,
"Yuan, Hang" <hang.yuan@...el.com>,
"Li, Jiebing" <jiebing.li@...el.com>
Subject: [PATCH 0/1] MMC: SDIO driver for Intel Moorestown platform
Hi Pierre and all,
Here's a SDIO driver code patch for Intel Moorestown platform. Per your response of my code submission last month, I modified the code and hope that you could spare time to review this patch, which is used for SDIO card power management. It's very important for MID products like Moorestown, as power saving is the key point for such embedded products.
Last time you asked me the use cases for the code. The following is my statement:
1. sdio_bus_suspend()/sdui_bus_resume() and mmc_sdio_suspend()/mmc_sdio_resume():
Currently SDIO bus driver doesn't have suspend/resume interface, We need this to suspend the functions one by one and then the whole card when the platform is put in S3/S4/S5 states.
2. sdio_external_suspend_device()/sdio_external_resume_device():
Also, similar to USB, we would like to be able to selectively suspend a particular function using sysfs interface for power management scheme (non-ACPI) if the function is not in use.
3. sdio_reset_device():
It comes to solve a scenario where there is a hang in the Host Interface HW, (i.e. the driver cannot access the device). In this case the function driver can detect that something is broken (using some sw watchdog for example), but it cannot reset its function (host interface is broken).
Thanks and regards,
Jiebing Li--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists