From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree
Date: Wed, 17 Oct 2012 13:38:00 +0000 [thread overview]
Message-ID: <201210171338.01011.arnd@arndb.de> (raw)
In-Reply-To: <20121015160740.GC7662@gmail.com>
On Monday 15 October 2012, Lee Jones wrote:
> > and so on. What are you actually missing in the properties that
> > are already there?
>
> MMC_CAP_ERASE
This one seems to be set unconditionally on some controllers but
not on others. Why would it need to be configurable?
> MMC_CAP_UHS_SDR12
> MMC_CAP_UHS_SDR25
> MMC_CAP_UHS_DDR50
Could this be derived from max-frequency?
> MMC_CAP_1_8V_DDR
Right, I suppose we need this. Should we have a minimum and maximum
voltage added to the common properties for this?
> MMC_CAP2_DETECT_ON_ERR
> MMC_CAP2_NO_SLEEP_CMD
I don't see these ones being set anywhere, but they were both
added by Ulf. Maybe he can comment on if or why they are needed
in devicetree, rather than being set by the driver unconditionally
or for specific versions of the host controller.
Arnd
next prev parent reply other threads:[~2012-10-17 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 13:15 [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree Lee Jones
2012-10-15 13:15 ` [PATCH 2/2] mmc: mmci: Make use of new DT capability parsing function Lee Jones
2012-10-15 14:20 ` [PATCH 1/2] mmc: core: Support all MMC capabilities when booting from Device Tree Arnd Bergmann
2012-10-15 16:07 ` Lee Jones
2012-10-17 13:38 ` Arnd Bergmann [this message]
2012-10-17 18:53 ` Ulf Hansson
2012-10-17 19:56 ` Philip Rakity
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=201210171338.01011.arnd@arndb.de \
--to=arnd@arndb.de \
--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