diff options
| author | Guangshuo Li <lgs201920130244@gmail.com> | 2026-09-16 00:45:37 +0800 |
|---|---|---|
| committer | Miquel Raynal <miquel.raynal@bootlin.com> | 2026-09-25 15:33:26 +0200 |
| commit | 8a485a40f45a19c5fcafb5cbee7387c2762af7c4 (patch) | |
| tree | c13d567d77453a3409b86e53ed244e5be6691652 /include/uapi/linux | |
| parent | 01947ecc37bdead7d2e1f199185b936820b90eda (diff) | |
| download | linux-next-8a485a40f45a19c5fcafb5cbee7387c2762af7c4.tar.gz linux-next-8a485a40f45a19c5fcafb5cbee7387c2762af7c4.zip | |
mtd: rawnand: nuvoton: fix clock cleanup on probe failure
ma35_nand_probe() gets and enables the NAND clock with
devm_clk_get_enabled(), but the ma35_nand_chips_init() failure path
also calls clk_disable() before returning.
devm_clk_get_enabled() registers a managed cleanup that calls
clk_disable_unprepare() on probe failure and driver removal. Calling
clk_disable() explicitly first drops the clock enable count, so the
managed cleanup attempts to disable the clock again and triggers the
clock framework warning for an already disabled clock.
Remove the redundant clk_disable() and let the managed clock cleanup
handle the clock state.
This issue was found by manual code inspection.
Fixes: 5abb5d414d55 ("mtd: rawnand: nuvoton: add new driver for the Nuvoton MA35 SoC")
Cc: stable@vger.kernel.org
Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Diffstat (limited to 'include/uapi/linux')
0 files changed, 0 insertions, 0 deletions
