Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20210617144602.2557619-1-fabien.dessenne@foss.st.com>
In-Reply-To: <20210617144602.2557619-1-fabien.dessenne@foss.st.com>
From:   Linus Walleij <linus.walleij@linaro.org>
Date:   Sat, 26 Jun 2021 01:53:48 +0200
Message-ID: <CACRpkdYOk8TgrQbEOMb-ZgZ8a6ZOYPgkfyWDr-Li6w0mfFO7KQ@mail.gmail.com>
Subject: Re: [PATCH] pinctrl: stm32: check for IRQ MUX validity during alloc()
To:     Fabien Dessenne <fabien.dessenne@foss.st.com>
Cc:     Maxime Coquelin <mcoquelin.stm32@gmail.com>,
        Alexandre Torgue <alexandre.torgue@foss.st.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
        linux-stm32@st-md-mailman.stormreply.com,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        linux-kernel <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Jun 17, 2021 at 4:46 PM Fabien Dessenne
<fabien.dessenne@foss.st.com> wrote:

> Considering the following irq_domain_ops call chain:
> - .alloc() is called when a clients calls platform_get_irq() or
>   gpiod_to_irq()
> - .activate() is called next, when the clients calls
>   request_threaded_irq()
> Check for the IRQ MUX conflict during the first stage (alloc instead of
> activate). This avoids to provide the client with an IRQ that can't be
> used.
>
> Signed-off-by: Fabien Dessenne <fabien.dessenne@foss.st.com>

Patch applied!

Yours,
Linus Walleij