On Wed, Nov 06, 2019 at 11:21:43AM +0100, Ahmad Fatoum wrote:
> On platforms like the ARM STM32MP and the ARM64 Layerscape, firmware
> (i.e. barebox) is expected to fixup the correct PSCI version into the
> Linux device tree, so functionality like system reset via PSCI works.
>
> Add a generic
On Mon, Nov 04, 2019 at 03:57:33PM +0800, sendpa...@qq.com wrote:
> From: Du Huanpeng
>
> Signed-off-by: Du Huanpeng
> ---
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions |
Typo...
---
arch/arm/mach-stm32mp/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-stm32mp/Kconfig b/arch/arm/mach-stm32mp/Kconfig
index e74029158223..9b55a3d21843 100644
--- a/arch/arm/mach-stm32mp/Kconfig
+++ b/arch/arm/mach-stm32mp/Kconfig
@@ -5,7 +5,7
On Wed, Nov 06, 2019 at 08:11:48AM +0100, Ahmad Fatoum wrote:
> This imports the regulator_desc documentation for the fields barebox
> uses out of Linux v5.4-rc1.
>
> Signed-off-by: Ahmad Fatoum
> ---
> include/regulator.h | 28
> 1 file changed, 28 insertions(+)
For more usability, translate CPU_ON error codes into the error
descriptions found in the PSCI Platform Design Document[1].
[1]:
http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf
Signed-off-by: Ahmad Fatoum
---
System reset on the STM32MP may be done via PSCI when running TF-A
as first-stage boot loader. Provide a PSCI driver to simplify using it:
- A psci_invoke function is exported, so other code can use it
- A fixup for the PSCI device tree node is registered
- A reset and poweroff handler via PSCI
On platforms like the ARM STM32MP and the ARM64 Layerscape, firmware
(i.e. barebox) is expected to fixup the correct PSCI version into the
Linux device tree, so functionality like system reset via PSCI works.
Add a generic client driver that handles this and enable its usage for
the STM32MP.
v1
The smc command has a help defined, but unused. Wire it in, so
help smc and smc -invalidoption work as expected.
While at it, remove the unimplemented -z option. It's unneeded,
because -c turns off the CPU after starting it again already.
Also it seems it's not implementable without
There's already an option to use when debugging PSCI. Instead of
requiring users to #define DEBUG 1 as well, have the smc command be
usable when CONFIG_ARM_PSCI_DEBUG, not DEBUG is defined.
Signed-off-by: Ahmad Fatoum
---
arch/arm/cpu/psci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
ARM TF-A reports compatibility with PSCI v1.1 since v1.5. Upstream
ARM TF-A support for STM32MP was introduced with v1.6.
It's thus safe to assume that the STM32MP barebox will never have to
interact with a secure monitor implementing PSCI v0.1.
Overwrite the psci device tree compatible to
We'll probably be using compressed DTBs for all new boards as well, thus
move the ARM_USE_COMPRESSED_DTB, so it's always selected for STM32MP.
Signed-off-by: Ahmad Fatoum
---
arch/arm/Kconfig | 1 +
arch/arm/mach-stm32mp/Kconfig | 1 -
2 files changed, 1 insertion(+), 1 deletion(-)
On Wed, Nov 06, 2019 at 08:11:47AM +0100, Ahmad Fatoum wrote:
> For testing regulator drivers, it can be handy to enable/disable them
> from the shell prompt. Extend the regulator command to support this.
>
> Signed-off-by: Ahmad Fatoum
> ---
> drivers/regulator/core.c | 67
On Wed, Nov 06, 2019 at 08:11:46AM +0100, Ahmad Fatoum wrote:
> In preparation for teaching the regulator command how to enable and
> disable regulators, move the regulator command implementation to the
> regulator core, so the internal interfaces for iterating through the
> list of available
On Wed, Nov 06, 2019 at 08:10:32AM +0100, Ahmad Fatoum wrote:
> In cases where firmware provides PSCI >0.1, it may be prudent to use it as
> backend for reset and poweroff. This driver accomplishes this.
>
> Signed-off-by: Ahmad Fatoum
> ---
> drivers/misc/Kconfig | 5 +++
>
14 matches
Mail list logo
