linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/20] mmc: mmci: Update DT documentation
Date: Fri, 21 Mar 2014 10:03:39 -0500	[thread overview]
Message-ID: <CAL_JsqJbaxayELNt+d1VSfFyD58eRYQM=d15RaFcFQKbot3iaw@mail.gmail.com> (raw)
In-Reply-To: <1395404057-27835-4-git-send-email-ulf.hansson@linaro.org>

On Fri, Mar 21, 2014 at 7:14 AM, Ulf Hansson <ulf.hansson@linaro.org> wrote:
> Document how to configure the regulator supplies and add an example of
> a typical mmci DT node.
>
> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
> ---
>  Documentation/devicetree/bindings/mmc/mmci.txt |   35 ++++++++++++++++++++++--
>  1 file changed, 33 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/mmci.txt b/Documentation/devicetree/bindings/mmc/mmci.txt
> index 2b584ca..d167562 100644
> --- a/Documentation/devicetree/bindings/mmc/mmci.txt
> +++ b/Documentation/devicetree/bindings/mmc/mmci.txt
> @@ -9,7 +9,38 @@ by mmc.txt and the properties used by the mmci driver.
>  Required properties:
>  - compatible             : contains "arm,pl18x", "arm,primecell".
>  - arm,primecell-periphid : contains the PrimeCell Peripheral ID.

This should not be required. This is only for if the peripheral ID is
wrong in the h/w.

> +- vmmc-supply            : phandle to the regulator device tree node.

You cannot add new required properties as that breaks the ABI. The
exception is if you *know* it is okay to break all users of this
binding.

>  Optional properties:
> -- mmc-cap-mmc-highspeed  : indicates whether MMC is high speed capable
> -- mmc-cap-sd-highspeed   : indicates whether SD is high speed capable
> +- mmc-cap-mmc-highspeed  : indicates whether MMC is high speed capable.
> +- mmc-cap-sd-highspeed   : indicates whether SD is high speed capable.
> +- vqmmc-supply           : phandle to the regulator device tree node.

Is this a standard property? If not, explain what vmmc and vgmmc are
for and what the difference is.

> +
> +Example:
> +
> +sdi0_per1 at 80126000 {
> +       compatible = "arm,pl18x", "arm,primecell";
> +       arm,primecell-periphid = <0x10480180>;

Drop this from the example.

> +       reg = <0x80126000 0x1000>;
> +       interrupts = <0 60 IRQ_TYPE_LEVEL_HIGH>;
> +
> +       dmas = <&dma 29 0 0x2>, /* Logical - DevToMem */
> +              <&dma 29 0 0x0>; /* Logical - MemToDev */
> +       dma-names = "rx", "tx";
> +
> +       clocks = <&prcc_kclk 1 5>, <&prcc_pclk 1 5>;
> +       clock-names = "sdi", "apb_pclk";
> +
> +       max-frequency = <100000000>;
> +       bus-width = <4>;
> +       mmc-cap-sd-highspeed;
> +       mmc-cap-mmc-highspeed;
> +       cd-gpios  = <&gpio2 31 0x4>; // 95
> +
> +       vmmc-supply = <&ab8500_ldo_aux3_reg>;
> +       vqmmc-supply = <&vmmci>;
> +
> +       pinctrl-names = "default", "sleep";
> +       pinctrl-0 = <&sdi0_default_mode>;
> +       pinctrl-1 = <&sdi0_sleep_mode>;
> +};
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-03-21 15:03 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 12:13 [PATCH 00/20] mmc: mmci: Improve DT support Ulf Hansson
2014-03-21 12:13 ` [PATCH 01/20] mmc: mmci: Convert to the mmc gpio API Ulf Hansson
2014-03-21 12:13 ` [PATCH 02/20] mmc: mmci: Convert to devm functions Ulf Hansson
2014-03-21 12:14 ` [PATCH 03/20] mmc: mmci: Update DT documentation Ulf Hansson
2014-03-21 15:03   ` Rob Herring [this message]
2014-03-24  9:03     ` Ulf Hansson
2014-03-21 12:14 ` [PATCH 04/20] mmc: mmci: Move signal directions bits into DT include file Ulf Hansson
2014-03-25 21:22   ` Linus Walleij
2014-03-25 23:05     ` Ulf Hansson
2014-03-28 21:03       ` Linus Walleij
2014-03-31 13:56         ` Ulf Hansson
2014-03-21 12:14 ` [PATCH 05/20] mmc: mmci: Add DT bindings for signal direction Ulf Hansson
2014-03-21 15:20   ` Rob Herring
2014-03-24  9:14     ` Ulf Hansson
2014-03-24 13:45       ` Rob Herring
2014-03-21 12:14 ` [PATCH 06/20] mmc: mmci: Use the common mmc DT parser Ulf Hansson
2014-03-21 12:14 ` [PATCH 07/20] ARM: ux500: Add mmci signal directions in DT for href Ulf Hansson
2014-03-21 12:14 ` [PATCH 08/20] ARM: ux500: Convert to the common mmc DT bindings for highspeed mode Ulf Hansson
2014-03-25 21:37   ` Linus Walleij
2014-03-21 12:14 ` [PATCH 09/20] ARM: nomadik: " Ulf Hansson
2014-03-25 21:37   ` Linus Walleij
2014-03-21 12:14 ` [PATCH 10/20] ARM: u300: " Ulf Hansson
2014-03-25 21:38   ` Linus Walleij
2014-03-21 12:14 ` [PATCH 11/20] mmc: mmci: Mark the DT bindings for highspeed mode as deprecated Ulf Hansson
2014-03-21 12:14 ` [PATCH 12/20] mmc: mmci: Enable MMC_CAP_CMD23 Ulf Hansson
2014-03-21 12:14 ` [PATCH 13/20] ARM: ux500: Add the mmc capabilities flags to DT Ulf Hansson
2014-03-25 21:39   ` Linus Walleij
2014-03-21 12:14 ` [PATCH 14/20] regulator: db8500-prcmu: Set 1.8V as a fixed voltage for vsmps2 Ulf Hansson
2014-03-21 12:25   ` Mark Brown
2014-03-21 13:03     ` Ulf Hansson
2014-03-21 17:47   ` Mark Brown
2014-03-21 12:14 ` [PATCH 15/20] ARM: ux500: Add a vmmc regulator through DT for the poped eMMC for href Ulf Hansson
2014-03-25 21:45   ` Linus Walleij
2014-03-26  9:27     ` Ulf Hansson
2014-03-26  9:31       ` Ulf Hansson
2014-03-21 12:14 ` [PATCH 16/20] ARM: ux500: Remove redundant board file for mmci platform data Ulf Hansson
2014-03-25 21:45   ` Linus Walleij
2014-03-21 12:14 ` [PATCH 17/20] mmc: mmci: Enforce DT for signal direction Ulf Hansson
2014-03-21 12:14 ` [PATCH 18/20] mmc: mmci: Enforce mmc capabilities through DT Ulf Hansson
2014-03-21 12:14 ` [PATCH 19/20] mmc: mmci: Enforce DMA configuration " Ulf Hansson
2014-03-21 12:14 ` [PATCH 20/20] mmc: mmci: Enforce max frequency " Ulf Hansson

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='CAL_JsqJbaxayELNt+d1VSfFyD58eRYQM=d15RaFcFQKbot3iaw@mail.gmail.com' \
    --to=robherring2@gmail.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).