From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 8/8] ARM: ux500: Remove traces of the ios_handler from platform code
Date: Mon, 21 Jan 2013 13:11:36 +0000 [thread overview]
Message-ID: <20130121131136.GA6551@gmail.com> (raw)
In-Reply-To: <CAPDyKFosXFxQCAeKNnmvM4rY5_otj=FfYdR1Vi_HBq_kk130eQ@mail.gmail.com>
On Fri, 14 Dec 2012, Ulf Hansson wrote:
> On 13 December 2012 14:22, Lee Jones <lee.jones@linaro.org> wrote:
> > Now MMCI on/off functionality is using the regulator framework
> > from the MMCI driver, there is no need to keep the ios_handler
> > laying around, duplicating functionality. So we're removing it.
> >
> > Acked-by: Linus Walleij <linus.walleij@linaro.org>
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
What's the latest on these Ulf? Have they been taken in yet?
> > ---
> > arch/arm/mach-ux500/board-mop500-sdi.c | 52 --------------------------------
> > 1 file changed, 52 deletions(-)
> >
> > diff --git a/arch/arm/mach-ux500/board-mop500-sdi.c b/arch/arm/mach-ux500/board-mop500-sdi.c
> > index 9c8e4a9..5a798d6 100644
> > --- a/arch/arm/mach-ux500/board-mop500-sdi.c
> > +++ b/arch/arm/mach-ux500/board-mop500-sdi.c
> > @@ -31,35 +31,6 @@
> > * SDI 0 (MicroSD slot)
> > */
> >
> > -/* GPIO pins used by the sdi0 level shifter */
> > -static int sdi0_en = -1;
> > -static int sdi0_vsel = -1;
> > -
> > -static int mop500_sdi0_ios_handler(struct device *dev, struct mmc_ios *ios)
> > -{
> > - switch (ios->power_mode) {
> > - case MMC_POWER_UP:
> > - case MMC_POWER_ON:
> > - /*
> > - * Level shifter voltage should depend on vdd to when deciding
> > - * on either 1.8V or 2.9V. Once the decision has been made the
> > - * level shifter must be disabled and re-enabled with a changed
> > - * select signal in order to switch the voltage. Since there is
> > - * no framework support yet for indicating 1.8V in vdd, use the
> > - * default 2.9V.
> > - */
> > - gpio_direction_output(sdi0_vsel, 0);
> > - gpio_direction_output(sdi0_en, 1);
> > - break;
> > - case MMC_POWER_OFF:
> > - gpio_direction_output(sdi0_vsel, 0);
> > - gpio_direction_output(sdi0_en, 0);
> > - break;
> > - }
> > -
> > - return 0;
> > -}
> > -
> > #ifdef CONFIG_STE_DMA40
> > struct stedma40_chan_cfg mop500_sdi0_dma_cfg_rx = {
> > .mode = STEDMA40_MODE_LOGICAL,
> > @@ -81,7 +52,6 @@ static struct stedma40_chan_cfg mop500_sdi0_dma_cfg_tx = {
> > #endif
> >
> > struct mmci_platform_data mop500_sdi0_data = {
> > - .ios_handler = mop500_sdi0_ios_handler,
> > .ocr_mask = MMC_VDD_29_30,
> > .f_max = 50000000,
> > .capabilities = MMC_CAP_4_BIT_DATA |
> > @@ -101,22 +71,6 @@ struct mmci_platform_data mop500_sdi0_data = {
> >
> > static void sdi0_configure(struct device *parent)
> > {
> > - int ret;
> > -
> > - ret = gpio_request(sdi0_en, "level shifter enable");
> > - if (!ret)
> > - ret = gpio_request(sdi0_vsel,
> > - "level shifter 1v8-3v select");
> > -
> > - if (ret) {
> > - pr_warning("unable to config sdi0 gpios for level shifter.\n");
> > - return;
> > - }
> > -
> > - /* Select the default 2.9V and enable level shifter */
> > - gpio_direction_output(sdi0_vsel, 0);
> > - gpio_direction_output(sdi0_en, 1);
> > -
> > /* Add the device, force v2 to subrevision 1 */
> > db8500_add_sdi0(parent, &mop500_sdi0_data, U8500_SDI_V2_PERIPHID);
> > }
> > @@ -124,8 +78,6 @@ static void sdi0_configure(struct device *parent)
> > void mop500_sdi_tc35892_init(struct device *parent)
> > {
> > mop500_sdi0_data.gpio_cd = GPIO_SDMMC_CD;
> > - sdi0_en = GPIO_SDMMC_EN;
> > - sdi0_vsel = GPIO_SDMMC_1V8_3V_SEL;
> > sdi0_configure(parent);
> > }
> >
> > @@ -264,8 +216,6 @@ void __init snowball_sdi_init(struct device *parent)
> > /* External Micro SD slot */
> > mop500_sdi0_data.gpio_cd = SNOWBALL_SDMMC_CD_GPIO;
> > mop500_sdi0_data.cd_invert = true;
> > - sdi0_en = SNOWBALL_SDMMC_EN_GPIO;
> > - sdi0_vsel = SNOWBALL_SDMMC_1V8_3V_GPIO;
> > sdi0_configure(parent);
> > }
> >
> > @@ -277,8 +227,6 @@ void __init hrefv60_sdi_init(struct device *parent)
> > db8500_add_sdi4(parent, &mop500_sdi4_data, U8500_SDI_V2_PERIPHID);
> > /* External Micro SD slot */
> > mop500_sdi0_data.gpio_cd = HREFV60_SDMMC_CD_GPIO;
> > - sdi0_en = HREFV60_SDMMC_EN_GPIO;
> > - sdi0_vsel = HREFV60_SDMMC_1V8_3V_GPIO;
> > sdi0_configure(parent);
> > /* WLAN SDIO channel */
> > db8500_add_sdi1(parent, &mop500_sdi1_data, U8500_SDI_V2_PERIPHID);
> >
>
> Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-01-21 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 13:22 [PATCH 1/8] Functionality add and bug-fixes related to MMCI regulators Lee Jones
2012-12-13 13:22 ` [PATCH 1/8] mmc: mmci: Move ios_handler functionality into the driver Lee Jones
2013-01-21 14:06 ` Lee Jones
2013-01-21 20:25 ` Ulf Hansson
2013-01-22 8:46 ` Lee Jones
2012-12-13 13:22 ` [PATCH 2/8] ARM: ux500: Set correct MMCI regulator voltages in the ux5x0 Device Tree Lee Jones
2012-12-13 13:22 ` [PATCH 3/8] ARM: ux500: Specify the ux5x0 MMCI regulator's on/off GPIO as high-enable Lee Jones
2012-12-13 13:22 ` [PATCH 4/8] ARM: ux500: Specify which IOS regulator to use for MMCI Lee Jones
2012-12-13 13:22 ` [PATCH 5/8] ARM: ux500: Use the correct name when supplying a GPIO enable pin Lee Jones
2012-12-13 13:22 ` [PATCH 6/8] ARM: ux500: Setup correct settling time for the MMCI regulator Lee Jones
2012-12-13 13:22 ` [PATCH 7/8] ARM: ux500: Use the GPIO regulator framework for SDI0's 'en' and 'vsel' Lee Jones
2012-12-13 15:09 ` Ulf Hansson
2013-01-21 13:11 ` Lee Jones
2012-12-13 13:22 ` [PATCH 8/8] ARM: ux500: Remove traces of the ios_handler from platform code Lee Jones
2012-12-14 8:25 ` Ulf Hansson
2013-01-21 13:11 ` Lee Jones [this message]
2013-01-23 10:04 ` Linus Walleij
2013-01-23 10:07 ` Linus Walleij
2013-01-23 11:27 ` Lee Jones
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=20130121131136.GA6551@gmail.com \
--to=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).