mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King <linux@armlinux.org.uk>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH] ARM: configs: stm32: Set CPU_V7M_NUM_IRQ to max value
Date: Fri, 31 Mar 2017 09:37:27 +0200	[thread overview]
Message-ID: <26da7d21-ee6e-e809-46b3-92f311c25a11@st.com> (raw)
In-Reply-To: <CAK8P3a3VYRUvFKd1CMTE-T-FhTx1YJr18Hqatmz7YK+A+JtFeQ@mail.gmail.com>

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
>

      reply	other threads:[~2017-03-31  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 10:09 Alexandre TORGUE
2017-03-30 15:36 ` Arnd Bergmann
2017-03-31  7:37   ` Alexandre Torgue [this message]

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=26da7d21-ee6e-e809-46b3-92f311c25a11@st.com \
    --to=alexandre.torgue@st.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=olof@lixom.net \
    /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

all inboxes | Powered by JetHome®