diff options
| author | Zoltan HERPAI <[email protected]> | 2024-03-20 09:36:02 +0100 |
|---|---|---|
| committer | Uwe Kleine-König <[email protected]> | 2024-03-25 07:31:26 +0100 |
| commit | 9eb05877dbee03064d3d3483cd6702f610d5a358 (patch) | |
| tree | 42f52ee86555d6f3c681cf911cd622e320b6d74e /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 4cece764965020c22cff7665b18a012006359095 (diff) | |
pwm: img: fix pwm clock lookup
22e8e19 has introduced a regression in the imgchip->pwm_clk lookup, whereas
the clock name has also been renamed to "imgchip". This causes the driver
failing to load:
[ 0.546905] img-pwm 18101300.pwm: failed to get imgchip clock
[ 0.553418] img-pwm: probe of 18101300.pwm failed with error -2
Fix this lookup by reverting the clock name back to "pwm".
Signed-off-by: Zoltan HERPAI <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Fixes: 22e8e19a46f7 ("pwm: img: Rename variable pointing to driver private data")
Signed-off-by: Uwe Kleine-König <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions