Switch to libgpiod and disable CONFIG_GPIO_SYSFS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Kinetic |
Confirmed
|
Undecided
|
Unassigned | ||
linux-raspi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Ubuntu kernels are built with CONFIG_GPIO_SYSFS=y after https:/
debian.
However, this interface got deprecated for removal:
https:/
https:/
"This marks the (optional) sysfs GPIO ABI as obsolete and schedules it for removal in 2020."
https:/
"THIS ABI IS DEPRECATED, THE ABI DOCUMENTATION HAS BEEN MOVED TO Documentation/
ARE SUPPOSED TO USE THE CHARACTER DEVICE ABI. THIS OLD SYSFS ABI WILL
NOT BE DEVELOPED (NO NEW FEATURES), IT WILL JUST BE MAINTAINED."
libgpiod and the use of a character file-based interface is a replacement to the sysfs interface:
https:/
Those two interfaces cannot be used interchangeably and working via libgpiod is not possible when the sysfs interface is used:
sudo gpioget gpiochip0 12
gpioget: error reading GPIO values: Device or resource busy
sudo gpioinfo | grep 12
line 12: "GPIO12" "sysfs" input active-high [used]
It would be good to switch to a newer interface since the old one does not get new features and there is no way to switch to libgpiod besides recompiling the kernel with "CONFIG_
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: kern-3230 |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1918583
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.