Re: [PATCH] irqchip/stm32-exti: map direct event to irq parent

2020-07-17 Thread Alexandre Torgue
On 7/17/20 2:37 PM, Marc Zyngier wrote: On Fri, 10 Jul 2020 10:37:47 +0100, Alexandre Torgue wrote: Hi Marc, On 7/10/20 11:31 AM, Marc Zyngier wrote: Alexandre, On Wed, 08 Jul 2020 05:57:24 +0100, kernel test robot wrote: [1 ] Hi Alexandre, I love your patch! Perhaps something to

Re: [PATCH] irqchip/stm32-exti: map direct event to irq parent

2020-07-17 Thread Marc Zyngier
On Fri, 10 Jul 2020 10:37:47 +0100, Alexandre Torgue wrote: > > Hi Marc, > > On 7/10/20 11:31 AM, Marc Zyngier wrote: > > Alexandre, > > > > On Wed, 08 Jul 2020 05:57:24 +0100, > > kernel test robot wrote: > >> > >> [1 ] > >> Hi Alexandre, > >> > >> I love your patch! Perhaps something to

Re: [PATCH] irqchip/stm32-exti: map direct event to irq parent

2020-07-10 Thread Alexandre Torgue
Hi Marc, On 7/10/20 11:31 AM, Marc Zyngier wrote: Alexandre, On Wed, 08 Jul 2020 05:57:24 +0100, kernel test robot wrote: [1 ] Hi Alexandre, I love your patch! Perhaps something to improve: [auto build test WARNING on stm32/stm32-next] [also build test WARNING on soc/for-next v5.8-rc4

Re: [PATCH] irqchip/stm32-exti: map direct event to irq parent

2020-07-10 Thread Marc Zyngier
Alexandre, On Wed, 08 Jul 2020 05:57:24 +0100, kernel test robot wrote: > > [1 ] > Hi Alexandre, > > I love your patch! Perhaps something to improve: > > [auto build test WARNING on stm32/stm32-next] > [also build test WARNING on soc/for-next v5.8-rc4 next-20200707] > [If your patch is

Re: [PATCH] irqchip/stm32-exti: map direct event to irq parent

2020-07-07 Thread kernel test robot
Hi Alexandre, I love your patch! Perhaps something to improve: [auto build test WARNING on stm32/stm32-next] [also build test WARNING on soc/for-next v5.8-rc4 next-20200707] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use as

[PATCH] irqchip/stm32-exti: map direct event to irq parent

2020-07-06 Thread Alexandre Torgue
EXTI lines are mainly used to wake-up system from CStop low power mode. Currently, if a device wants to use a EXTI (direct) line as wakeup line, it has to declare 2 interrupts: - one for EXTI used to wake-up system (with dedicated_wake_irq api). - one for GIC used to get the wake up reason