From: Andreas Fenkart <afenkart@gmail.com>
To: linux-mmc@vger.kernel.org
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
pascal.huerst@gmail.com, Andreas Fenkart <afenkart@gmail.com>
Subject: [PATCH v2 4/9] omap_hsmmc: remove un-ready power_saving field in omap2_hsmmc_info
Date: Mon, 29 Sep 2014 11:32:54 +0200 [thread overview]
Message-ID: <1411983179-28677-5-git-send-email-afenkart@gmail.com> (raw)
In-Reply-To: <1411983179-28677-1-git-send-email-afenkart@gmail.com>
these fields are never read, probably an unimplemented feature
or superseded by pm_runtime
Signed-off-by: Andreas Fenkart <afenkart@gmail.com>
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c b/arch/arm/mach-omap2/board-rx51-peripherals.c
index ddfc8df..0a8ac84 100644
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
@@ -500,7 +500,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
.cover_only = true,
.gpio_cd = 160,
.gpio_wp = -EINVAL,
- .power_saving = true,
},
{
.name = "internal",
@@ -510,7 +509,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
.gpio_cd = -EINVAL,
.gpio_wp = -EINVAL,
.nonremovable = true,
- .power_saving = true,
.remux = rx51_mmc2_remux,
},
{} /* Terminator */
diff --git a/arch/arm/mach-omap2/hsmmc.h b/arch/arm/mach-omap2/hsmmc.h
index bdc8870..30c78c1 100644
--- a/arch/arm/mach-omap2/hsmmc.h
+++ b/arch/arm/mach-omap2/hsmmc.h
@@ -16,7 +16,6 @@ struct omap2_hsmmc_info {
bool ext_clock; /* use external pin for input clock */
bool cover_only; /* No card detect - just cover switch */
bool nonremovable; /* Nonremovable e.g. eMMC */
- bool power_saving; /* Try to sleep or power off when possible */
bool deferred; /* mmc needs a deferred probe */
int gpio_cd; /* or -EINVAL */
int gpio_wp; /* or -EINVAL */
--
2.1.0
next prev parent reply other threads:[~2014-09-29 9:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 9:32 [PATCH v2 0/9] unshare and simplify omap_hsmmc platform struct Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 1/9] omap_hsmmc: use separate platform data for ompa3 and omap 1/2 driver Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 2/9] omap_hsmmc: remove unused fields in platform_data Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 3/9] omap_hsmmc: remove un-initialized callbacks from platform data Andreas Fenkart
2014-09-29 9:32 ` Andreas Fenkart [this message]
2014-09-29 9:32 ` [PATCH v2 5/9] omap_hsmmc: remove unused get_context_loss_count callback Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 6/9] omap_hsmmc: remove unnecessary omap_hsmmc_slot_data indirection Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 7/9] omap_hsmmc: pass mmc_priv struct to gpio init / free Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 8/9] omap_hsmmc: Remove unnecessary callbacks from platform data Andreas Fenkart
2014-09-29 9:32 ` [PATCH v2 9/9] omap_hsmmc: remove unused slot_id parameter Andreas Fenkart
2014-10-02 16:42 ` Felipe Balbi
2014-10-02 16:45 ` Tony Lindgren
2014-10-02 16:51 ` Felipe Balbi
2014-10-02 16:36 ` [PATCH v2 0/9] unshare and simplify omap_hsmmc platform struct Tony Lindgren
2014-10-03 13:00 ` Ulf Hansson
2014-10-06 7:34 ` Ulf Hansson
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=1411983179-28677-5-git-send-email-afenkart@gmail.com \
--to=afenkart@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pascal.huerst@gmail.com \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.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