From: josephl@nvidia.com (Joseph Lo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5 7/9] ARM: dts: tegra: add non-removable and keep-power-in-suspend property for MMC
Date: Wed, 3 Apr 2013 14:28:32 +0800 [thread overview]
Message-ID: <1364970512.16957.15.camel@jlo-ubuntu-64.nvidia.com> (raw)
In-Reply-To: <20130403054549.GA6764@avionic-0098.mockup.avionic-design.de>
On Wed, 2013-04-03 at 13:45 +0800, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Tue, Apr 02, 2013 at 01:58:41PM -0600, Stephen Warren wrote:
> > On 04/02/2013 05:20 AM, Joseph Lo wrote:
> > > This patch adds "non-removable" property of MMC host where the eMMC device
> > > is for Tegra platform.
> > >
> > > And the "keep-power-in-suspend" property was used for the SDIO device that
> > > need this to go into suspend mode (e.g. BRCM43xx series).
> >
> > > arch/arm/boot/dts/tegra20-paz00.dts | 1 +
> > > arch/arm/boot/dts/tegra20-seaboard.dts | 2 ++
> > > arch/arm/boot/dts/tegra20-ventana.dts | 2 ++
> > > arch/arm/boot/dts/tegra20-whistler.dts | 1 +
> > > arch/arm/boot/dts/tegra30-beaver.dts | 1 +
> > > arch/arm/boot/dts/tegra30-cardhu-a02.dts | 1 +
> > > arch/arm/boot/dts/tegra30-cardhu-a04.dts | 1 +
> > > arch/arm/boot/dts/tegra30-cardhu.dtsi | 1 +
> >
> > I think there are a bunch of other boards that need a similar change,
> > right? There are certainly eMMC devices on other boards, and shouldn't
> > they be marked with non-removable? In particular, Beaver, Dalmore, and
> > Pluto, and likely some/all of the Colibri and Avionic Design boards. I
> > think it should be obvious which SDHCI devices need this, since there
> > won't be any cd-gpios property and the bus-width will likely be 8.
>
> For Tegra20 Tamonten we don't use eMMC. Ideally we'd be using NAND to
> boot from but that doesn't have mainline support. I have a semi-working
> patch and will probably spend some more time getting it ready. The MMC
> cards are all removable, though I guess since they are the boot device
> they still should remain powered in suspend?
>
The "non-removable" property is a specific property to avoid the risk of
writing back data to a different card after resume. If you just want to
test the suspend function, you can add "mmc_core.removable=0" in your
boot arg.
The "keep-power-in-suspend" is used for the BRCM43xx series SDIO device.
Without this, it can't go into suspend mode.
next prev parent reply other threads:[~2013-04-03 6:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 11:20 [PATCH V5 0/9] ARM: tegra: add platform suspend support Joseph Lo
2013-04-02 11:20 ` [PATCH V5 1/9] gpio: tegra: add gpio wakeup source handling Joseph Lo
2013-04-03 16:29 ` Linus Walleij
2013-04-03 16:52 ` Stephen Warren
2013-04-03 21:20 ` Stephen Warren
2013-04-02 11:20 ` [PATCH V5 2/9] ARM: tegra: irq: add wake up handling Joseph Lo
2013-04-02 11:20 ` [PATCH V5 3/9] ARM: dt: tegra: add bindings of power management configurations for PMC Joseph Lo
2013-04-02 11:20 ` [PATCH V5 4/9] ARM: tegra: pm: add platform suspend support Joseph Lo
2013-04-02 11:20 ` [PATCH V5 5/9] ARM: dts: tegra: add power gpio keys to DT Joseph Lo
2013-04-02 11:20 ` [PATCH V5 6/9] ARM: dts: tegra: whistler: add wakeup source for KBC Joseph Lo
2013-04-02 11:20 ` [PATCH V5 7/9] ARM: dts: tegra: add non-removable and keep-power-in-suspend property for MMC Joseph Lo
2013-04-02 19:58 ` Stephen Warren
2013-04-03 5:45 ` Thierry Reding
2013-04-03 6:28 ` Joseph Lo [this message]
2013-04-03 6:59 ` Joseph Lo
2013-04-02 11:20 ` [PATCH V5 8/9] ARM: tegra: config: defconfig update Joseph Lo
2013-04-02 11:20 ` [PATCH V5 9/9] ARM: dts: tegra: add the PM configurations of PMC Joseph Lo
2013-04-02 20:00 ` Stephen Warren
2013-04-03 5:59 ` Thierry Reding
2013-04-03 6:34 ` Joseph Lo
2013-04-03 7:04 ` Thierry Reding
2013-04-03 7:11 ` Joseph Lo
2013-04-03 7:19 ` Thierry Reding
2013-04-03 7:33 ` Joseph Lo
2013-04-02 19:39 ` [PATCH V5 0/9] ARM: tegra: add platform suspend support Stephen Warren
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=1364970512.16957.15.camel@jlo-ubuntu-64.nvidia.com \
--to=josephl@nvidia.com \
--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).