From: Christoph Fritz <chf.fritz@googlemail.com>
To: Mark Brown <broonie@kernel.org>, Jagan Teki <jagan@amarulasolutions.com>
Cc: Adrien Grassein <adrien.grassein@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] regulator: pf8x00: set ramp_delay for bucks
Date: Mon, 25 Jan 2021 17:13:41 +0100 [thread overview]
Message-ID: <60d8eb8feefd26380cc9c6503f835e569be90465.camel@googlemail.com> (raw)
This patch sets ramp_delay for bucks to the max value given by the
datasheet.
Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
Reviewed-by: Adrien Grassein <adrien.grassein@gmail.com>
---
drivers/regulator/pf8x00-regulator.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/regulator/pf8x00-regulator.c b/drivers/regulator/pf8x00-regulator.c
index 1e5582d73405..edf5c88bf43e 100644
--- a/drivers/regulator/pf8x00-regulator.c
+++ b/drivers/regulator/pf8x00-regulator.c
@@ -351,6 +351,7 @@ static const struct regulator_ops pf8x00_vsnvs_ops = {
.type = REGULATOR_VOLTAGE, \
.id = PF8X00_BUCK ## _id, \
.owner = THIS_MODULE, \
+ .ramp_delay = 19000, \
.linear_ranges = pf8x00_sw1_to_6_voltages, \
.n_linear_ranges = \
ARRAY_SIZE(pf8x00_sw1_to_6_voltages), \
@@ -381,6 +382,7 @@ static const struct regulator_ops pf8x00_vsnvs_ops = {
.type = REGULATOR_VOLTAGE, \
.id = PF8X00_BUCK7, \
.owner = THIS_MODULE, \
+ .ramp_delay = 19000, \
.volt_table = voltages, \
.vsel_reg = (base) + SW_RUN_VOLT, \
.vsel_mask = 0xff, \
--
2.29.2
next reply other threads:[~2021-01-25 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 16:13 Christoph Fritz [this message]
2021-01-25 18:03 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2021-01-17 20:49 [PATCH] regulator: pf8x00: Add suspend support Christoph Fritz
2021-01-21 9:42 ` Christoph Fritz
2021-01-25 9:27 ` [PATCH] regulator: pf8x00: set ramp_delay for bucks Christoph Fritz
2021-01-25 9:54 ` Adrien Grassein
2021-01-25 13:09 ` Mark Brown
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=60d8eb8feefd26380cc9c6503f835e569be90465.camel@googlemail.com \
--to=chf.fritz@googlemail.com \
--cc=adrien.grassein@gmail.com \
--cc=broonie@kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®