All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kotas <jank@cadence.com>
To: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<alim.akhtar@samsung.com>, <avri.altman@wdc.com>,
	<pedrom.sousa@synopsys.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-scsi@vger.kernel.org>, Jan Kotas <jank@cadence.com>
Subject: [PATCH 1/2] dt-bindings: scsi: ufs-cdns: Update Cadence UFS compatibility list
Date: Wed, 27 Mar 2019 14:44:04 +0000	[thread overview]
Message-ID: <20190327144405.5716-2-jank@cadence.com> (raw)
In-Reply-To: <20190327144405.5716-1-jank@cadence.com>

This patch adds a new compatible string description for
CDNS UFS HCD + M31 16nm PHY.

Signed-off-by: Jan Kotas <jank@cadence.com>
---
 Documentation/devicetree/bindings/ufs/cdns,ufshc.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt b/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt
index a04a4989e..02347b017 100644
--- a/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt
+++ b/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt
@@ -5,8 +5,9 @@ Each UFS controller instance should have its own node.
 Please see the ufshcd-pltfrm.txt for a list of all available properties.
 
 Required properties:
-- compatible	: Compatible list, contains the following controller:
-			"cdns,ufshc"
+- compatible	: Compatible list, contains one of the following controllers:
+			"cdns,ufshc" - Generic CDNS HCI,
+			"cdns,ufshc-m31-16nm" - CDNS UFS HC + M31 16nm PHY
 		  complemented with the JEDEC version:
 			"jedec,ufs-2.0"
 
-- 
2.15.0


WARNING: multiple messages have this Message-ID (diff)
From: Jan Kotas <jank@cadence.com>
To: robh+dt@kernel.org, mark.rutland@arm.com,
	alim.akhtar@samsung.com, avri.altman@wdc.com,
	pedrom.sousa@synopsys.com, jejb@linux.ibm.com,
	martin.petersen@oracle.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, Jan Kotas <jank@cadence.com>
Subject: [PATCH 1/2] dt-bindings: scsi: ufs-cdns: Update Cadence UFS compatibility list
Date: Wed, 27 Mar 2019 14:44:04 +0000	[thread overview]
Message-ID: <20190327144405.5716-2-jank@cadence.com> (raw)
In-Reply-To: <20190327144405.5716-1-jank@cadence.com>

This patch adds a new compatible string description for
CDNS UFS HCD + M31 16nm PHY.

Signed-off-by: Jan Kotas <jank@cadence.com>
---
 Documentation/devicetree/bindings/ufs/cdns,ufshc.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt b/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt
index a04a4989e..02347b017 100644
--- a/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt
+++ b/Documentation/devicetree/bindings/ufs/cdns,ufshc.txt
@@ -5,8 +5,9 @@ Each UFS controller instance should have its own node.
 Please see the ufshcd-pltfrm.txt for a list of all available properties.
 
 Required properties:
-- compatible	: Compatible list, contains the following controller:
-			"cdns,ufshc"
+- compatible	: Compatible list, contains one of the following controllers:
+			"cdns,ufshc" - Generic CDNS HCI,
+			"cdns,ufshc-m31-16nm" - CDNS UFS HC + M31 16nm PHY
 		  complemented with the JEDEC version:
 			"jedec,ufs-2.0"
 
-- 
2.15.0

  reply	other threads:[~2019-03-27 14:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27 14:44 [PATCH 0/2] scsi: ufs-cdns: Add M31 PHY init Jan Kotas
2019-03-27 14:44 ` Jan Kotas
2019-03-27 14:44 ` Jan Kotas [this message]
2019-03-27 14:44   ` [PATCH 1/2] dt-bindings: scsi: ufs-cdns: Update Cadence UFS compatibility list Jan Kotas
2019-03-31  6:42   ` Rob Herring
2019-04-01  7:49     ` Jan Kotas
2019-04-03  4:15   ` Rob Herring
2019-03-27 14:44 ` [PATCH 2/2] scsi: ufs-cdns: Add support for UFSHCI with M31 PHY Jan Kotas
2019-03-27 14:44   ` Jan Kotas
2019-04-04  3:24   ` Martin K. Petersen
2019-04-04  3:24     ` Martin K. Petersen

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=20190327144405.5716-2-jank@cadence.com \
    --to=jank@cadence.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin.petersen@oracle.com \
    --cc=pedrom.sousa@synopsys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.