From: Sergio Prado <sergio.prado@e-labworks.com>
To: Rob Herring <robh@kernel.org>
Cc: ulf.hansson@linaro.org, mark.rutland@arm.com,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ben-linux@fluff.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/2] dt-bindings: mmc: add DT binding for S3C24XX MMC/SD/SDIO controller
Date: Tue, 24 Jan 2017 16:49:32 -0200 [thread overview]
Message-ID: <20170124184932.GA20814@sprado-desktop> (raw)
In-Reply-To: <20170118223816.nccyc7aoa7succsi@rob-hp-laptop>
On Wed, Jan 18, 2017 at 04:38:16PM -0600, Rob Herring wrote:
> On Fri, Jan 13, 2017 at 01:05:52PM -0200, Sergio Prado wrote:
> > +This file documents differences between the core mmc properties described by
> > +mmc.txt and the properties used by the Samsung S3C24XX MMC/SD/SDIO controller
> > +implementation.
> > +
> > +Required SoC Specific Properties:
> > +- compatible: should be one of the following
> > + - "samsung,s3c2410-sdi": for controllers compatible with s3c2410
> > + - "samsung,s3c2412-sdi": for controllers compatible with s3c2412
> > + - "samsung,s3c2440-sdi": for controllers compatible with s3c2440
> > +- clocks: Should reference the controller clock
> > +- clock-names: Should contain "sdi"
>
> You are missing things from the example.
Properties "compatible", "clocks" and "clock-names" are documented.
Properties "bus-width", "cd-gpios" and "wp-gpios" are documented in
mmc.txt as I described before the example. Should I describe them again?
Do I need to document common properties like "pinctrl-names",
"pinctrl-0", "reg" and "interrupts"?
>
> > +
> > +Example:
> > + mmc0: mmc@5a000000 {
> > + compatible = "samsung,s3c2440-sdi";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&sdi_pins>;
> > + reg = <0x5a000000 0x100000>;
> > + interrupts = <0 0 21 3>;
> > + clocks = <&clocks PCLK_SDI>;
> > + clock-names = "sdi";
> > + bus-width = <4>;
> > + cd-gpios = <&gpg 8 GPIO_ACTIVE_LOW>;
> > + wp-gpios = <&gph 8 GPIO_ACTIVE_LOW>;
> > + };
> > +
> > + Note: This example shows both SoC specific and board specific properties
> > + in a single device node. The properties can be actually be separated
> > + into SoC specific node and board specific node.
>
> The source structure is not relavent to the binding.
OK.
>
> Rob
--
Sergio Prado
Embedded Labworks
Office: +55 11 2628-3461
Mobile: +55 11 97123-3420
next prev parent reply other threads:[~2017-01-24 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 15:05 [PATCH v3 0/2] mmc: host: s3cmci: add device tree support Sergio Prado
2017-01-13 15:05 ` [PATCH v3 1/2] dt-bindings: mmc: add DT binding for S3C24XX MMC/SD/SDIO controller Sergio Prado
2017-01-18 22:38 ` Rob Herring
2017-01-24 18:49 ` Sergio Prado [this message]
2017-01-13 15:05 ` [PATCH v3 2/2] mmc: host: s3cmci: allow probing from device tree Sergio Prado
2017-01-19 11:10 ` 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=20170124184932.GA20814@sprado-desktop \
--to=sergio.prado@e-labworks.com \
--cc=ben-linux@fluff.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--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).