From: Tony Lindgren <tony@atomide.com>
To: NeilBrown <neilb@suse.de>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Andreas Fenkart <afenkart@gmail.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
GTA04 owners <gta04-owner@goldelico.com>,
NeilBrown <neil@brown.name>,
linux-omap <linux-omap@vger.kernel.org>,
Florian Vaussard <florian.vaussard@epfl.ch>,
Ash Charles <ash@gumstix.com>
Subject: Re: [PATCH 3/4] mmc: sdio: support switching to 1-bit before turning off clocks
Date: Wed, 4 Mar 2015 07:08:27 -0800 [thread overview]
Message-ID: <20150304150827.GA13520@atomide.com> (raw)
In-Reply-To: <20150304162848.2d33914d@notabene.brown>
* NeilBrown <neilb@suse.de> [150303 21:29]:
> On Tue, 3 Mar 2015 14:53:55 -0800 Tony Lindgren <tony@atomide.com> wrote:
> >
> > --- a/arch/arm/boot/dts/omap3-gta04.dtsi
> > +++ b/arch/arm/boot/dts/omap3-gta04.dtsi
> > @@ -367,6 +367,7 @@
> > };
> >
> > &mmc2 {
> > + interrupts-extended = <&intc 86 &omap3_pmx_core 0x12e>;
> > vmmc-supply = <&vaux4>;
> > bus-width = <4>;
> > ti,non-removable;
>
> I had
>
> + interrupts-extended = <&intc 86 &gpio5 5 0>; /* GPIO_133 */
> + pinctrl-names = "default", "idle";
> + pinctrl-0 = <&mmc2_pins>;
> + pinctrl-1 = <&mmc2_cirq_pin>;
>
> together with
>
> + mmc2_cirq_pin: pinmux_cirq_pin {
> + pinctrl-single,pins = <
> + OMAP3_CORE1_IOPAD(0x215e, PIN_INPUT_PULLUP | MUX_MODE4)
> + >;
> + };
> +
>
>
> and a longer definition for mmc2_pins.
>
> Is that one line reconfigure the pin on demand? How does that work?
Well the remuxing of the mmc2 dat1 pin is not needed on omap3/4/5.
These SoCs have the iochain wake-up events.
Remuxing is needed on SoCs with no iochain wake-up events, such as
am355x, am437x and dra7 variants.
Not sure if we actually have the gpio5 bank wake-up the system
properly currently from off-idle. It could be that only gpio1 bank
is currently capable of wake-up from off-idle without needing
to use the iochain wake-up also for GPIO lines.
Regards,
Tony
next prev parent reply other threads:[~2015-03-04 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 2:42 [PATCH 0/4] Switch to 1-bit mode SDIO before disabling clocks NeilBrown
2015-02-24 2:42 ` [PATCH 2/4] mmc: core: allow non-blocking form of mmc_claim_host NeilBrown
2015-03-23 9:58 ` Ulf Hansson
2015-03-23 15:19 ` Ulf Hansson
2015-02-24 2:42 ` [PATCH 1/4] mmc: core: fold mmc_set_bus_width calls into sdio_enable_4bit_bus NeilBrown
2015-03-23 9:34 ` Ulf Hansson
2015-02-24 2:42 ` [PATCH 3/4] mmc: sdio: support switching to 1-bit before turning off clocks NeilBrown
2015-03-03 22:53 ` Tony Lindgren
2015-03-04 5:28 ` NeilBrown
2015-03-04 15:08 ` Tony Lindgren [this message]
2015-03-23 9:10 ` Ulf Hansson
2015-03-25 21:49 ` NeilBrown
2015-02-24 2:42 ` [PATCH 4/4] mmc: omap_hsmmc: switch to 1-bit before stopping clocks NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2015-01-30 19:05 [PATCH-v2 0/4] mmc: switch to 1-bit mode which " NeilBrown
2015-01-30 19:05 ` [PATCH 3/4] mmc: sdio: support switching to 1-bit before turning off clocks NeilBrown
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=20150304150827.GA13520@atomide.com \
--to=tony@atomide.com \
--cc=afenkart@gmail.com \
--cc=ash@gumstix.com \
--cc=florian.vaussard@epfl.ch \
--cc=gta04-owner@goldelico.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=neil@brown.name \
--cc=neilb@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).