From: William Zhang <william.zhang@broadcom.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] Enable MMIO GPIO on BCMBCA
Date: Wed, 18 Sep 2024 17:42:15 -0700 [thread overview]
Message-ID: <c56fb9a5-a53a-f59a-005e-140ed58ce134@broadcom.com> (raw)
In-Reply-To: <CACRpkdZTarsXp7D08gpXGLQwBppf6wJ8FBYop1wP2Xq-fxMm=A@mail.gmail.com>
On 09/17/2024 12:03 PM, Linus Walleij wrote:
> On Tue, Sep 17, 2024 at 8:13 PM William Zhang
> <william.zhang@broadcom.com> wrote:
>
>> If we upstream more elaborated driver later, it will be a dedicated gpio
>> controller driver and not use this basic mmio gpio and we can have
>> the new compatible.
>
> Thinking of it, in that case the driver would just use one reg = <>
> property for the whole I/O range used by the chip and then it need
> a new compatible anyway. Let's drop this for now. I'll switch over
> to the old compatible.
>
> It seems the approach taken with this SoC is a combination of
> simple GPIO and a separate extint (external interrupt) unit, so
> it does not need GPIOs to be able to trigger interrupts, which
> was my major worry.
>
I am looking into this and we should be able to support an irq chip for
this gpio controller that control external interrupt controller. So any
gpio that is configured in external interrupt controller can trigger
an interrupt.
Will post such driver for review when it is ready.
> Yours,
> Linus Walleij
>
prev parent reply other threads:[~2024-09-19 0:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 12:44 [PATCH 0/2] Enable MMIO GPIO on BCMBCA Linus Walleij
2024-09-17 12:44 ` [PATCH 1/2] dt-bindings: gpio: Add BCMBCA to MMIO compatibles Linus Walleij
2024-09-17 12:44 ` [PATCH 2/2] gpio: mmio: Support BCMBCA GPIO compatible Linus Walleij
2024-09-17 18:13 ` [PATCH 0/2] Enable MMIO GPIO on BCMBCA William Zhang
2024-09-17 19:03 ` Linus Walleij
2024-09-19 0:42 ` William Zhang [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=c56fb9a5-a53a-f59a-005e-140ed58ce134@broadcom.com \
--to=william.zhang@broadcom.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=robh@kernel.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).