summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorRosen Penev <rosenp@gmail.com>2026-09-04 17:43:34 -0700
committerBartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>2026-09-07 10:52:46 +0200
commit4d305c2273123119c27d6e4c822215e650c451e3 (patch)
tree333810bcfb61e32c52c6fe5470c6d0b2bb43737e /scripts/Makefile.thinlto
parent6f2e63ef82062a5254f43e0d499053f1e1b19f8b (diff)
downloadlinux-next-4d305c2273123119c27d6e4c822215e650c451e3.tar.gz
linux-next-4d305c2273123119c27d6e4c822215e650c451e3.zip
gpio: mvebu: name regmaps to fix debugfs collisions
Each marvell,armada-370-gpio node provides both 'gpio' and 'pwm' register windows, and the driver creates one regmap per window on the same platform device. The shared regmap_config was unnamed, so both maps defaulted their debugfs directory to dev_name(), e.g. debugfs: 'f1018100.gpio' already exists in 'regmap' because the PWM regmap (and on Armada XP the per-CPU regmap) claimed the same directory as the GPIO regmap. Give each regmap a distinct .name so the debugfs directories become '<dev>.gpio', '<dev>.percpu' and '<dev>.pwm'. This only affects debugfs naming; register access is unchanged. Assisted-by: opencode:big-pickle Signed-off-by: Rosen Penev <rosenp@gmail.com> Reviewed-by: Linus Walleij <linusw@kernel.org> Link: https://patch.msgid.link/20260905004334.177074-1-rosenp@gmail.com Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions