All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Asutosh Das (asd)" <asutoshd@codeaurora.org>
To: asutoshd@qti.qualcomm.com, linux-scsi@vger.kernel.org
Subject: Re: [<RFC PATCH v2> 2/3] ufs-qcom: scsi: configure write booster type
Date: Fri, 20 Mar 2020 17:52:04 -0700	[thread overview]
Message-ID: <13af63cc-c0f2-72c0-14aa-18ff8fd3751f@codeaurora.org> (raw)
In-Reply-To: <116b8c6bed27ffbee9da6ccfd52a2fdc612648b4.1584750888.git.asutoshd@codeaurora.org>

On 3/20/2020 5:48 PM, Asutosh Das wrote:
> Configure the WriteBooster type to preserve user-space mode.
> This would ensure that no user-space capacity is reduced
> when write booster is enabled.
> 
> Change-Id: I4144531a73ea3b5d5ede76beae45722366b1e75c
> Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
> ---
>   drivers/scsi/ufs/ufs-qcom.c | 7 +++++++
>   1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/scsi/ufs/ufs-qcom.c b/drivers/scsi/ufs/ufs-qcom.c
> index 6115ac6..59f3243 100644
> --- a/drivers/scsi/ufs/ufs-qcom.c
> +++ b/drivers/scsi/ufs/ufs-qcom.c
> @@ -1689,6 +1689,12 @@ static void ufs_qcom_device_reset(struct ufs_hba *hba)
>   	usleep_range(10, 15);
>   }
>   
> +static u32 ufs_qcom_wb_get_user_cap_mode(struct ufs_hba *hba)
> +{
> +	/* QCom prefers no user-space reduction mode */
> +	return UFS_WB_BUFF_PRESERVE_USER_SPACE;
> +}
> +
>   /**
>    * struct ufs_hba_qcom_vops - UFS QCOM specific variant operations
>    *
> @@ -1710,6 +1716,7 @@ static const struct ufs_hba_variant_ops ufs_hba_qcom_vops = {
>   	.resume			= ufs_qcom_resume,
>   	.dbg_register_dump	= ufs_qcom_dump_dbg_regs,
>   	.device_reset		= ufs_qcom_device_reset,
> +	.wb_get_user_cap_mode	= ufs_qcom_wb_get_user_cap_mode,
>   };
>   
>   /**
> 

Hi,
Please ignore this patch, I'll send the proper series.

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

  reply	other threads:[~2020-03-21  0:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  0:48 [<RFC PATCH v2> 0/3] WriteBooster Feature Support Asutosh Das
2020-03-21  0:48 ` Asutosh Das
2020-03-21  0:48 ` [<RFC PATCH v2> 1/3] scsi: ufs: add write booster feature support Asutosh Das
2020-03-21  0:52   ` Asutosh Das (asd)
2020-03-21  0:48 ` [<RFC PATCH v2> 2/3] ufs-qcom: scsi: configure write booster type Asutosh Das
2020-03-21  0:52   ` Asutosh Das (asd) [this message]
2020-03-21  0:48 ` [<RFC PATCH v2> 3/3] ufs: sysfs: add sysfs entries for write booster Asutosh Das
2020-03-21  0:52   ` Asutosh Das (asd)
2020-03-21  0:52 ` [<RFC PATCH v2> 0/3] WriteBooster Feature Support 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=13af63cc-c0f2-72c0-14aa-18ff8fd3751f@codeaurora.org \
    --to=asutoshd@codeaurora.org \
    --cc=asutoshd@qti.qualcomm.com \
    --cc=linux-scsi@vger.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.