From: Prathamesh Shete <pshete@nvidia.com>
To: <linus.walleij@linaro.org>, <bgolaszewski@baylibre.com>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<linux-gpio@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <smangipudi@nvidia.com>, <pshete@nvidia.com>
Subject: [PATCH v3 0/2] gpio: tegra: add multiple interrupt support
Date: Tue, 7 Sep 2021 13:02:22 +0530 [thread overview]
Message-ID: <20210907073224.3070-1-pshete@nvidia.com> (raw)
In-Reply-To: <YTWeSJ7jGamxx9Uu@orome.fritz.box>
From: pshete <pshete@nvidia.com>
These patches adds multiple interrupt support.
Each main GPIO is associated with 8 interrupts per controller in case of NON-AON GPIO's and
4 interrupts per controller in AON GPIO.
This is new feature starting Tegra194
The interrupt route map determines which interrupt line is to be used.
pshete (2):
gpio: tegra: add multiple interrupt support
arm64: tegra: GPIO Interrupt entries
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 49 +++++++++++++++++++++++-
drivers/gpio/gpio-tegra186.c | 27 ++++++++++---
2 files changed, 69 insertions(+), 7 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2021-09-07 7:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 10:15 [PATCH v2 0/2] gpio: tegra: add multiple interrupt support Prathamesh Shete
2021-09-03 10:15 ` [PATCH v2 1/2] " Prathamesh Shete
2021-09-06 4:51 ` Thierry Reding
2021-09-07 7:23 ` Prathamesh Shete
2021-09-07 7:30 ` [PATCH v2 0/2] " Prathamesh Shete
2021-09-07 7:30 ` [PATCH v2 1/2] " Prathamesh Shete
2021-09-07 7:30 ` [PATCH v2 2/2] arm64: tegra: GPIO Interrupt entries Prathamesh Shete
2021-09-07 7:32 ` Prathamesh Shete [this message]
2021-09-07 7:32 ` [PATCH v3 1/2] gpio: tegra: add multiple interrupt support Prathamesh Shete
2021-09-17 10:47 ` Thierry Reding
2021-09-07 7:32 ` [PATCH v3 2/2] arm64: tegra: GPIO Interrupt entries Prathamesh Shete
2021-09-22 9:29 ` Bartosz Golaszewski
2021-09-22 13:25 ` Thierry Reding
2021-09-24 14:37 ` Thierry Reding
2021-09-03 10:15 ` [PATCH v2 " Prathamesh Shete
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=20210907073224.3070-1-pshete@nvidia.com \
--to=pshete@nvidia.com \
--cc=bgolaszewski@baylibre.com \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=smangipudi@nvidia.com \
--cc=thierry.reding@gmail.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).