From: alexandre.torgue@st.com (Alexandre Torgue)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 6/9] pinctrl: Add IRQ support to STM32 gpios
Date: Thu, 8 Sep 2016 17:47:02 +0200 [thread overview]
Message-ID: <0063a1ef-1b09-7cfc-f18b-76f2bb07eb84@st.com> (raw)
In-Reply-To: <CACRpkdZ_r0phJeScTYs_LmEHavcjGo6YjHPEHo-rKAv+rLgiFg@mail.gmail.com>
Hi Linus,
On 09/07/2016 11:06 PM, Linus Walleij wrote:
> On Tue, Sep 6, 2016 at 6:45 PM, Alexandre TORGUE
> <alexandre.torgue@st.com> wrote:
>
>> This patch adds IRQ support to STM32 gpios.
>>
>> The EXTI controller has 16 lines dedicated to GPIOs.
>> EXTI line n can be connected to only line n of one of the GPIO ports, for
>> example EXTI0 can be connected to either PA0, or PB0, or PC0...
>> This port selection is done by specifying the port number into System
>> Config registers.
>>
>> Signed-off-by: Maxime Coquelin <mcoquelin.stm32@gmail.com>
>> Signed-off-by: Alexandre TORGUE <alexandre.torgue@st.com>
>
>> +++ b/drivers/pinctrl/stm32/Kconfig
>> @@ -6,6 +6,8 @@ config PINCTRL_STM32
>> select PINMUX
>> select GENERIC_PINCONF
>> select GPIOLIB
>> + select GPIOLIB_IRQCHIP
>
> But you're not really using GPIOLIB_IRQCHIP. You have a different,
> super-complex irqchip in use.
Thanks Linus for this review. I will send a V5.
Just one question, when you say "super-complex irqchip in use", do you
mean I could use another (simplest) solution to handle this EXTI controller?
Regards
Alex
>
> So just don't select this.
>
>> + bank->gpio_chip.irqdomain = irq_domain_create_hierarchy(pctl->domain,
>> + 0, STM32_GPIO_IRQ_LINE, bank->fwnode,
>> + &stm32_gpio_domain_ops, bank);
>
> Don't use that irqdomain pointer inside the gpio_chip.
>
> Instead declare the irqdomain pointer inside struct stm32_gpio_bank
> or something like that.
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2016-09-08 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 16:45 [PATCH v4 0/9] Add STM32 EXTI interrupt controller support Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 1/9] Documentation: dt-bindings: Document STM32 EXTI controller bindings Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 2/9] drivers: irqchip: Add STM32 external interrupts support Alexandre TORGUE
2016-09-06 17:37 ` Jason Cooper
2016-09-08 9:03 ` Alexandre Torgue
2016-09-06 16:45 ` [PATCH v4 3/9] ARM: STM32: Select external interrupts controller Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 4/9] ARM: dts: Add EXTI controller node to stm32f429 Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 5/9] Documentation: dt-bindings: Add IRQ related properties of STM32 pinctrl Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 6/9] pinctrl: Add IRQ support to STM32 gpios Alexandre TORGUE
2016-09-07 21:06 ` Linus Walleij
2016-09-08 15:47 ` Alexandre Torgue [this message]
2016-09-12 12:58 ` Linus Walleij
2016-09-12 13:38 ` Alexandre Torgue
2016-09-06 16:45 ` [PATCH v4 7/9] ARM: dts: Add GPIO irq support to STM2F429 Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 8/9] ARM: dts: Declare push button as GPIO key on stm32f429 boards Alexandre TORGUE
2016-09-06 16:45 ` [PATCH v4 9/9] ARM: config: Enable GPIO Key driver in stm32_defconfig Alexandre TORGUE
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=0063a1ef-1b09-7cfc-f18b-76f2bb07eb84@st.com \
--to=alexandre.torgue@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).