linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alim Akhtar <alim.akhtar@samsung.com>
To: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: JBottomley@odin.com, vinholikatti@gmail.com,
	amit.daniel@samsung.com, essuuj@gmail.com,
	devicetree@vger.kernel.org
Subject: [PATCH v2 11/11] scsi: ufs: Add exynos ufs platform data
Date: Thu, 17 Sep 2015 15:15:37 +0530	[thread overview]
Message-ID: <1442483137-32376-12-git-send-email-alim.akhtar@samsung.com> (raw)
In-Reply-To: <1442483137-32376-1-git-send-email-alim.akhtar@samsung.com>

This adds ufs_hba_exynos_ops{} to platform data, so that
exynos ufs driver can be probed.

Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
---
 drivers/scsi/ufs/ufshcd-pltfrm.c |    2 ++
 drivers/scsi/ufs/ufshcd.h        |    1 +
 2 files changed, 3 insertions(+)

diff --git a/drivers/scsi/ufs/ufshcd-pltfrm.c b/drivers/scsi/ufs/ufshcd-pltfrm.c
index 7db9564..39dae76 100644
--- a/drivers/scsi/ufs/ufshcd-pltfrm.c
+++ b/drivers/scsi/ufs/ufshcd-pltfrm.c
@@ -373,6 +373,8 @@ static int ufshcd_pltfrm_remove(struct platform_device *pdev)
 
 static const struct of_device_id ufs_of_match[] = {
 	{ .compatible = "jedec,ufs-1.1"},
+	{ .compatible = "samsung,exynos7-ufs",
+	 .data	= &ufs_hba_exynos_ops},
 	{},
 };
 
diff --git a/drivers/scsi/ufs/ufshcd.h b/drivers/scsi/ufs/ufshcd.h
index 83fe605..15f2a7c 100644
--- a/drivers/scsi/ufs/ufshcd.h
+++ b/drivers/scsi/ufs/ufshcd.h
@@ -687,4 +687,5 @@ static inline int ufshcd_dme_peer_get(struct ufs_hba *hba,
 
 int ufshcd_hold(struct ufs_hba *hba, bool async);
 void ufshcd_release(struct ufs_hba *hba);
+extern const struct ufs_hba_variant_ops ufs_hba_exynos_ops;
 #endif /* End of Header */
-- 
1.7.10.4


      parent reply	other threads:[~2015-09-17  9:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  9:45 [PATCH v2 00/11] exynos-ufs: add support for Exynos Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 01/11] phy: exynos-ufs: add UFS PHY driver for EXYNOS SoC Alim Akhtar
2015-09-21 14:33   ` Rob Herring
2015-10-01  4:32     ` Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 02/11] scsi: ufs: add quirk to contain unconformable utrd field Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 03/11] scsi: ufs: add quirk to fix mishandling utrlclr/utmrlclr Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 04/11] scsi: ufs: add quirk not to allow reset of interrupt aggregation Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 05/11] scsi: ufs: add quirk to enable host controller without hce Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 06/11] scsi: ufs: add specific callback for nexus type Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 07/11] scsi: ufs: add add specific callback for hibern8 Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 08/11] scsi: ufs: make ufshcd_config_pwr_mode of non-static func Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 09/11] scsi: ufs: return value of pwr_change_notify Alim Akhtar
2015-09-17  9:45 ` [PATCH v2 10/11] scsi: ufs-exynos: add UFS host support for Exynos SoCs Alim Akhtar
2015-09-17  9:45 ` Alim Akhtar [this message]

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=1442483137-32376-12-git-send-email-alim.akhtar@samsung.com \
    --to=alim.akhtar@samsung.com \
    --cc=JBottomley@odin.com \
    --cc=amit.daniel@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=essuuj@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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).