From: Zixun LI <admin@hifiphile.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, Zixun LI <admin@hifiphile.com>
Subject: [PATCH 1/3] gpio: at91: Implement GPIOF_FUNC in get_function()
Date: Fri, 18 Oct 2024 22:27:13 +0200 [thread overview]
Message-ID: <20241018202715.283011-1-admin@hifiphile.com> (raw)
This patch adds support for determining whether a gpio pin is mapped as
peripheral function.
Signed-off-by: Zixun LI <admin@hifiphile.com>
---
drivers/gpio/at91_gpio.c | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/gpio/at91_gpio.c b/drivers/gpio/at91_gpio.c
index 1409db5dc1..64a6e8a4a5 100644
--- a/drivers/gpio/at91_gpio.c
+++ b/drivers/gpio/at91_gpio.c
@@ -220,6 +220,15 @@ static bool at91_get_port_output(struct at91_port *at91_port, int offset)
val = readl(&at91_port->osr);
return val & mask;
}
+
+static bool at91_get_port_pio(struct at91_port *at91_port, int offset)
+{
+ u32 mask, val;
+
+ mask = 1 << offset;
+ val = readl(&at91_port->psr);
+ return val & mask;
+}
#endif
static void at91_set_port_input(struct at91_port *at91_port, int offset,
@@ -550,7 +559,9 @@ static int at91_gpio_get_function(struct udevice *dev, unsigned offset)
{
struct at91_port_priv *port = dev_get_priv(dev);
- /* GPIOF_FUNC is not implemented yet */
+ if (!at91_get_port_pio(port->regs, offset))
+ return GPIOF_FUNC;
+
if (at91_get_port_output(port->regs, offset))
return GPIOF_OUTPUT;
else
--
2.46.2
next reply other threads:[~2024-10-18 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 20:27 Zixun LI [this message]
2024-10-18 20:27 ` [PATCH 2/3] gpio: at91: Implement ops set_flags Zixun LI
2024-11-12 13:21 ` Eugen Hristev
2024-11-12 16:06 ` Zixun LI
2024-10-18 20:27 ` [PATCH 3/3] gpio: at91: Implement ops get_flags Zixun LI
2024-11-12 13:13 ` [PATCH 1/3] gpio: at91: Implement GPIOF_FUNC in get_function() Eugen Hristev
2024-11-12 15:57 ` Zixun LI
2024-11-12 15:58 ` Eugen Hristev
2024-11-12 16:17 ` Zixun LI
2024-11-12 16:21 ` Eugen Hristev
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=20241018202715.283011-1-admin@hifiphile.com \
--to=admin@hifiphile.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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