From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: <linux-renesas-soc@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
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 <erosca@de.adit-jv.com>,
Eugeniu Rosca <rosca.eugeniu@gmail.com>
Subject: [RFC PATCH 0/3] gpio: rcar: Add support for GPIO alternative interrupt
Date: Wed, 22 Apr 2020 12:10:23 +0200 [thread overview]
Message-ID: <20200422101026.9220-1-erosca@de.adit-jv.com> (raw)
The motivation behind this series is described in commit
("gpio: rcar: Add support for GPIO alternative interrupt").
The reasons for which RFC tag is attached are:
- Have Renesas/linux-gpio communities been facing GPIO interrupt
partitioning questions in the past (specifically AP vs RT)?
- Is it a no-go to have mandatory DTS dependencies like updating
'interrupts' on specifying the new 'use-alternative-interrupt'?
Many thanks for your comments!
Eugeniu Rosca (1):
[LOCAL] arm64: dts: renesas: ulcb: Showcase 'use-alternative-interrupt'
Torii Kenichi (2):
dt-bindings: gpio-rcar: Add optional use-alternative-interrupt property
gpio: rcar: Add support for GPIO alternative interrupt
Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt | 3 +++
arch/arm64/boot/dts/renesas/ulcb.dtsi | 40 ++++++++++++++++++++++++++++++++++++++++
drivers/gpio/gpio-rcar.c | 22 +++++++++++++++++-----
3 files changed, 60 insertions(+), 5 deletions(-)
--
2.26.0
next reply other threads:[~2020-04-22 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 10:10 Eugeniu Rosca [this message]
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
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=20200422101026.9220-1-erosca@de.adit-jv.com \
--to=erosca@de.adit-jv.com \
--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=geert+renesas@glider.be \
--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=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
all inboxes | Powered by JetHome®