01 Dec, 2019
1 commit
-
The wakeup specific IRQ management is no more needed to wake up the
stm32 platform. A relationship has been established between the EXTI and
the RX IRQ, just need to declare the EXTI interrupt instead of the
IPCC RX IRQ.Signed-off-by: Alexandre Torgue
Signed-off-by: Fabien Dessenne
Signed-off-by: Jassi Brar
11 Jul, 2019
1 commit
-
Add spinlock protection on IPCC register update to avoid race condition.
Without this fix, stm32_ipcc_set_bits and stm32_ipcc_clr_bits can be
called in parallel for different channels. This results in register
corruptions.Signed-off-by: Arnaud Pouliquen
Reviewed-by: Fabien Dessenne
Signed-off-by: Jassi Brar
09 May, 2019
1 commit
-
On failure of_irq_get() returns a negative value or zero, which is
not handled as an error in the existing implementation.
Instead of using this API, use platform_get_irq() that returns
exclusively a negative value on failure.
Also, do not output an error log in case of defer probe error.Signed-off-by: Fabien Dessenne
Signed-off-by: Jassi Brar
07 Mar, 2019
2 commits
-
If the "wakeup-source" property does not exist there is no need to call
device_init_wakeup("false") at probe.Signed-off-by: Fabien Dessenne
Signed-off-by: Jassi Brar -
By default do not enable the wakeup source.
This lets the userspace application decide whether the wakeup source
shall be enabled or not.Signed-off-by: Fabien Dessenne
Signed-off-by: Jassi Brar
22 Dec, 2018
1 commit
-
Get rid of some boilerplate driver removal code by using the newly added
device-managed registration API.Reviewed-by: Ludovic Barre
Signed-off-by: Thierry Reding
Signed-off-by: Jassi Brar
07 Jun, 2018
1 commit
-
The STMicroelectronics STM32 Inter-Processor Communication Controller
(IPCC) is used for communicating data between two processors.
It provides a non blocking signaling mechanism to post and retrieve
communication data in an atomic way.Signed-off-by: Fabien Dessenne
Signed-off-by: Ludovic Barre
Signed-off-by: Jassi Brar