From: Amit Singh Tomar <amittomer25@gmail.com>
To: andre.przywara@arm.com, afaerber@suse.de,
manivannan.sadhasivam@linaro.org, robh+dt@kernel.org
Cc: cristian.ciocaltea@gmail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-actions@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v3 08/10] dt-bindings: mmc: owl: add compatible string actions,s700-mmc
Date: Tue, 2 Jun 2020 23:03:10 +0530 [thread overview]
Message-ID: <1591119192-18538-9-git-send-email-amittomer25@gmail.com> (raw)
In-Reply-To: <1591119192-18538-1-git-send-email-amittomer25@gmail.com>
The commit adds a new SoC specific compatible string "actions,s700-mmc"
in combination with more generic string "actions,owl-mmc".
Placement order of these strings should abide by the principle of
"from most specific to most general".
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Amit Singh Tomar <amittomer25@gmail.com>
---
Changes since v2:
* Added Rob's Reviewed-by tag
* Newly added patch in v2.
---
Documentation/devicetree/bindings/mmc/owl-mmc.yaml | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mmc/owl-mmc.yaml b/Documentation/devicetree/bindings/mmc/owl-mmc.yaml
index 12b40213426d..9604ef695585 100644
--- a/Documentation/devicetree/bindings/mmc/owl-mmc.yaml
+++ b/Documentation/devicetree/bindings/mmc/owl-mmc.yaml
@@ -14,7 +14,11 @@ maintainers:
properties:
compatible:
- const: actions,owl-mmc
+ oneOf:
+ - const: actions,owl-mmc
+ - items:
+ - const: actions,s700-mmc
+ - const: actions,owl-mmc
reg:
maxItems: 1
--
2.7.4
next prev parent reply other threads:[~2020-06-02 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 17:33 [PATCH v3 00/10] Add MMC and DMA support for Actions S700 Amit Singh Tomar
2020-06-02 17:33 ` [PATCH v3 01/10] dmaengine: Actions: get rid of bit fields from dma descriptor Amit Singh Tomar
2020-06-03 7:22 ` Manivannan Sadhasivam
2020-06-03 17:28 ` Amit Tomer
2020-06-02 17:33 ` [PATCH v3 02/10] dmaengine: Actions: Add support for S700 DMA engine Amit Singh Tomar
2020-06-06 3:17 ` kernel test robot
2020-06-02 17:33 ` [PATCH v3 03/10] clk: actions: Add MMC clock-register reset bits Amit Singh Tomar
2020-06-02 17:33 ` [PATCH v3 04/10] arm64: dts: actions: limit address range for pinctrl node Amit Singh Tomar
2020-06-02 17:33 ` [PATCH v3 05/10] dt-bindings: dmaengine: convert Actions Semi Owl SoCs bindings to yaml Amit Singh Tomar
2020-06-02 17:33 ` [PATCH v3 06/10] arm64: dts: actions: Add DMA Controller for S700 Amit Singh Tomar
2020-06-03 8:30 ` Manivannan Sadhasivam
2020-06-02 17:33 ` [PATCH v3 07/10] dt-bindings: reset: s700: Add binding constants for mmc Amit Singh Tomar
2020-06-02 17:33 ` Amit Singh Tomar [this message]
2020-06-02 17:33 ` [PATCH v3 09/10] arm64: dts: actions: Add MMC controller support for S700 Amit Singh Tomar
2020-06-02 17:33 ` [PATCH v3 10/10] arm64: dts: actions: Add uSD support for Cubieboard7 Amit Singh Tomar
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=1591119192-18538-9-git-send-email-amittomer25@gmail.com \
--to=amittomer25@gmail.com \
--cc=afaerber@suse.de \
--cc=andre.przywara@arm.com \
--cc=cristian.ciocaltea@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.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).