From: Ye Zhang <ye.zhang@rock-chips.com>
To: Ye Zhang <ye.zhang@rock-chips.com>,
linus.walleij@linaro.org, brgl@bgdev.pl, heiko@sntech.de,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com, tao.huang@rock-chips.com,
finley.xiao@rock-chips.com, tim.chen@rock-chips.com,
elaine.zhang@rock-chips.com,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: [PATCH v5 4/4] gpio: rockchip: Set input direction when request irq
Date: Tue, 12 Nov 2024 09:54:08 +0800 [thread overview]
Message-ID: <20241112015408.3139996-5-ye.zhang@rock-chips.com> (raw)
In-Reply-To: <20241112015408.3139996-1-ye.zhang@rock-chips.com>
Since the GPIO can only generate interrupts when its direction is set to
input, it is set to input before requesting the interrupt resources.
Signed-off-by: Ye Zhang <ye.zhang@rock-chips.com>
Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
---
drivers/gpio/gpio-rockchip.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-rockchip.c b/drivers/gpio/gpio-rockchip.c
index c090cac694bf..cdfdd5501a1e 100644
--- a/drivers/gpio/gpio-rockchip.c
+++ b/drivers/gpio/gpio-rockchip.c
@@ -476,8 +476,11 @@ static int rockchip_irq_reqres(struct irq_data *d)
{
struct irq_chip_generic *gc = irq_data_get_irq_chip_data(d);
struct rockchip_pin_bank *bank = gc->private;
+ irq_hw_number_t hwirq = irqd_to_hwirq(d);
- return gpiochip_reqres_irq(&bank->gpio_chip, d->hwirq);
+ rockchip_gpio_direction_input(&bank->gpio_chip, hwirq);
+
+ return gpiochip_reqres_irq(&bank->gpio_chip, hwirq);
}
static void rockchip_irq_relres(struct irq_data *d)
--
2.34.1
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-11-12 2:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 1:54 [PATCH v5 0/4] gpio: rockchip: Update the GPIO driver Ye Zhang
2024-11-12 1:54 ` [PATCH v5 1/4] gpio: rockchip: explan the format of the GPIO version ID Ye Zhang
2024-11-12 1:54 ` [PATCH v5 2/4] gpio: rockchip: change the GPIO version judgment logic Ye Zhang
2024-11-12 10:37 ` Andy Shevchenko
2024-11-12 1:54 ` [PATCH v5 3/4] gpio: rockchip: support new version GPIO Ye Zhang
2024-11-12 1:54 ` Ye Zhang [this message]
2024-11-12 8:48 ` [PATCH v5 4/4] gpio: rockchip: Set input direction when request irq Bartosz Golaszewski
2024-11-12 10:40 ` Andy Shevchenko
2024-11-12 12:50 ` Bartosz Golaszewski
2024-11-12 12:53 ` Bartosz Golaszewski
2024-11-12 13:22 ` Sebastian Reichel
2024-11-12 13:49 ` Bartosz Golaszewski
2024-11-12 12:52 ` (subset) [PATCH v5 0/4] gpio: rockchip: Update the GPIO driver Bartosz Golaszewski
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=20241112015408.3139996-5-ye.zhang@rock-chips.com \
--to=ye.zhang@rock-chips.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=elaine.zhang@rock-chips.com \
--cc=finley.xiao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mika.westerberg@linux.intel.com \
--cc=sebastian.reichel@collabora.com \
--cc=tao.huang@rock-chips.com \
--cc=tim.chen@rock-chips.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