** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Plucky)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Koichiro Den (koichiroden)
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) => Koichiro Den (koichiroden)
** Changed in: linux (Ubuntu Plucky)
Assignee: (unassigned) => Koichiro Den (koichiroden)
--
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/2103496
Title:
Introduce configfs-based interface for gpio-aggregator
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
In Progress
Status in linux source package in Plucky:
In Progress
Bug description:
[ Impact ]
The existing 'new_device' interface for gpio-aggregator
(https://docs.kernel.org/admin-guide/gpio/gpio-aggregator.html) has several
limitations:
* No way to determine when GPIO aggregator creation is complete.
* No way to retrieve errors when creating a GPIO aggregator.
* No way to trace a GPIO line of an aggregator back to its corresponding
physical device.
* The 'new_device' echo does not indicate which virtual gpiochip<N> was
created.
* No way to assign names to GPIO lines exported through an aggregator.
While the GPIO aggregator concept is useful for resource isolation,
these limitations currently hinder its practical effectiveness. This
patch series addresses all those issues.
[ Fix ]
Apply 12 patches in total:
* Apply [PATCH 1/3] to [PATCH 3/3] from [1], which have landed in
linux-next.
* Add a "UBUNTU: [Config]" commit for the new config option
CONFIG_DEV_SYNC_PROBE.
* Apply [PATCH 2/9] to [PATCH 9/9] from [2], which are under review.
[1]
https://lore.kernel.org/all/[email protected]/
[2]
https://lore.kernel.org/all/[email protected]/
Note:
- [1] is a preparatory patch series for [2].
- [PATCH 1/9] from [2] was already picked and landed in mainline.
[ Test Plan ]
Run kselftest.
[ Where problems could occur ]
Any regressions would only impact users who load and use the
gpio-aggregator module, potentially causing issues like memory leaks or
system crashes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103496/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
