From: Jaedon Shin <jaedon.shin@gmail.com>
To: Al Cooper <alcooperx@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
linux-mmc@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Jaedon Shin <jaedon.shin@gmail.com>
Subject: [v3 1/2] mmc: DT: sdhci-brcmstb: Bindings document for common sdhci-brcmstb
Date: Tue, 30 Aug 2016 15:30:09 +0900 [thread overview]
Message-ID: <20160830063010.10171-2-jaedon.shin@gmail.com> (raw)
In-Reply-To: <20160830063010.10171-1-jaedon.shin@gmail.com>
- Renames the DT binding document to common for ARM and MIPS based SoCs
- Adds a compatible string "brcm,bcm7445-sdhci" that is representation
for the Broadcom BCM7445 and family. It is initial and typical 28nm
generation ARM based SoC.
Signed-off-by: Jaedon Shin <jaedon.shin@gmail.com>
---
.../mmc/{brcm,bcm7425-sdhci.txt => brcm,sdhci-brcmstb.txt} | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
rename Documentation/devicetree/bindings/mmc/{brcm,bcm7425-sdhci.txt => brcm,sdhci-brcmstb.txt} (81%)
diff --git a/Documentation/devicetree/bindings/mmc/brcm,bcm7425-sdhci.txt b/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.txt
similarity index 81%
rename from Documentation/devicetree/bindings/mmc/brcm,bcm7425-sdhci.txt
rename to Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.txt
index 82847174c37d..555229367935 100644
--- a/Documentation/devicetree/bindings/mmc/brcm,bcm7425-sdhci.txt
+++ b/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.txt
@@ -8,14 +8,16 @@ on Device Tree properties to enable them for SoC/Board combinations
that support them.
Required properties:
-- compatible: "brcm,bcm7425-sdhci"
+- compatible: should be one of the following
+ - "brcm,bcm7425-sdhci"
+ - "brcm,bcm7445-sdhci"
Refer to clocks/clock-bindings.txt for generic clock consumer properties.
Example:
sdhci@f03e0100 {
- compatible = "brcm,bcm7425-sdhci";
+ compatible = "brcm,bcm7445-sdhci";
reg = <0xf03e0000 0x100>;
interrupts = <0x0 0x26 0x0>;
sdhci,auto-cmd12;
@@ -27,7 +29,7 @@ Example:
sdhci@f03e0300 {
non-removable;
bus-width = <0x8>;
- compatible = "brcm,bcm7425-sdhci";
+ compatible = "brcm,bcm7445-sdhci";
reg = <0xf03e0200 0x100>;
interrupts = <0x0 0x27 0x0>;
sdhci,auto-cmd12;
--
2.9.3
next prev parent reply other threads:[~2016-08-30 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 6:30 [v3 0/2] Fix incorrect capability Jaedon Shin
2016-08-30 6:30 ` Jaedon Shin [this message]
[not found] ` <20160830063010.10171-2-jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-02 14:55 ` [v3 1/2] mmc: DT: sdhci-brcmstb: Bindings document for common sdhci-brcmstb Rob Herring
2016-09-03 10:48 ` Jaedon Shin
[not found] ` <20160830063010.10171-1-jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-30 6:30 ` [v3 2/2] mmc: sdhci-brcmstb: Fix incorrect capability Jaedon Shin
[not found] ` <20160830063010.10171-3-jaedon.shin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-08 7:57 ` Adrian Hunter
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=20160830063010.10171-2-jaedon.shin@gmail.com \
--to=jaedon.shin@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=alcooperx@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@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).