devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wan Ahmad Zainie <wan.ahmad.zainie.wan.mohamad@intel.com>
To: kishon@ti.com, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	wan.ahmad.zainie.wan.mohamad@intel.com
Subject: [PATCH 1/2] dt-bindings: phy: intel: Add documentation for Keem Bay eMMC PHY
Date: Mon, 16 Mar 2020 18:37:25 +0800	[thread overview]
Message-ID: <20200316103726.16339-2-wan.ahmad.zainie.wan.mohamad@intel.com> (raw)
In-Reply-To: <20200316103726.16339-1-wan.ahmad.zainie.wan.mohamad@intel.com>

Document Intel Keem Bay eMMC PHY DT bindings.

Signed-off-by: Wan Ahmad Zainie <wan.ahmad.zainie.wan.mohamad@intel.com>
---
 .../bindings/phy/intel,keembay-emmc-phy.yaml  | 57 +++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/phy/intel,keembay-emmc-phy.yaml

diff --git a/Documentation/devicetree/bindings/phy/intel,keembay-emmc-phy.yaml b/Documentation/devicetree/bindings/phy/intel,keembay-emmc-phy.yaml
new file mode 100644
index 000000000000..af1d62fc8323
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/intel,keembay-emmc-phy.yaml
@@ -0,0 +1,57 @@
+# SPDX-License-Identifier: GPL-2.0-only
+# Copyright 2020 Intel Corporation
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/phy/intel,keembay-emmc-phy.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: Intel Keem Bay eMMC PHY
+
+maintainers:
+  - Wan Ahmad Zainie <wan.ahmad.zainie.wan.mohamad@intel.com>
+
+properties:
+  compatible:
+    enum:
+      - intel,keembay-emmc-phy
+
+  reg:
+    maxItems: 1
+
+  clocks:
+    maxItems: 1
+
+  clock-names:
+    items:
+      - const: emmcclk
+
+  intel,syscon:
+    $ref: '/schemas/types.yaml#/definitions/phandle'
+    description:
+      A phandle to a syscon device used to access core/phy configuration
+      registers.
+
+  "#phy-cells":
+    const: 0
+
+required:
+  - compatible
+  - reg
+  - intel,syscon
+  - "#phy-cells"
+
+examples:
+  - |
+    mmc_phy_syscon: syscon@20290000 {
+          compatible = "simple-mfd", "syscon";
+          reg = <0x0 0x20290000 0x0 0x54>;
+    };
+
+    emmc_phy: mmc_phy@20290000 {
+          compatible = "intel,keembay-emmc-phy";
+          reg = <0x0 0x20290000 0x0 0x54>;
+          clocks = <&mmc>;
+          clock-names = "emmcclk";
+          intel,syscon = <&mmc_phy_syscon>;
+          #phy-cells = <0>;
+    };
-- 
2.17.1


  reply	other threads:[~2020-03-16 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 10:37 [PATCH 0/2] phy: intel: Add Keem Bay eMMC PHY support Wan Ahmad Zainie
2020-03-16 10:37 ` Wan Ahmad Zainie [this message]
2020-03-20  5:58   ` [PATCH 1/2] dt-bindings: phy: intel: Add documentation for Keem Bay eMMC PHY Kishon Vijay Abraham I
2020-03-30 20:23   ` Rob Herring
2020-04-29  0:58     ` Wan Mohamad, Wan Ahmad Zainie
2020-03-16 10:37 ` [PATCH 2/2] phy: intel: Add Keem Bay eMMC PHY support Wan Ahmad Zainie

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=20200316103726.16339-2-wan.ahmad.zainie.wan.mohamad@intel.com \
    --to=wan.ahmad.zainie.wan.mohamad@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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).