From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/7] MMC: mmci: Enable Device Tree support for ux500 variants
Date: Mon, 9 Apr 2012 14:27:18 +0000 [thread overview]
Message-ID: <201204091427.19110.arnd@arndb.de> (raw)
In-Reply-To: <20120406041401.28A993E0BC4@localhost>
On Friday 06 April 2012, Grant Likely wrote:
> Yes, "clock-frequency" already has established usage as an exact clock
> specification. If it is a maximum as you say then something like
> "max-frequency" makes more sense.
>
> Someone was working on a common MMC DT binding. Really all of the MMC
> drivers should use the same binding for the common bits.
Agreed.
Should we use max-frequency or clock-frequency for sdhci though? It looks
like this is both the maximum frequency that it can use and the base frequency
that the actual clock rate is derived from (can be a fraction).
Arnd
next prev parent reply other threads:[~2012-04-09 14:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 9:55 [0/7] Next round of DT enablement for ux500/Snowball Lee Jones
2012-04-05 9:55 ` [PATCH 1/7] ARM: ux500: New DT:ed snowball_platform_devs for one-by-one device enablement Lee Jones
2012-04-10 9:03 ` Linus Walleij
2012-04-10 9:26 ` Lee Jones
2012-04-10 11:02 ` Linus Walleij
2012-04-10 11:15 ` Lee Jones
2012-04-05 9:55 ` [PATCH 2/7] ARM: ux500: New DT:ed u8500_init_devices " Lee Jones
2012-04-10 9:05 ` Linus Walleij
2012-04-05 9:55 ` [PATCH 3/7] drivers/gpio: gpio-nomadik: Apply Device Tree bindings Lee Jones
2012-04-10 9:14 ` Linus Walleij
2012-04-10 9:19 ` Linus Walleij
2012-04-05 9:55 ` [PATCH 4/7] drivers/gpio: gpio-nomadik: Provide documentation for " Lee Jones
2012-04-06 4:20 ` Grant Likely
2012-04-10 7:24 ` Lee Jones
2012-05-11 19:12 ` Grant Likely
2012-05-11 22:18 ` Linus Walleij
2012-05-11 22:24 ` Grant Likely
2012-05-14 8:33 ` Lee Jones
2012-04-05 9:55 ` [PATCH 5/7] ARM: ux500: Rename gpio_keys in the Device Tree file Lee Jones
2012-04-10 9:16 ` Linus Walleij
2012-04-05 9:55 ` [PATCH 6/7] MMC: mmci: Enable Device Tree support for ux500 variants Lee Jones
2012-04-05 12:36 ` Russell King - ARM Linux
2012-04-05 13:45 ` Lee Jones
2012-04-06 4:14 ` Grant Likely
2012-04-09 14:27 ` Arnd Bergmann [this message]
2012-04-09 14:41 ` Chris Ball
2012-04-05 9:55 ` [PATCH 7/7] MMC: mmci: Add required documentation for Device Tree bindings Lee Jones
2012-04-18 13:04 ` Arnd Bergmann
2012-04-18 14:25 ` Pawel Moll
2012-04-18 14:29 ` Lee Jones
2012-04-18 16:32 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2012-04-05 10:25 [PATCH 1/7] ARM: ux500: New DT:ed snowball_platform_devs for one-by-one device enablement Lee Jones
2012-04-05 10:25 ` [PATCH 6/7] MMC: mmci: Enable Device Tree support for ux500 variants Lee Jones
2012-04-13 14:05 [PATCH 0/7 v2] Next round of DT enablement for ux500/Snowball Lee Jones
2012-04-13 14:05 ` [PATCH 6/7] MMC: mmci: Enable Device Tree support for ux500 variants Lee Jones
2012-04-13 14:42 ` Pawel Moll
2012-04-13 14:51 ` Arnd Bergmann
2012-04-13 14:54 ` Lee Jones
2012-04-13 15:05 ` Pawel Moll
2012-04-13 15:16 ` Lee Jones
2012-04-13 15:27 ` Pawel Moll
2012-04-16 8:48 ` Linus Walleij
2012-04-16 9:06 ` Lee Jones
2012-04-16 9:18 ` Linus Walleij
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=201204091427.19110.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;
as well as URLs for NNTP newsgroup(s).