Replies: 1 comment
-
|
That would typically be reported once someone requests this GPIO using the gpiod in-kernel API. Pinctrl and GPIO subsystems are somewhat related but not tightly integrated so for a free GPIO it does not look into the pinctrl internals and the flags it sets. Please assign it to some dummy driver (gpio-virtuser for instance) and see if it's reported then. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I’m working with a TI AM62-based Linux board running Kernel v6.12 and libgpiod v2.2.2.
The issue I’m facing is that when I configure some GPIOs with pull-up settings directly in the Device Tree, it works as expected—I can measure a logic high (1) on the input pins.
Below is the relevant part of the Device Tree that defines GPIO_1 as an input with a pull-up resistor:
However, when I later check the pin status using
gpioinfo -c1, it only reports the pin as an input (without showing the pull-up configuration).Does the Linux kernel expose an interface that allows libgpiod to retrieve the current pull-up/pull-down configuration of a GPIO pin?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions