From: Michael Grzeschik <m.grzeschik@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/4] regulator: pfuze: add support to other architectures
Date: Mon, 27 Jan 2020 16:50:11 +0100 [thread overview]
Message-ID: <20200127155013.4388-2-m.grzeschik@pengutronix.de> (raw)
In-Reply-To: <20200127155013.4388-1-m.grzeschik@pengutronix.de>
Currently the pfuze driver is build dependent to ARCH_IMX6. To make it
possible to work with ARCH_IMX8 we move the imx6_poweroff call to an own
poweroff handler.
Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
---
arch/arm/mach-imx/imx6.c | 8 ++++++++
drivers/regulator/Kconfig | 2 +-
drivers/regulator/pfuze.c | 2 --
3 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-imx/imx6.c b/arch/arm/mach-imx/imx6.c
index 41e0066add..8f1638c1ea 100644
--- a/arch/arm/mach-imx/imx6.c
+++ b/arch/arm/mach-imx/imx6.c
@@ -401,3 +401,11 @@ void __noreturn imx6_pm_stby_poweroff(void)
while(1);
}
+
+static int imx6_init(void)
+{
+ poweroff_handler_register_fn(imx6_pm_stby_poweroff);
+
+ return 0;
+}
+coredevice_initcall(imx6_init);
diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
index 28bd69a2a5..f47a115da2 100644
--- a/drivers/regulator/Kconfig
+++ b/drivers/regulator/Kconfig
@@ -19,7 +19,7 @@ config REGULATOR_BCM283X
config REGULATOR_PFUZE
bool "Freescale PFUZE100/200/3000 regulator driver"
depends on I2C
- depends on ARCH_IMX6
+ depends on ARCH_IMX6 || ARCH_IMX8MQ
config REGULATOR_STPMIC1
tristate "STMicroelectronics STPMIC1 PMIC Regulators"
diff --git a/drivers/regulator/pfuze.c b/drivers/regulator/pfuze.c
index 55f7eb5d4c..91aaec0e7e 100644
--- a/drivers/regulator/pfuze.c
+++ b/drivers/regulator/pfuze.c
@@ -142,8 +142,6 @@ static void pfuze_power_off_prepare(struct poweroff_handler *handler)
regmap_write_bits(pfuze_dev->map, PFUZE100_VGEN6VOL,
PFUZE100_VGENxLPWR | PFUZE100_VGENxSTBY,
PFUZE100_VGENxSTBY);
-
- imx6_pm_stby_poweroff();
}
static struct regmap_bus regmap_pfuze_i2c_bus = {
--
2.25.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-01-27 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 15:50 [PATCH 1/4] regulator: pfuze: remove unsued define Michael Grzeschik
2020-01-27 15:50 ` Michael Grzeschik [this message]
2020-01-28 8:45 ` [PATCH 2/4] regulator: pfuze: add support to other architectures Sascha Hauer
2020-01-29 22:19 ` Michael Grzeschik
2020-01-30 7:57 ` Sascha Hauer
2020-01-27 15:50 ` [PATCH 3/4] regulator: pfuze: add include regmap.h so struct regmap is known Michael Grzeschik
2020-01-27 15:50 ` [PATCH 4/4] ARM: phyCORE-i.MX8M SOM: add pmic initialisation for power good Michael Grzeschik
2020-01-28 8:48 ` Sascha Hauer
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=20200127155013.4388-2-m.grzeschik@pengutronix.de \
--to=m.grzeschik@pengutronix.de \
--cc=barebox@lists.infradead.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