diff options
| author | Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com> | 2025-02-05 12:10:58 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-21 14:01:15 +0100 |
| commit | ba6ab3f04d0bae2dad76d82d427bbcec365f73a1 (patch) | |
| tree | 38239bc796113791ecf951e667c88404f0b2c387 /scripts/basic | |
| parent | 1f5b7a566e5b262fe2e72f35fb0fef7e9bd1225c (diff) | |
| download | linux-ba6ab3f04d0bae2dad76d82d427bbcec365f73a1.tar.gz linux-ba6ab3f04d0bae2dad76d82d427bbcec365f73a1.tar.bz2 linux-ba6ab3f04d0bae2dad76d82d427bbcec365f73a1.zip | |
pinctrl: pinconf-generic: Print unsigned value if a format is registered
[ Upstream commit 0af4c120f5e7a1ea70aff7da2dfb65b6148a3e84 ]
Commit 3ba11e684d16 ("pinctrl: pinconf-generic: print hex value")
unconditionally switched to printing hex values in
pinconf_generic_dump_one(). However, if a dump format is registered for the
dumped pin, the hex value is printed as well. This hex value does not
necessarily correspond 1:1 with the hardware register value (as noted by
commit 3ba11e684d16 ("pinctrl: pinconf-generic: print hex value")). As a
result, user-facing output may include information like:
output drive strength (0x100 uA).
To address this, check if a dump format is registered for the dumped
property, and print the unsigned value instead when applicable.
Fixes: 3ba11e684d16 ("pinctrl: pinconf-generic: print hex value")
Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Link: https://lore.kernel.org/20250205101058.2034860-1-claudiu.beznea.uj@bp.renesas.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/basic')
0 files changed, 0 insertions, 0 deletions