From: Rob Herring <robh@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: devicetree@vger.kernel.org, Hector Martin <marcan@marcan.st>,
Sven Peter <sven@svenpeter.dev>, Marc Zyngier <maz@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
nd@arm.com, Rob Herring <robh+dt@kernel.org>,
Mark Kettenis <kettenis@openbsd.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 2/5] dt-bindings: pinctrl: add #interrupt-cells to apple,pinctrl
Date: Mon, 18 Oct 2021 14:30:18 -0500 [thread overview]
Message-ID: <YW3LSl1yVifMcg5m@robh.at.kernel.org> (raw)
In-Reply-To: <20211016141839.45460-3-joey.gouly@arm.com>
On Sat, 16 Oct 2021 15:18:36 +0100, Joey Gouly wrote:
> The GPIO/pinctrl hardware can act as an interrupt-controller, so add
> the #interrupt-cells property to the binding.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> ---
> Documentation/devicetree/bindings/pinctrl/apple,pinctrl.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-10-18 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 14:18 [PATCH v3 0/5] pinctrl/GPIO driver for Apple SoCs Joey Gouly
2021-10-16 14:18 ` [PATCH v3 1/5] gpio: Allow per-parent interrupt data Joey Gouly
2021-10-16 22:37 ` Linus Walleij
2021-11-04 15:30 ` Bartosz Golaszewski
2021-10-16 14:18 ` [PATCH v3 2/5] dt-bindings: pinctrl: add #interrupt-cells to apple,pinctrl Joey Gouly
2021-10-17 10:20 ` Sven Peter
2021-10-18 19:30 ` Rob Herring [this message]
2021-10-16 14:18 ` [PATCH v3 3/5] dt-bindings: pinctrl: Add apple,npins property " Joey Gouly
2021-10-18 19:30 ` Rob Herring
2021-10-16 14:18 ` [PATCH v3 4/5] pinctrl: add pinctrl/GPIO driver for Apple SoCs Joey Gouly
2021-10-16 18:07 ` Alyssa Rosenzweig
2021-10-16 19:00 ` Mark Kettenis
2021-10-16 22:57 ` Linus Walleij
2021-10-16 14:18 ` [PATCH v3 5/5] MAINTAINERS: add pinctrl-apple-gpio to ARM/APPLE MACHINE Joey Gouly
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=YW3LSl1yVifMcg5m@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alyssa.rosenzweig@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=joey.gouly@arm.com \
--cc=kettenis@openbsd.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=robh+dt@kernel.org \
--cc=sven@svenpeter.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.