Those entries are created by debugfs handlers in the pinctrl subsystem:
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinconf-groups
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinconf-pins
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-pins
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pinmux-functions
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/gpio-ranges
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pingroups
/sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins
/sys/kernel/debug/pinctrl/pinctrl-handles
/sys/kernel/debug/pinctrl/pinctrl-maps
/sys/kernel/debug/pinctrl/pinctrl-devices
The BeagleBone pinctrl driver is pinctrl-single implements the generic
pin_dbg_show handler with pcs_pin_dbg_show():
https://elixir.bootlin.com/linux/latest/source/drivers/pinctrl/pinctrl-single.c#L302
static const struct pinctrl_ops pcs_pinctrl_ops = {
.get_groups_count = pinctrl_generic_get_group_count,
.get_group_name = pinctrl_generic_get_group_name,
.get_group_pins = pinctrl_generic_get_group_pins,
.pin_dbg_show = pcs_pin_dbg_show,
.dt_node_to_map = pcs_dt_node_to_map,
.dt_free_map = pcs_dt_free_map,
};
The information it displays is primarily a result of the device tree
properties that the pinctrl-single drivers parses and then uses to mux
the pins appropriately.
Is there something specific that you are trying to find? Or some goal
that you are trying to accomplish?
-Drew