From: Keerthy <j-keerthy@ti.com>
To: <linus.walleij@linaro.org>, <bgolaszewski@baylibre.com>
Cc: <lokeshvutla@ti.com>, <linux-gpio@vger.kernel.org>,
<t-kristo@ti.com>, <j-keerthy@ti.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 2/3] gpio: davinci: Add new compatible for K3 AM654 SoCs
Date: Wed, 5 Jun 2019 13:32:58 +0530 [thread overview]
Message-ID: <20190605080259.2462-3-j-keerthy@ti.com> (raw)
In-Reply-To: <20190605080259.2462-1-j-keerthy@ti.com>
Add new compatible for K3 AM654 SoCs.
Signed-off-by: Keerthy <j-keerthy@ti.com>
---
drivers/gpio/gpio-davinci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio-davinci.c
index 0977590eb996..fc494a84a29d 100644
--- a/drivers/gpio/gpio-davinci.c
+++ b/drivers/gpio/gpio-davinci.c
@@ -632,6 +632,7 @@ static int davinci_gpio_irq_setup(struct platform_device *pdev)
static const struct of_device_id davinci_gpio_ids[] = {
{ .compatible = "ti,keystone-gpio", keystone_gpio_get_irq_chip},
+ { .compatible = "ti,am654-gpio", keystone_gpio_get_irq_chip},
{ .compatible = "ti,dm6441-gpio", davinci_gpio_get_irq_chip},
{ /* sentinel */ },
};
--
2.17.1
next prev parent reply other threads:[~2019-06-05 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 8:02 [PATCH v2 0/3] gpio: davinci: Add support for TI K3 AM6 platform Keerthy
2019-06-05 8:02 ` [PATCH v2 1/3] gpio: davinci: Fix the compiler warning with ARM64 config enabled Keerthy
2019-06-07 22:34 ` Linus Walleij
2019-06-05 8:02 ` Keerthy [this message]
2019-06-05 14:26 ` [PATCH v2 2/3] gpio: davinci: Add new compatible for K3 AM654 SoCs Bartosz Golaszewski
2019-06-05 15:13 ` Keerthy
2019-06-06 7:49 ` Bartosz Golaszewski
2019-06-07 22:38 ` Linus Walleij
2019-06-07 22:36 ` Linus Walleij
2019-06-05 8:02 ` [PATCH v2 3/3] gpio: Davinci: Add K3 dependencies Keerthy
2019-06-07 22:36 ` Linus Walleij
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=20190605080259.2462-3-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=t-kristo@ti.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).