From: nguyenb@codeaurora.org
To: cang@codeaurora.org, asutoshd@codeaurora.org,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Supports Reading UFS's Vcc Voltage Levels from DT
Date: Thu, 10 Sep 2020 01:29:58 +0000 [thread overview]
Message-ID: <0101017475a232b3-44f95537-e287-4e5c-b956-c0f8c56c1a3c-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <cover.1598939393.git.nguyenb@codeaurora.org>
On 2020-08-31 23:00, Bao D. Nguyen wrote:
> UFS's specification supports a range of Vcc operating voltages.
> Allows selecting the UFS Vcc operating voltage levels by reading
> the UFS's vcc-voltage-level in the device tree.
>
> Bao D. Nguyen (2):
> scsi: dt-bindings: ufs: Add vcc-voltage-level for UFS
> scsi: ufs: Support reading UFS's Vcc voltage from device tree
>
> Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt | 2 ++
> drivers/scsi/ufs/ufshcd-pltfrm.c | 15
> ++++++++++++---
> 2 files changed, 14 insertions(+), 3 deletions(-)
Hello, please help review the change and comment if any.
Thanks!
Bao
prev parent reply other threads:[~2020-09-10 2:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 6:00 [PATCH v1 0/2] Supports Reading UFS's Vcc Voltage Levels from DT Bao D. Nguyen
2020-09-01 6:00 ` [PATCH v1 1/2] scsi: dt-bindings: ufs: Add vcc-voltage-level for UFS Bao D. Nguyen
2020-09-13 9:35 ` Avri Altman
2020-09-14 16:19 ` nguyenb
2020-09-14 18:35 ` Rob Herring
2020-09-15 8:10 ` nguyenb
2020-09-18 19:01 ` Rob Herring
2020-09-22 0:22 ` nguyenb
2020-09-22 0:36 ` Bjorn Andersson
2020-09-23 17:32 ` nguyenb
2020-09-15 4:41 ` Bjorn Andersson
2020-09-15 8:14 ` nguyenb
2020-09-15 13:43 ` Bjorn Andersson
2020-09-15 16:47 ` nguyenb
2020-09-15 18:36 ` Bjorn Andersson
2020-09-01 6:00 ` [PATCH v1 2/2] scsi: ufs: Support reading UFS's Vcc voltage from device tree Bao D. Nguyen
2020-09-13 9:37 ` Avri Altman
2020-09-14 18:43 ` nguyenb
2020-09-15 6:51 ` Avri Altman
2020-09-15 13:46 ` Bjorn Andersson
2020-09-10 1:29 ` nguyenb [this message]
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=0101017475a232b3-44f95537-e287-4e5c-b956-c0f8c56c1a3c-000000@us-west-2.amazonses.com \
--to=nguyenb@codeaurora.org \
--cc=asutoshd@codeaurora.org \
--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).