From: Stanley Chu <stanley.chu@mediatek.com>
To: <linux-scsi@vger.kernel.org>, <martin.petersen@oracle.com>,
<avri.altman@wdc.com>, <alim.akhtar@samsung.com>,
<jejb@linux.ibm.com>, <asutoshd@codeaurora.org>
Cc: bvanassche@acm.org, andy.teng@mediatek.com,
chun-hung.wu@mediatek.com, kuohong.wang@mediatek.com,
linux-kernel@vger.kernel.org, cang@codeaurora.org,
linux-mediatek@lists.infradead.org, peter.wang@mediatek.com,
matthias.bgg@gmail.com, Stanley Chu <stanley.chu@mediatek.com>,
linux-arm-kernel@lists.infradead.org, beanhuo@micron.com
Subject: [PATCH v3 0/5] scsi: ufs: Fix WriteBooster and cleanup UFS driver
Date: Sun, 17 May 2020 01:46:10 +0800 [thread overview]
Message-ID: <20200516174615.15445-1-stanley.chu@mediatek.com> (raw)
Hi,
This patch set fixes some WriteBooster issues and do small cleanup in UFS driver
v2 -> v3
- Introduce patch [5] to fix possible VCC power drain during runtime suspend (Asutosh)
v1 -> v2
- Remove dummy new line in patch [4] (Asutosh)
- Add more limitation to allow WriteBooster flush during Hibern8 in runtime-suspend. Now the device power mode is kept as Active power mode only if link is put in Hibern8 or Auto-Hibern8 is enabled during runtime-suspend (Asutosh)
Stanley Chu (5):
scsi: ufs: Remove unnecessary memset for dev_info
scsi: ufs: Allow WriteBooster on UFS 2.2 devices
scsi: ufs: Fix index of attributes query for WriteBooster feature
scsi: ufs: Fix WriteBooster flush during runtime suspend
scsi: ufs: Fix possible VCC power drain during runtime suspend
drivers/scsi/ufs/ufs-sysfs.c | 13 ++++-
drivers/scsi/ufs/ufs.h | 2 +-
drivers/scsi/ufs/ufshcd.c | 99 +++++++++++++++++++++++++-----------
drivers/scsi/ufs/ufshcd.h | 3 +-
4 files changed, 82 insertions(+), 35 deletions(-)
--
2.18.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next reply other threads:[~2020-05-16 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 17:46 Stanley Chu [this message]
2020-05-16 17:46 ` [PATCH v3 1/5] scsi: ufs: Remove unnecessary memset for dev_info Stanley Chu
2020-05-17 6:11 ` Avri Altman
2020-05-16 17:46 ` [PATCH v3 2/5] scsi: ufs: Allow WriteBooster on UFS 2.2 devices Stanley Chu
2020-05-17 6:12 ` Avri Altman
2020-05-16 17:46 ` [PATCH v3 3/5] scsi: ufs: Fix index of attributes query for WriteBooster feature Stanley Chu
2020-05-17 6:13 ` Avri Altman
2020-05-16 17:46 ` [PATCH v3 4/5] scsi: ufs: Fix WriteBooster flush during runtime suspend Stanley Chu
2020-05-16 17:46 ` [PATCH v3 5/5] scsi: ufs: Fix possible VCC power drain " Stanley Chu
2020-05-19 16:27 ` Asutosh Das (asd)
2020-05-20 7:23 ` Stanley Chu
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=20200516174615.15445-1-stanley.chu@mediatek.com \
--to=stanley.chu@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.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