From: Mark Zhang <markz@nvidia.com>
To: lgirdwood@gmail.com, broonie@kernel.org, linux-kernel@vger.kernel.org
Cc: linux-tegra@vger.kernel.org, Mark Zhang <markz@nvidia.com>,
Venkat Reddy Talla <vreddytalla@nvidia.com>
Subject: [PATCH 2/2] regulator: max77620: disable notifier events for FPS rails
Date: Thu, 10 Jan 2019 12:11:17 +0800 [thread overview]
Message-ID: <20190110041117.8216-2-markz@nvidia.com> (raw)
In-Reply-To: <20190110041117.8216-1-markz@nvidia.com>
Disabling regulator notifier events if regulator is
configured part of flexible power sequencer(FPS),
there is no SW control to enable/disable if regulator
is configured part of FPS, so disabling notifier events
if client driver try to enable/disable FPS rails.
Signed-off-by: Venkat Reddy Talla <vreddytalla@nvidia.com>
Signed-off-by: Mark Zhang <markz@nvidia.com>
---
drivers/regulator/max77620-regulator.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/regulator/max77620-regulator.c b/drivers/regulator/max77620-regulator.c
index cd93cf53e23c..20e985071bfc 100644
--- a/drivers/regulator/max77620-regulator.c
+++ b/drivers/regulator/max77620-regulator.c
@@ -823,6 +823,13 @@ static int max77620_regulator_probe(struct platform_device *pdev)
rdesc->name, ret);
return ret;
}
+
+ /* there is no SW control for rails which are part of FPS
+ * set always no contraint to true to avoid regulator
+ * enable/disable notification
+ */
+ if (pmic->reg_pdata[id].active_fps_src != MAX77620_FPS_SRC_NONE)
+ rdev->constraints->always_on = true;
}
return 0;
--
2.19.2
next prev parent reply other threads:[~2019-01-10 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 4:11 [PATCH 1/2] regulator: max77620: Initialize values for DT properties Mark Zhang
2019-01-10 4:11 ` Mark Zhang [this message]
2019-01-10 12:07 ` [PATCH 2/2] regulator: max77620: disable notifier events for FPS rails Mark Brown
2019-01-11 13:35 ` Mark Zhang
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=20190110041117.8216-2-markz@nvidia.com \
--to=markz@nvidia.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=vreddytalla@nvidia.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