linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value
@ 2017-03-23 10:09 Alexandre TORGUE
  2017-03-30 15:36 ` Arnd Bergmann
  0 siblings, 1 reply; 3+ messages in thread
From: Alexandre TORGUE @ 2017-03-23 10:09 UTC (permalink / raw)
  To: linux-arm-kernel

stm32_defconfig is used for several STM32 MCU: STM32F429, STM32F469,
STM32F746 and now STM32H743. Each of MCU listed have different interrupts
number mapped on NVIC. STM32F429: 81, STM32F469: 92, STM32F746: 97 and
STM32H743: 149. I could set CPU_V7M_NUM_IRQ to 149 but in order to avoid
forgetting to update this value for next STM32 MCU I prefer to set it to
max value: 240.

Signed-off-by: Alexandre TORGUE <alexandre.torgue@st.com>

diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig
index a9d8e3c..7c9c157 100644
--- a/arch/arm/configs/stm32_defconfig
+++ b/arch/arm/configs/stm32_defconfig
@@ -20,6 +20,7 @@ CONFIG_EMBEDDED=y
 # CONFIG_MMU is not set
 CONFIG_ARM_SINGLE_ARMV7M=y
 CONFIG_ARCH_STM32=y
+CONFIG_CPU_V7M_NUM_IRQ=240
 CONFIG_SET_MEM_PARAM=y
 CONFIG_DRAM_BASE=0x90000000
 CONFIG_FLASH_MEM_BASE=0x08000000
-- 
1.9.1

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value
  2017-03-23 10:09 [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value Alexandre TORGUE
@ 2017-03-30 15:36 ` Arnd Bergmann
  2017-03-31  7:37   ` Alexandre Torgue
  0 siblings, 1 reply; 3+ messages in thread
From: Arnd Bergmann @ 2017-03-30 15:36 UTC (permalink / raw)
  To: linux-arm-kernel

On Thu, Mar 23, 2017 at 11:09 AM, Alexandre TORGUE
<alexandre.torgue@st.com> wrote:
> stm32_defconfig is used for several STM32 MCU: STM32F429, STM32F469,
> STM32F746 and now STM32H743. Each of MCU listed have different interrupts
> number mapped on NVIC. STM32F429: 81, STM32F469: 92, STM32F746: 97 and
> STM32H743: 149. I could set CPU_V7M_NUM_IRQ to 149 but in order to avoid
> forgetting to update this value for next STM32 MCU I prefer to set it to
> max value: 240.
>
> Signed-off-by: Alexandre TORGUE <alexandre.torgue@st.com>

It's not entirely clear who you want to apply this (if any), given that you sent
the patch to yourself. I've applied it to next/defconfig now, hope that's
what you intended.

      Arnd

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value
  2017-03-30 15:36 ` Arnd Bergmann
@ 2017-03-31  7:37   ` Alexandre Torgue
  0 siblings, 0 replies; 3+ messages in thread
From: Alexandre Torgue @ 2017-03-31  7:37 UTC (permalink / raw)
  To: linux-arm-kernel

Hi Arnd

On 03/30/2017 05:36 PM, Arnd Bergmann wrote:
> On Thu, Mar 23, 2017 at 11:09 AM, Alexandre TORGUE
> <alexandre.torgue@st.com> wrote:
>> stm32_defconfig is used for several STM32 MCU: STM32F429, STM32F469,
>> STM32F746 and now STM32H743. Each of MCU listed have different interrupts
>> number mapped on NVIC. STM32F429: 81, STM32F469: 92, STM32F746: 97 and
>> STM32H743: 149. I could set CPU_V7M_NUM_IRQ to 149 but in order to avoid
>> forgetting to update this value for next STM32 MCU I prefer to set it to
>> max value: 240.
>>
>> Signed-off-by: Alexandre TORGUE <alexandre.torgue@st.com>
>
> It's not entirely clear who you want to apply this (if any), given that you sent
> the patch to yourself. I've applied it to next/defconfig now, hope that's
> what you intended.

Actually, I pushed it mainly to share the patch and check comments. I 
planned to add it in my pull request, but no pb if you already took it :).

Regards
Alex

>
>       Arnd
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-31  7:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-23 10:09 [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value Alexandre TORGUE
2017-03-30 15:36 ` Arnd Bergmann
2017-03-31  7:37   ` Alexandre Torgue

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).