From: Stanley Chu <stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
To: linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
avri.altman-Sjgp3cTcYWE@public.gmane.org,
alim.akhtar-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
pedrom.sousa-HKixBCOQz3hWk0Htik3J/w@public.gmane.org
Cc: marc.w.gonzalez-GANU6spQydw@public.gmane.org,
chun-hung.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
kuohong.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
peter.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: scsi: ufs: Fix regulator operations and remove "<name>-fixed-regulator" device tree property
Date: Mon, 18 Mar 2019 10:14:34 +0800 [thread overview]
Message-ID: <1552875280-16196-1-git-send-email-stanley.chu@mediatek.com> (raw)
Hi,
Sorry please help review V3 instead of previous versions.
In this version I fix and add more details in commit messages, and add one patch to fix "undefined voltage range" issue as well.
This patch series fixes UFS regulator operations, including voltage and current (re-)configuration flow during initialization or different power modes.
Besides, remove "<name>-fixed-regulator" device tree property because it is not necessary anymore after fixes.
V3:
- Fix and add more details in commit messages.
- Add one patch "scsi: ufs: Avoid configuring undefined voltage range on a regulator".
V2:
- Add two patches to prepare to and remove "<name>-fixed-regulator" device tree property.
- Add more details on patch "scsi: ufs: remove unused min_uA field in struct ufs_vreg" (Marc Gonzalez).
Stanley Chu (5):
scsi: ufs: Remove unused min_uA field in struct ufs_vreg
scsi: ufs: Avoid configuring undefined voltage range on a regulator
scsi: ufs: Fix regulator load and icc-level configuration
scsi: ufs: Change "<name>-max-microamp" to non-mandatory property
scsi: ufs: Remove "<name>-fixed-regulator" device tree property
drivers/scsi/ufs/ufs.h | 1 -
drivers/scsi/ufs/ufshcd-pltfrm.c | 14 +++-----------
drivers/scsi/ufs/ufshcd.c | 28 ++++++++++++++++++++--------
3 files changed, 23 insertions(+), 20 deletions(-)
next reply other threads:[~2019-03-18 2:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 2:14 Stanley Chu [this message]
[not found] ` <1552875280-16196-1-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-18 2:14 ` [PATCH v3 0/5] scsi: ufs: Fix regulator operations and remove "<name>-fixed-regulator" device tree property Stanley Chu
[not found] ` <1552875280-16196-2-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-25 1:16 ` Stanley Chu
2019-03-18 2:14 ` [PATCH v3 1/5] scsi: ufs: Remove unused min_uA field in struct ufs_vreg Stanley Chu
[not found] ` <1552875280-16196-3-git-send-email-stanley.chu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2019-03-19 3:06 ` Alim Akhtar
2019-03-18 2:14 ` [PATCH v3 2/5] scsi: ufs: Avoid configuring undefined voltage range on a regulator Stanley Chu
2019-03-18 2:14 ` [PATCH v3 3/5] scsi: ufs: Fix regulator load and icc-level configuration Stanley Chu
2019-03-18 2:14 ` [PATCH v3 4/5] scsi: ufs: Change "<name>-max-microamp" to non-mandatory property Stanley Chu
2019-03-18 2:14 ` [PATCH v3 5/5] scsi: ufs: Remove "<name>-fixed-regulator" device tree property Stanley Chu
-- strict thread matches above, loose matches on Subject: below --
2019-03-15 9:26 scsi: ufs: fix regulator operations and remove " 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=1552875280-16196-1-git-send-email-stanley.chu@mediatek.com \
--to=stanley.chu-nus5lvnupcjwk0htik3j/w@public.gmane.org \
--cc=alim.akhtar-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=avri.altman-Sjgp3cTcYWE@public.gmane.org \
--cc=chun-hung.wu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=kuohong.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marc.w.gonzalez-GANU6spQydw@public.gmane.org \
--cc=martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pedrom.sousa-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=peter.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.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.