From: Asutosh Das <asutoshd@codeaurora.org>
To: cang@codeaurora.org, Avri.Altman@wdc.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Cc: Asutosh Das <asutoshd@codeaurora.org>, linux-arm-msm@vger.kernel.org
Subject: [<RFC RESEND PATCH v2> 0/3] WriteBooster Feature Support
Date: Fri, 20 Mar 2020 17:59:17 -0700 [thread overview]
Message-ID: <cover.1584752043.git.asutoshd@codeaurora.org> (raw)
Still a RFC patch, because I'm still expecting some comments
on the design.
v1 -> v2:
- Addressed comments on v1
- Supports shared buffer mode only
- Didn't use exception event as suggested.
The reason being while testing I saw that the WriteBooster
available buffer remains at 0x1 for a longer time if flush is
enabled all the time as compared to an event-based enablement.
This essentially means that writes go to the WriteBooster buffer
more. Spec says that the if flush is enabled, the device would
flush when it sees the command queue empty. So I guess that'd trigger
flush more than an event based approach.
Anyway the Vcc would be turned-off during system suspend, so flush
would stop anyway.
In this patchset, I never turn-off flush.
Hence the RFC.
Asutosh Das (3):
scsi: ufs: add write booster feature support
ufs-qcom: scsi: configure write booster type
ufs: sysfs: add sysfs entries for write booster
drivers/scsi/ufs/ufs-qcom.c | 7 ++
drivers/scsi/ufs/ufs-sysfs.c | 39 ++++++-
drivers/scsi/ufs/ufs.h | 37 ++++++-
drivers/scsi/ufs/ufshcd.c | 238 ++++++++++++++++++++++++++++++++++++++++++-
drivers/scsi/ufs/ufshcd.h | 9 ++
5 files changed, 324 insertions(+), 6 deletions(-)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
next reply other threads:[~2020-03-21 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 0:59 Asutosh Das [this message]
2020-03-21 0:59 ` [<RFC RESEND PATCH v2> 1/3] scsi: ufs: add write booster feature support Asutosh Das
2020-03-21 0:59 ` [<RFC RESEND PATCH v2> 2/3] ufs-qcom: scsi: configure write booster type Asutosh Das
2020-03-21 0:59 ` [<RFC RESEND PATCH v2> 3/3] ufs: sysfs: add sysfs entries for write booster Asutosh Das
2020-03-26 21:53 ` [<RFC RESEND PATCH v2> 0/3] WriteBooster Feature Support Avri Altman
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=cover.1584752043.git.asutoshd@codeaurora.org \
--to=asutoshd@codeaurora.org \
--cc=Avri.Altman@wdc.com \
--cc=cang@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).