From: Prathamesh Shete <pshete@nvidia.com>
To: <linus.walleij@linaro.org>, <bgolaszewski@baylibre.com>,
<linux-gpio@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <jonathanh@nvidia.com>,
<thierry.reding@gmail.com>
Cc: <smangipudi@nvidia.com>, <pshete@nvidia.com>,
Manish Bhardwaj <mbhardwaj@nvidia.com>
Subject: [PATCH v2] gpio: tegra186: add Tegra234 PMC compatible in GPIO driver
Date: Tue, 16 Aug 2022 15:57:25 +0530 [thread overview]
Message-ID: <20220816102725.14708-1-pshete@nvidia.com> (raw)
In-Reply-To: <Yhe0pCpfeCpyfPWg@orome>
Using this patch we are adding PMC compatible string for
Tegra234 in GPIO driver so the IRQ hierarchy can be set.
Signed-off-by: Manish Bhardwaj <mbhardwaj@nvidia.com>
Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
---
drivers/gpio/gpio-tegra186.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpio-tegra186.c b/drivers/gpio/gpio-tegra186.c
index 54d9fa7da9c1..824a355ff27a 100644
--- a/drivers/gpio/gpio-tegra186.c
+++ b/drivers/gpio/gpio-tegra186.c
@@ -669,6 +669,7 @@ static unsigned int tegra186_gpio_child_offset_to_irq(struct gpio_chip *chip,
static const struct of_device_id tegra186_pmc_of_match[] = {
{ .compatible = "nvidia,tegra186-pmc" },
{ .compatible = "nvidia,tegra194-pmc" },
+ { .compatible = "nvidia,tegra234-pmc" },
{ /* sentinel */ }
};
--
2.17.1
next prev parent reply other threads:[~2022-08-16 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 8:24 [PATCH] gpio: tegra186: add Tegra234 PMC compatible in GPIO driver Prathamesh Shete
2022-02-24 16:39 ` Thierry Reding
2022-08-16 10:27 ` Prathamesh Shete [this message]
2022-09-08 10:31 ` [PATCH v2] " Prathamesh Shete
2022-09-08 13:21 ` Linus Walleij
2023-01-09 20:30 ` Jon Hunter
2023-01-10 8:24 ` Linus Walleij
2023-01-11 8:27 ` Bartosz Golaszewski
2022-09-15 12:38 ` Thierry Reding
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=20220816102725.14708-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=mbhardwaj@nvidia.com \
--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 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.