Enable CONFIG_GPIO_SYSFS option in the Kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Trusty |
Fix Released
|
Medium
|
Kent Baxley | ||
Utopic |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
It appears we don't set the CONFIG_GPIO_SYSFS on Trusty (or Utopic?) for x86.
By enabled, I mean:
CONFIG_GPIO_SYSFS=y
This option (along with a few gpio devices) is needed to enable programming of such things as the I2C Mux through via the CPLDs on some OEM 'whitebox' switches that will leverage Software Defined Networking.
This option can, of course, be set and users can build their own kernels, but, if at all possible they'd like to keep this as stock as they can.
config GPIO_SYSFS
bool "/sys/class/
depends on SYSFS
help
Say Y here to add a sysfs interface for GPIOs.
This is mostly useful to work around omissions in a system's
kernel support. Those are common in custom and semicustom
hardware assembled using standard kernels with a minimum of
custom patches. In those cases, userspace code may import
a given GPIO from the kernel, if no kernel driver requested it.
Kernel drivers may also request that a particular GPIO be
exported to userspace; this can be useful when debugging.
Changed in linux (Ubuntu Trusty): | |
assignee: | nobody → Kent Baxley (kentb) |
status: | New → In Progress |
Changed in linux (Ubuntu Utopic): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | Confirmed → In Progress |
Changed in linux (Ubuntu Trusty): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Utopic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Trusty): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Utopic): | |
importance: | Undecided → Medium |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1342153
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.