Skip to contentSkip to conversation

Introduce a vops for resetting host controller

PATCH In review Can Guo 4 participants 11 messages Oct 23, 2019 – Nov 4, 2019

Subsystems (2)
lore
Share & tools
lore

Can Guo

author
#0 lore raw

cover Introduce a vops for resetting host controller

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

Can Guo (2):
scsi: ufs: Introduce a vops for resetting host controller
scsi: ufs-qcom: Add reset control support for host controller

 drivers/scsi/ufs/ufs-qcom.c | 43 +++++++++++++++++++++++++++++++++++++++++++
 drivers/scsi/ufs/ufs-qcom.h |  3 +++
 drivers/scsi/ufs/ufshcd.c   | 16 ++++++++++++++++
 drivers/scsi/ufs/ufshcd.h   | 10 ++++++++++
 4 files changed, 72 insertions(+)
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
author
#1 lore raw

PATCH 1/2 scsi: ufs: Introduce a vops for resetting host controller

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

---
 drivers/scsi/ufs/ufshcd.c | 16 ++++++++++++++++
 drivers/scsi/ufs/ufshcd.h | 10 ++++++++++
 2 files changed, 26 insertions(+)
drivers/scsi/ufs/ufshcd.c +16 -0
index c28c144..161e3c4 100644
@@ -3859,6 +3859,14 @@ static int ufshcd_link_recovery(struct ufs_hba *hba)
 	ufshcd_set_eh_in_progress(hba);
 	spin_unlock_irqrestore(hba->host->host_lock, flags);
 
+	ret = ufshcd_vops_full_reset(hba);
+	if (ret)
+		dev_warn(hba->dev, "%s: full reset returned %d\n",
+				  __func__, ret);
+
+	/* Reset the attached device */
+	ufshcd_vops_device_reset(hba);
+
 	ret = ufshcd_host_reset_and_restore(hba);
 
 	spin_lock_irqsave(hba->host->host_lock, flags);
@@ -6241,6 +6249,11 @@ static int ufshcd_reset_and_restore(struct ufs_hba *hba)
 	int retries = MAX_HOST_RESET_RETRIES;
 
 	do {
+		err = ufshcd_vops_full_reset(hba);
+		if (err)
+			dev_warn(hba->dev, "%s: full reset returned %d\n",
+					__func__, err);
+
 		/* Reset the attached device */
 		ufshcd_vops_device_reset(hba);
 
@@ -8384,6 +8397,9 @@ int ufshcd_init(struct ufs_hba *hba, void __iomem *mmio_base, unsigned int irq)
 		goto exit_gating;
 	}
 
+	/* Reset controller to power on reset (POR) state */
+	ufshcd_vops_full_reset(hba);
+
 	/* Reset the attached device */
 	ufshcd_vops_device_reset(hba);
 
drivers/scsi/ufs/ufshcd.h +10 -0
index e0fe247..253b9ea 100644
@@ -296,6 +296,8 @@ struct ufs_pwr_mode_info {
  * @apply_dev_quirks: called to apply device specific quirks
  * @suspend: called during host controller PM callback
  * @resume: called during host controller PM callback
+ * @full_reset: called for handling variant specific implementations of
+ *              resetting the hci
  * @dbg_register_dump: used to dump controller debug information
  * @phy_initialization: used to initialize phys
  * @device_reset: called to issue a reset pulse on the UFS device
@@ -325,6 +327,7 @@ struct ufs_hba_variant_ops {
 	int	(*apply_dev_quirks)(struct ufs_hba *);
 	int     (*suspend)(struct ufs_hba *, enum ufs_pm_op);
 	int     (*resume)(struct ufs_hba *, enum ufs_pm_op);
+	int	(*full_reset)(struct ufs_hba *hba);
 	void	(*dbg_register_dump)(struct ufs_hba *hba);
 	int	(*phy_initialization)(struct ufs_hba *);
 	void	(*device_reset)(struct ufs_hba *hba);
@@ -1076,6 +1079,13 @@ static inline int ufshcd_vops_resume(struct ufs_hba *hba, enum ufs_pm_op op)
 	return 0;
 }
 
+static inline int ufshcd_vops_full_reset(struct ufs_hba *hba)
+{
+	if (hba->vops && hba->vops->full_reset)
+		return hba->vops->full_reset(hba);
+	return 0;
+}
+
 static inline void ufshcd_vops_dbg_register_dump(struct ufs_hba *hba)
 {
 	if (hba->vops && hba->vops->dbg_register_dump)
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
author
#10 lore raw

PATCH 2/2 scsi: ufs-qcom: Add reset control support for host controller

In reply to Can Guo

Add reset control for host controller and provide it through vops to UFS core driver.

---
 drivers/scsi/ufs/ufs-qcom.c | 43 +++++++++++++++++++++++++++++++++++++++++++
 drivers/scsi/ufs/ufs-qcom.h |  3 +++
 2 files changed, 46 insertions(+)
drivers/scsi/ufs/ufs-qcom.c +43 -0
index a5b7148..3dee906 100644
@@ -576,6 +576,39 @@ static int ufs_qcom_resume(struct ufs_hba *hba, enum ufs_pm_op pm_op)
 	return 0;
 }
 
+static int ufs_qcom_full_reset(struct ufs_hba *hba)
+{
+	int ret = -ENOTSUPP;
+	struct ufs_qcom_host *host = ufshcd_get_variant(hba);
+
+	if (!host->core_reset) {
+		dev_warn(hba->dev, "%s: failed, err = %d\n", __func__, ret);
+		goto out;
+	}
+
+	ret = reset_control_assert(host->core_reset);
+	if (ret) {
+		dev_err(hba->dev, "%s: core_reset assert failed, err = %d\n",
+				 __func__, ret);
+		goto out;
+	}
+
+	/*
+	 * The hardware requirement for delay between assert/deassert
+	 * is at least 3-4 sleep clock (32.7KHz) cycles, which comes to
+	 * ~125us (4/32768). To be on the safe side add 200us delay.
+	 */
+	usleep_range(200, 210);
+
+	ret = reset_control_deassert(host->core_reset);
+	if (ret)
+		dev_err(hba->dev, "%s: core_reset deassert failed, err = %d\n",
+				 __func__, ret);
+
+out:
+	return ret;
+}
+
 #ifdef CONFIG_MSM_BUS_SCALING
 static int ufs_qcom_get_bus_vote(struct ufs_qcom_host *host,
 		const char *speed_mode)
@@ -1101,6 +1134,15 @@ static int ufs_qcom_init(struct ufs_hba *hba)
 	host->hba = hba;
 	ufshcd_set_variant(hba, host);
 
+	/* Setup the reset control of HCI */
+	host->core_reset = devm_reset_control_get(hba->dev, "rst");
+	if (IS_ERR(host->core_reset)) {
+		err = PTR_ERR(host->core_reset);
+		dev_warn(dev, "Failed to get reset control %d\n", err);
+		host->core_reset = NULL;
+		err = 0;
+	}
+
 	/* Fire up the reset controller. Failure here is non-fatal. */
 	host->rcdev.of_node = dev->of_node;
 	host->rcdev.ops = &ufs_qcom_reset_ops;
@@ -1596,6 +1638,7 @@ static void ufs_qcom_device_reset(struct ufs_hba *hba)
 	.apply_dev_quirks	= ufs_qcom_apply_dev_quirks,
 	.suspend		= ufs_qcom_suspend,
 	.resume			= ufs_qcom_resume,
+	.full_reset		= ufs_qcom_full_reset,
 	.dbg_register_dump	= ufs_qcom_dump_dbg_regs,
 	.device_reset		= ufs_qcom_device_reset,
 };
drivers/scsi/ufs/ufs-qcom.h +3 -0
index d401f17..2d95e7c 100644
@@ -6,6 +6,7 @@
 #define UFS_QCOM_H_
 
 #include <linux/reset-controller.h>
+#include <linux/reset.h>
 
 #define MAX_UFS_QCOM_HOSTS	1
 #define MAX_U32                 (~(u32)0)
