linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Schiller <mschiller@tdt.de>
To: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-mips@linux-mips.org
Cc: linus.walleij@linaro.org, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, ralf@linux-mips.org, blogic@openwrt.org,
	hauke@hauke-m.de, jogo@openwrt.org, daniel.schwierzeck@gmail.com,
	Martin Schiller <mschiller@tdt.de>
Subject: [PATCH v3 5/5] pinctrl/lantiq: Implement gpio_chip.to_irq
Date: Thu, 26 Nov 2015 11:00:10 +0100	[thread overview]
Message-ID: <1448532010-30930-5-git-send-email-mschiller@tdt.de> (raw)
In-Reply-To: <1448532010-30930-1-git-send-email-mschiller@tdt.de>

From: John Crispin <blogic@openwrt.org>

Signed-off-by: John Crispin <blogic@openwrt.org>
Signed-off-by: Martin Schiller <mschiller@tdt.de>
---
Changes in v3:
- Moved this change into a separate patch

Changes in v2: 
None

 drivers/pinctrl/pinctrl-xway.c | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/drivers/pinctrl/pinctrl-xway.c b/drivers/pinctrl/pinctrl-xway.c
index b78baaa..8ae99a8 100644
--- a/drivers/pinctrl/pinctrl-xway.c
+++ b/drivers/pinctrl/pinctrl-xway.c
@@ -1573,6 +1573,18 @@ static int xway_gpio_dir_out(struct gpio_chip *chip, unsigned int pin, int val)
 	return 0;
 }
 
+static int xway_gpio_to_irq(struct gpio_chip *chip, unsigned offset)
+{
+	struct ltq_pinmux_info *info = dev_get_drvdata(chip->dev);
+	int i;
+
+	for (i = 0; i < info->num_exin; i++)
+		if (info->exin[i] == offset)
+			return ltq_eiu_get_irq(i);
+
+	return -1;
+}
+
 static struct gpio_chip xway_chip = {
 	.label = "gpio-xway",
 	.direction_input = xway_gpio_dir_in,
@@ -1581,6 +1593,7 @@ static struct gpio_chip xway_chip = {
 	.set = xway_gpio_set,
 	.request = gpiochip_generic_request,
 	.free = gpiochip_generic_free,
+	.to_irq = xway_gpio_to_irq,
 	.base = -1,
 };
 
-- 
2.1.4


  parent reply	other threads:[~2015-11-26 10:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 10:00 [PATCH v3 1/5] pinctrl/lantiq: updating devicetree binding description Martin Schiller
     [not found] ` <1448532010-30930-1-git-send-email-mschiller-h82pf8jx2gI@public.gmane.org>
2015-11-26 10:00   ` [PATCH v3 2/5] pinctrl/lantiq: introduce new dedicated devicetree bindings Martin Schiller
2015-11-30 12:13     ` Linus Walleij
2015-11-26 10:00 ` [PATCH v3 3/5] pinctrl/lantiq: update devicetree binding in dts file Martin Schiller
2015-11-30 12:15   ` Linus Walleij
2015-11-26 10:00 ` [PATCH v3 4/5] pinctrl/lantiq: Fix GPIO Setup of GPIO Port3 Martin Schiller
2015-11-30 12:17   ` Linus Walleij
2015-11-26 10:00 ` Martin Schiller [this message]
2015-11-30 12:21   ` [PATCH v3 5/5] pinctrl/lantiq: Implement gpio_chip.to_irq Linus Walleij
2015-11-30 12:11 ` [PATCH v3 1/5] pinctrl/lantiq: updating devicetree binding description 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=1448532010-30930-5-git-send-email-mschiller@tdt.de \
    --to=mschiller@tdt.de \
    --cc=blogic@openwrt.org \
    --cc=daniel.schwierzeck@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=hauke@hauke-m.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jogo@openwrt.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=ralf@linux-mips.org \
    --cc=robh+dt@kernel.org \
    /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).