From: Andrej Picej <andrej.picej@norik.com>
To: support.opensource@diasemi.com, lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org, andrej.picej@norik.com,
s.riedmueller@phytec.de
Subject: [PATCH 1/2] mfd: da9062: Make vbuck_a registers volatile
Date: Wed, 24 Nov 2021 08:00:00 +0100 [thread overview]
Message-ID: <20211124070001.2516750-1-andrej.picej@norik.com> (raw)
From: Stefan Riedmueller <s.riedmueller@phytec.de>
The VBUCK1_A, VBUCK2_A, VBUCK3_A and VBUCK4_A registers are used to set the
desired output voltage of the BUCK 1-4 buck regulators. These values can be
critical if used as input for core voltages. Thus make them volatile so
they do not get cached.
Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de>
Signed-off-by: Andrej Picej <andrej.picej@norik.com>
---
drivers/mfd/da9062-core.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/da9062-core.c b/drivers/mfd/da9062-core.c
index 2774b2cbaea6..c0dad5461946 100644
--- a/drivers/mfd/da9062-core.c
+++ b/drivers/mfd/da9062-core.c
@@ -572,6 +572,8 @@ static const struct regmap_range da9062_aa_volatile_ranges[] = {
regmap_reg_range(DA9062AA_COUNT_S, DA9062AA_SECOND_D),
regmap_reg_range(DA9062AA_SEQ, DA9062AA_SEQ),
regmap_reg_range(DA9062AA_EN_32K, DA9062AA_EN_32K),
+ regmap_reg_range(DA9062AA_VBUCK2_A, DA9062AA_VBUCK2_A),
+ regmap_reg_range(DA9062AA_VBUCK3_A, DA9062AA_VBUCK3_A),
};
static const struct regmap_access_table da9062_aa_readable_table = {
--
2.25.1
next reply other threads:[~2021-11-24 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 7:00 Andrej Picej [this message]
2021-11-24 7:00 ` [PATCH 2/2] mfd: da9063: Make vbcore " Andrej Picej
2021-11-24 9:34 ` Adam Thomson
2021-11-24 14:04 ` Andrej Picej
2021-11-24 14:47 ` Adam Thomson
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=20211124070001.2516750-1-andrej.picej@norik.com \
--to=andrej.picej@norik.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.riedmueller@phytec.de \
--cc=support.opensource@diasemi.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
all inboxes | Powered by JetHome®