From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Chris Paterson <chris.paterson2@renesas.com>,
Yusuke Ashiduka <ashiduka@fujitsu.com>,
Torii Kenichi <torii.ken1@jp.fujitsu.com>,
Fukui Yohhei <yohhei.fukui@denso-ten.com>,
Yasushi Asano <yasano@jp.adit-jv.com>,
Yuichi Kusakabe <yuichi.kusakabe@denso-ten.com>,
Andrew Gabbasov <andrew_gabbasov@mentor.com>,
Jiada Wang <jiada_wang@mentor.com>,
Eugeniu Rosca <rosca.eugeniu@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [RFC PATCH 1/3] dt-bindings: gpio-rcar: Add optional use-alternative-interrupt property
Date: Fri, 24 Apr 2020 10:06:59 +0200 [thread overview]
Message-ID: <CAMuHMdXvrBHuBpVbJ=fUcRsQ9qk4Q3Lr13DeJjiHanN3f8K+1g@mail.gmail.com> (raw)
In-Reply-To: <20200422101026.9220-2-erosca@de.adit-jv.com>
Hi Eugeniu,
CC devicetree
On Wed, Apr 22, 2020 at 12:11 PM Eugeniu Rosca <erosca@de.adit-jv.com> wrote:
> From: Torii Kenichi <torii.ken1@jp.fujitsu.com>
>
> When setting this property, you must set alternate interrupt number in
> the 'interrupts' property.
>
> Signed-off-by: Torii Kenichi <torii.ken1@jp.fujitsu.com>
> [erosca: tidy up the descriptions/comments]
> Signed-off-by: Eugeniu Rosca <erosca@de.adit-jv.com>
Thanks for your/forwarding this patch!
> --- a/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
> +++ b/Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
> @@ -50,6 +50,9 @@ Optional properties:
> - clocks: Must contain a reference to the functional clock. The property is
> mandatory if the hardware implements a controllable functional clock for
> the GPIO instance.
> + - use-alternative-interrupt: Use 'alternative' GPIO interrupt instead
renesas,use-alternative-interrupt?
(unless you can convince Rob this becomes a generic property).
> + of 'normal' GPIO interrupt. When you specify this property, you must
> + also change the 'interrupts' DT property.
In light of "DT describes the hardware", I think you should instead list
both interrupts in DT. I.e. first/single interrupt is the normal one,
second optional interrupt is the alternative one.
On R-Car Gen2, the oldest SoC family with this feature I could find,
they are called "ext_int" resp. "ext_alt_int", so introducing the
optional "clock-names" property would be a good idea, too.
> - gpio-reserved-ranges: See gpio.txt.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-04-24 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 10:10 [RFC PATCH 0/3] gpio: rcar: Add support for GPIO alternative interrupt Eugeniu Rosca
2020-04-22 10:10 ` [RFC PATCH 1/3] dt-bindings: gpio-rcar: Add optional use-alternative-interrupt property Eugeniu Rosca
2020-04-24 8:06 ` Geert Uytterhoeven [this message]
2020-04-22 10:10 ` [RFC PATCH 2/3] gpio: rcar: Add support for GPIO alternative interrupt Eugeniu Rosca
2020-04-24 8:36 ` Geert Uytterhoeven
2020-04-22 10:10 ` [RFC PATCH 3/3] [LOCAL] arm64: dts: renesas: ulcb: Showcase 'use-alternative-interrupt' Eugeniu Rosca
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='CAMuHMdXvrBHuBpVbJ=fUcRsQ9qk4Q3Lr13DeJjiHanN3f8K+1g@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=andrew_gabbasov@mentor.com \
--cc=ashiduka@fujitsu.com \
--cc=bgolaszewski@baylibre.com \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=grygorii.strashko@ti.com \
--cc=jiada_wang@mentor.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rosca.eugeniu@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=torii.ken1@jp.fujitsu.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=yasano@jp.adit-jv.com \
--cc=yohhei.fukui@denso-ten.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
--cc=yuichi.kusakabe@denso-ten.com \
/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).