@@ -233,6 +234,8 @@ struct ufs_qcom_host {
 	u32 dbg_print_en;
 	struct ufs_qcom_testbus testbus;
 
+	/* Reset control of HCI */
+	struct reset_control *core_reset;
 	struct reset_controller_dev rcdev;
 
 	struct gpio_desc *device_reset;
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
#2 lore raw

RE: [EXT] [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

In reply to Can Guo

Hi, Can Guo
Actually, we already have DME_RESET, this is not enough for Qualcomm host? Thanks,

//Bean

Quoted 90 lines

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

---
 drivers/scsi/ufs/ufshcd.c | 16 ++++++++++++++++  drivers/scsi/ufs/ufshcd.h | 10
++++++++++
 2 files changed, 26 insertions(+)
drivers/scsi/ufs/ufshcd.c index renamed from drivers/scsi/ufs/ufshcd.c +0 -0

c28c144..161e3c4 100644

drivers/scsi/ufs/ufshcd.c +8 -0
@@ -3859,6 +3859,14 @@ static int ufshcd_link_recovery(struct ufs_hba *hba)
 	ufshcd_set_eh_in_progress(hba);
 	spin_unlock_irqrestore(hba->host->host_lock, flags);
 
+	ret = ufshcd_vops_full_reset(hba);
+	if (ret)
+		dev_warn(hba->dev, "%s: full reset returned %d\n",
+				  __func__, ret);
+
+	/* Reset the attached device */
+	ufshcd_vops_device_reset(hba);
+
 	ret = ufshcd_host_reset_and_restore(hba);
 
 	spin_lock_irqsave(hba->host->host_lock, flags); @@ -6241,6 +6249,11

@@ static int ufshcd_reset_and_restore(struct ufs_hba *hba)

drivers/scsi/ufs/ufshcd.c +8 -0
 	int retries = MAX_HOST_RESET_RETRIES;
 
 	do {
+		err = ufshcd_vops_full_reset(hba);
+		if (err)
+			dev_warn(hba->dev, "%s: full reset returned %d\n",
+					__func__, err);
+
 		/* Reset the attached device */
 		ufshcd_vops_device_reset(hba);
@@ -8384,6 +8397,9 @@ int ufshcd_init(struct ufs_hba *hba, void __iomem
 *mmio_base, unsigned int irq)
 		goto exit_gating;
 	}
 
+	/* Reset controller to power on reset (POR) state */
+	ufshcd_vops_full_reset(hba);
+
 	/* Reset the attached device */
 	ufshcd_vops_device_reset(hba);
drivers/scsi/ufs/ufshcd.h index renamed from drivers/scsi/ufs/ufshcd.h +0 -0

e0fe247..253b9ea 100644

drivers/scsi/ufs/ufshcd.h +10 -1
@@ -296,6 +296,8 @@ struct ufs_pwr_mode_info {
  * @apply_dev_quirks: called to apply device specific quirks
  * @suspend: called during host controller PM callback
  * @resume: called during host controller PM callback
+ * @full_reset: called for handling variant specific implementations of
+ *              resetting the hci
  * @dbg_register_dump: used to dump controller debug information
  * @phy_initialization: used to initialize phys
  * @device_reset: called to issue a reset pulse on the UFS device @@ -325,6
+327,7 @@ struct ufs_hba_variant_ops {
 	int	(*apply_dev_quirks)(struct ufs_hba *);
 	int     (*suspend)(struct ufs_hba *, enum ufs_pm_op);
 	int     (*resume)(struct ufs_hba *, enum ufs_pm_op);
+	int	(*full_reset)(struct ufs_hba *hba);
 	void	(*dbg_register_dump)(struct ufs_hba *hba);
 	int	(*phy_initialization)(struct ufs_hba *);
 	void	(*device_reset)(struct ufs_hba *hba);
@@ -1076,6 +1079,13 @@ static inline int ufshcd_vops_resume(struct ufs_hba
 *hba, enum ufs_pm_op op)
 	return 0;
 }
 
+static inline int ufshcd_vops_full_reset(struct ufs_hba *hba) {
+	if (hba->vops && hba->vops->full_reset)
+		return hba->vops->full_reset(hba);
+	return 0;
+}
+
 static inline void ufshcd_vops_dbg_register_dump(struct ufs_hba *hba)  {
 	if (hba->vops && hba->vops->dbg_register_dump)
--

The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

#3 lore raw

Re: [EXT] [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

Quoted 6 lines · Bean Huo (beanhuo)

Hi, Can Guo
Actually, we already have DME_RESET, this is not enough for Qualcomm host? Thanks,

//Bean

Hi Bean,

Yes, for Qualcomm hosts, we need this to fully reset the whole UFS controller block

Can Guo

Quoted 97 lines
Quoted 97 lines

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

---
 drivers/scsi/ufs/ufshcd.c | 16 ++++++++++++++++  
drivers/scsi/ufs/ufshcd.h | 10
++++++++++
 2 files changed, 26 insertions(+)
drivers/scsi/ufs/ufshcd.c index renamed from drivers/scsi/ufs/ufshcd.c +0 -0

c28c144..161e3c4 100644

drivers/scsi/ufs/ufshcd.c +8 -0
@@ -3859,6 +3859,14 @@ static int ufshcd_link_recovery(struct ufs_hba 
 *hba)
 	ufshcd_set_eh_in_progress(hba);
 	spin_unlock_irqrestore(hba->host->host_lock, flags);
 
+	ret = ufshcd_vops_full_reset(hba);
+	if (ret)
+		dev_warn(hba->dev, "%s: full reset returned %d\n",
+				  __func__, ret);
+
+	/* Reset the attached device */
+	ufshcd_vops_device_reset(hba);
+
 	ret = ufshcd_host_reset_and_restore(hba);
 

spin_lock_irqsave(hba->host->host_lock, flags); @@ -6241,6 +6249,11
@@ static int ufshcd_reset_and_restore(struct ufs_hba *hba)

drivers/scsi/ufs/ufshcd.c +5 -0
 	int retries = MAX_HOST_RESET_RETRIES;
 
 	do {
+		err = ufshcd_vops_full_reset(hba);
+		if (err)
+			dev_warn(hba->dev, "%s: full reset returned %d\n",
+					__func__, err);
+
 		/* Reset the attached device */
 		ufshcd_vops_device_reset(hba);
@@ -8384,6 +8397,9 @@ int ufshcd_init(struct ufs_hba *hba, void 

__iomem
*mmio_base, unsigned int irq)

drivers/scsi/ufs/ufshcd.c +3 -0
 		goto exit_gating;
 	}
 
+	/* Reset controller to power on reset (POR) state */
+	ufshcd_vops_full_reset(hba);
+
 	/* Reset the attached device */
 	ufshcd_vops_device_reset(hba);
drivers/scsi/ufs/ufshcd.h index renamed from drivers/scsi/ufs/ufshcd.h +0 -0

e0fe247..253b9ea 100644

drivers/scsi/ufs/ufshcd.h +1 -0
@@ -296,6 +296,8 @@ struct ufs_pwr_mode_info {
  * @apply_dev_quirks: called to apply device specific quirks
  * @suspend: called during host controller PM callback
  * @resume: called during host controller PM callback
+ * @full_reset: called for handling variant specific implementations 

of
+ * resetting the hci
* @dbg_register_dump: used to dump controller debug information
* @phy_initialization: used to initialize phys
* @device_reset: called to issue a reset pulse on the UFS device @@
-325,6
+327,7 @@ struct ufs_hba_variant_ops {

drivers/scsi/ufs/ufshcd.h +1 -0
 	int	(*apply_dev_quirks)(struct ufs_hba *);
 	int     (*suspend)(struct ufs_hba *, enum ufs_pm_op);
 	int     (*resume)(struct ufs_hba *, enum ufs_pm_op);
+	int	(*full_reset)(struct ufs_hba *hba);
 	void	(*dbg_register_dump)(struct ufs_hba *hba);
 	int	(*phy_initialization)(struct ufs_hba *);
 	void	(*device_reset)(struct ufs_hba *hba);
@@ -1076,6 +1079,13 @@ static inline int ufshcd_vops_resume(struct 

ufs_hba
*hba, enum ufs_pm_op op)

drivers/scsi/ufs/ufshcd.h +6 -1
 	return 0;
 }
 
+static inline int ufshcd_vops_full_reset(struct ufs_hba *hba) {
+	if (hba->vops && hba->vops->full_reset)
+		return hba->vops->full_reset(hba);
+	return 0;
+}
+
 static inline void ufshcd_vops_dbg_register_dump(struct ufs_hba *hba) 
 {
 	if (hba->vops && hba->vops->dbg_register_dump)
--

The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project

#4 lore raw

Re: [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

In reply to Can Guo
Quoted 19 lines · Can Guo

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

---
  drivers/scsi/ufs/ufshcd.c | 16 ++++++++++++++++
  drivers/scsi/ufs/ufshcd.h | 10 ++++++++++
  2 files changed, 26 insertions(+)
drivers/scsi/ufs/ufshcd.c +1 -0
index c28c144..161e3c4 100644
@@ -3859,6 +3859,14 @@ static int ufshcd_link_recovery(struct ufs_hba *hba)
  	ufshcd_set_eh_in_progress(hba);
  	spin_unlock_irqrestore(hba->host->host_lock, flags);
 
+	ret = ufshcd_vops_full_reset(hba);

drivers/scsi/ufs/ufshcd.c static int ufshcd_link_recovery(struct ufs_hba *hba) · line 3872

Quoted 10 lines
drivers/scsi/ufs/ufshcd.c +7 -0
+	if (ret)
+		dev_warn(hba->dev, "%s: full reset returned %d\n",
+				  __func__, ret);
+
+	/* Reset the attached device */
+	ufshcd_vops_device_reset(hba);
+
  	ret = ufshcd_host_reset_and_restore(hba);
 
  	spin_lock_irqsave(hba->host->host_lock, flags);

In all your cases, especially after this adjustment, ufshcd_vops_full_reset is called blindly (+error checking message) before ufshcd_vops_device_reset. What about dropping the .full_reset (should really have been called .hw_reset or .host_reset) addition to the vops, just adding ufshcd_vops_device_reset call here before ufshcd_host_reset_and_restore, and in the driver folding the ufshcd_vops_full_reset code into the .device_reset handler?

Would that be workable? It would be simpler if so.

I can see a desire for the heads up (ufshcd_vops_full_reset+)ufshcd_vops_device_reset calls before ufshcd_host_reset_and_restore because that function will spin 10 seconds waiting for a response from a standardized register, that itself could be hardware locked up requiring product specific reset procedures. But if that is the case, then what about all the other calls to ufshcd_host_reset_and_restore in this file that are not provided the heads up? My guess is that the host device only demonstrated issues in the ufshcd_link_recovery handling path? Are you sure this is the only path that tickles the controller into a hardware lockup state?

Sincerely -- Mark Salyzyn

#5 lore raw

Re: [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

Quoted 52 lines · Mark Salyzyn
Quoted 18 lines · Can Guo

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

---
  drivers/scsi/ufs/ufshcd.c | 16 ++++++++++++++++
  drivers/scsi/ufs/ufshcd.h | 10 ++++++++++
  2 files changed, 26 insertions(+)
drivers/scsi/ufs/ufshcd.c +0 -0
index c28c144..161e3c4 100644
@@ -3859,6 +3859,14 @@ static int ufshcd_link_recovery(struct ufs_hba 
 *hba)
  	ufshcd_set_eh_in_progress(hba);
  	spin_unlock_irqrestore(hba->host->host_lock, flags);

drivers/scsi/ufs/ufshcd.c static int ufshcd_link_recovery(struct ufs_hba · line 3871

Quoted 10 lines
drivers/scsi/ufs/ufshcd.c +7 -0
  +	ret = ufshcd_vops_full_reset(hba);
+	if (ret)
+		dev_warn(hba->dev, "%s: full reset returned %d\n",
+				  __func__, ret);
+
+	/* Reset the attached device */
+	ufshcd_vops_device_reset(hba);
+
  	ret = ufshcd_host_reset_and_restore(hba);
    	spin_lock_irqsave(hba->host->host_lock, flags);

In all your cases, especially after this adjustment, ufshcd_vops_full_reset is called blindly (+error checking message) before ufshcd_vops_device_reset. What about dropping the .full_reset (should really have been called .hw_reset or .host_reset) addition to the vops, just adding ufshcd_vops_device_reset call here before ufshcd_host_reset_and_restore, and in the driver folding the ufshcd_vops_full_reset code into the .device_reset handler?

Would that be workable? It would be simpler if so.

I can see a desire for the heads up (ufshcd_vops_full_reset+)ufshcd_vops_device_reset calls before ufshcd_host_reset_and_restore because that function will spin 10 seconds waiting for a response from a standardized register, that itself could be hardware locked up requiring product specific reset procedures. But if that is the case, then what about all the other calls to ufshcd_host_reset_and_restore in this file that are not provided the heads up? My guess is that the host device only demonstrated issues in the ufshcd_link_recovery handling path? Are you sure this is the only path that tickles the controller into a hardware lockup state?

Quoted 1 line

Sincerely -- Mark Salyzyn

Hi Mark Salyzyn,

Folding the "full_reset" vops inito "device_reset" vops is one choice for now. Shall do that. Your guess is correct. the head up is needed in ufshcd_link_recovery() path because link is already in bad state when we are here, expeically after hibern8 exit fails. So we need a full reset to PHY and host controller here before host_reset_and_restore. But other calls to host_reset_and_restore are under good conditions.

Regards,
Can Guo.

#6 lore raw

RE: [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

In reply to Can Guo

Hi,

Quoted 6 lines

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

Did you withdraw from this patches and insert them to one of your fix bundle?
I couldn't tell.
As this is a vop, in what way its functionality can't be included in the device reset that was recently added?

Thanks,
Avri

#7 lore raw

RE: [EXT] RE: [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

Hi, Can

I agree with Avri, you can add this series patches to your bundle, and that is also easy to review for us. Otherwise, we are confused by somehow crossing different series patches.
Thanks,

//Bean

Quoted 15 lines

Hi,

Quoted 6 lines

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

Did you withdraw from this patches and insert them to one of your fix bundle? I couldn't tell.
As this is a vop, in what way its functionality can't be included in the device reset that was recently added?

Thanks,
Avri

#9 lore raw

Re: [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

In reply to Avri Altman
Quoted 6 lines · Avri Altman

Hi,

Quoted 5 lines

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

Quoted 8 lines
Quoted 1 line

Did you withdraw from this patches and insert them to one of your fix bundle? I couldn't tell.
As this is a vop, in what way its functionality can't be included in the device reset that was recently added?

Thanks,
Avri

Hi Avri,

Sorry for making you confused.
Yes, I dropped this series because it cannot fulfil its purpose anymore. I come up with a way which puts the reset in the right place in UFS QCOM platfrom driver without an extra vops, so I inserted the two changes in fix bundle 3.

Thanks,
Can Guo.

#8 lore raw

Re: [EXT] RE: [PATCH v1 1/2] scsi: ufs: Introduce a vops for resetting host controller

In reply to Bean Huo (beanhuo)
Quoted 8 lines · Bean Huo (beanhuo)

Hi, Can

I agree with Avri, you can add this series patches to your bundle, and that is also easy to review for us.
Otherwise, we are confused by somehow crossing different series patches. Thanks,

//Bean

Hi Bean,

I moved the two changes to fix bundle 3. The vops is not needed anymore. Meanwhile I find it inappropriate to put the host controller reset inside the device reset vops. So you can check the new changes in fix bundle 3.

Regards,
Can Guo.

Quoted 15 lines
Quoted 15 lines

Hi,

Quoted 6 lines

Some UFS host controllers need their specific implementations of resetting to get them into a good state. Provide a new vops to allow the platform driver to implement this own reset operation.

Did you withdraw from this patches and insert them to one of your fix bundle? I couldn't tell.
As this is a vop, in what way its functionality can't be included in the device reset that was recently added?

Thanks,
Avri