devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: kishon@ti.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, subhashj@codeaurora.org,
	bjorn.andersson@linaro.org, devicetree@vger.kernel.org,
	jejb@linux.vnet.ibm.com, vinholikatti@gmail.com,
	Vivek Gautam <vivek.gautam@codeaurora.org>
Subject: [PATCH 2/5] phy: Add UFS PHY modes
Date: Fri,  4 Aug 2017 12:18:49 +0530	[thread overview]
Message-ID: <1501829332-5183-3-git-send-email-vivek.gautam@codeaurora.org> (raw)
In-Reply-To: <1501829332-5183-1-git-send-email-vivek.gautam@codeaurora.org>

UFS phy has two modes for each High speed generation.
These modes are identified by two rates of operations -
Rate A, and Rate B.
Add these UFS phy modes to phy framework.

Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
---
 include/linux/phy/phy.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
index 78bb0d7f6b11..27e25bb78bfb 100644
--- a/include/linux/phy/phy.h
+++ b/include/linux/phy/phy.h
@@ -27,6 +27,8 @@ enum phy_mode {
 	PHY_MODE_USB_HOST,
 	PHY_MODE_USB_DEVICE,
 	PHY_MODE_USB_OTG,
+	PHY_MODE_UFS_HS_A,
+	PHY_MODE_UFS_HS_B,
 };
 
 /**
-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation

  parent reply	other threads:[~2017-08-04  6:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  6:48 [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code Vivek Gautam
2017-08-04  6:48 ` [PATCH 1/5] dt-bindings: phy: Add PHY_TYPE_UFS definition Vivek Gautam
2017-08-04  6:48 ` Vivek Gautam [this message]
2017-08-04  6:48 ` [PATCH 3/5] phy: qcom-ufs: Add support to set phy mode Vivek Gautam
2017-08-04  6:48 ` [PATCH 4/5] scsi/ufs: qcom: Set phy mode based on the controllers HS MODE Vivek Gautam
     [not found]   ` <1501829332-5183-5-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-09-26 22:44     ` Subhash Jadavani
2017-09-27  6:31       ` Vivek Gautam
2017-08-04  6:48 ` [PATCH 5/5] ufs/phy: qcom: Refactor to use phy_init call Vivek Gautam
     [not found]   ` <1501829332-5183-6-git-send-email-vivek.gautam-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-09-26 23:13     ` Subhash Jadavani
2017-09-27  6:21       ` Vivek Gautam
2017-08-08 12:09 ` [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code Kishon Vijay Abraham I
2017-08-08 15:50   ` Vivek Gautam
2017-08-09  5:48     ` Kishon Vijay Abraham I
     [not found]       ` <d49316e0-8ccc-21b3-e952-ddb0a941f3b3-l0cyMroinI0@public.gmane.org>
2017-08-09  6:44         ` Vivek Gautam
2017-08-11  0:03           ` Martin K. Petersen
2017-08-11  7:12             ` Vivek Gautam
2017-08-14  5:17               ` Asutosh Das (asd)

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=1501829332-5183-3-git-send-email-vivek.gautam@codeaurora.org \
    --to=vivek.gautam@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=kishon@ti.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=robh+dt@kernel.org \
    --cc=subhashj@codeaurora.org \
    --cc=vinholikatti@gmail.com \
    /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).