kernel-packages team mailing list archive

[Tim Gardner <tim.gardner@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Utopic)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1342153

Title:
  Enable CONFIG_GPIO_SYSFS option in the Kernel

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “linux” source package in Trusty:
  Fix Committed
Status in “linux” source package in Utopic:
  Fix Committed

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/gpio/... (sysfs interface)"
          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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153/+subscriptions