From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Marek Vasut <marek.vasut+renesas@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH/RFC 3/5] mfd: bd9571mwv: Allow DDR Backup Power register access
Date: Tue, 10 Oct 2017 17:26:16 +0200 [thread overview]
Message-ID: <1507649178-31473-4-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1507649178-31473-1-git-send-email-geert+renesas@glider.be>
Enable read/write access to the BD9571MWV_BKUP_MODE_CNT register, which
is a.o. used to configure DDR Backup Power.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/mfd/bd9571mwv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mfd/bd9571mwv.c b/drivers/mfd/bd9571mwv.c
index 64e088dfe7b05b5b..503979c81dae11bb 100644
--- a/drivers/mfd/bd9571mwv.c
+++ b/drivers/mfd/bd9571mwv.c
@@ -29,6 +29,7 @@ static const struct mfd_cell bd9571mwv_cells[] = {
static const struct regmap_range bd9571mwv_readable_yes_ranges[] = {
regmap_reg_range(BD9571MWV_VENDOR_CODE, BD9571MWV_PRODUCT_REVISION),
+ regmap_reg_range(BD9571MWV_BKUP_MODE_CNT, BD9571MWV_BKUP_MODE_CNT),
regmap_reg_range(BD9571MWV_AVS_SET_MONI, BD9571MWV_AVS_DVFS_VID(3)),
regmap_reg_range(BD9571MWV_VD18_VID, BD9571MWV_VD33_VID),
regmap_reg_range(BD9571MWV_DVFS_VINIT, BD9571MWV_DVFS_VINIT),
@@ -44,6 +45,7 @@ static const struct regmap_access_table bd9571mwv_readable_table = {
};
static const struct regmap_range bd9571mwv_writable_yes_ranges[] = {
+ regmap_reg_range(BD9571MWV_BKUP_MODE_CNT, BD9571MWV_BKUP_MODE_CNT),
regmap_reg_range(BD9571MWV_AVS_VD09_VID(0), BD9571MWV_AVS_VD09_VID(3)),
regmap_reg_range(BD9571MWV_DVFS_SETVID, BD9571MWV_DVFS_SETVID),
regmap_reg_range(BD9571MWV_GPIO_DIR, BD9571MWV_GPIO_OUT),
--
2.7.4
next prev parent reply other threads:[~2017-10-10 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 15:26 [PATCH/RFC 0/5] arm64: dts: renesas: Salvator-X/XS: Enable DDR Backup Mode Geert Uytterhoeven
2017-10-10 15:26 ` [PATCH/RFC 2/5] mfd: bd9571mwv: Add DDR Backup Power register bit definitions Geert Uytterhoeven
2017-10-13 8:51 ` Lee Jones
2018-04-23 18:05 ` Applied "mfd: bd9571mwv: Add DDR Backup Power register bit definitions" to the regulator tree Mark Brown
2017-10-10 15:26 ` Geert Uytterhoeven [this message]
[not found] ` <1507649178-31473-4-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-10-13 8:58 ` [PATCH/RFC 3/5] mfd: bd9571mwv: Allow DDR Backup Power register access Lee Jones
2017-10-13 9:06 ` Geert Uytterhoeven
2017-10-13 9:56 ` Lee Jones
2018-04-23 18:05 ` Applied "mfd: bd9571mwv: Allow DDR Backup Power register access" to the regulator tree Mark Brown
[not found] ` <1507649178-31473-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-10-10 15:26 ` [PATCH/RFC 1/5] dt-bindings: mfd: bd9571mwv: Document rohm,ddr-backup-power Geert Uytterhoeven
2017-10-13 8:55 ` Lee Jones
2017-10-13 9:02 ` Geert Uytterhoeven
2017-10-13 10:00 ` Lee Jones
2017-10-10 15:26 ` [PATCH/RFC 4/5] regulator: bd9571mwv: Add support for backup mode Geert Uytterhoeven
[not found] ` <1507649178-31473-5-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2017-10-18 11:02 ` Mark Brown
2017-10-18 11:19 ` Geert Uytterhoeven
2017-10-18 11:24 ` Mark Brown
2017-10-18 11:28 ` Geert Uytterhoeven
2017-10-24 8:34 ` Mark Brown
2017-10-10 15:26 ` [PATCH/RFC 5/5] arm64: dts: renesas: salvator-common: Configure PMIC for DDR Backup Power Geert Uytterhoeven
2017-10-16 7:09 ` Simon Horman
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=1507649178-31473-4-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).