On 8/30/2024 7:13 PM, Li Zetao wrote: > There are many examples[1][2] of clk resource leakage in LTS. The > reason is that developers need to maintain the allocation and release > of clk resources themselves, but this will increase the burden on > developers. Using the API related to devm_clk_get_*_enable ensures > that the life cycle of clk is consistent with that of the device, > reducing the risk of unreleased resources like clk. > > Several other developers are also working on converting to more > secure interfaces, and this patch set is in principle the same as > theirs. ... > drivers/net/dsa/bcm_sf2.c | 28 ++---- > drivers/net/ethernet/allwinner/sun4i-emac.c | 13 +-- > drivers/net/ethernet/arc/emac_rockchip.c | 34 ++----- > drivers/net/ethernet/ethoc.c | 18 ++-- > drivers/net/ethernet/faraday/ftgmac100.c | 27 ++--- > drivers/net/ethernet/hisilicon/hisi_femac.c | 17 +--- > drivers/net/ethernet/lantiq_xrx200.c | 17 +--- > .../stmicro/stmmac/dwmac-dwc-qos-eth.c | 98 ++++--------------- > drivers/net/ethernet/sunplus/spl2sw_driver.c | 18 +--- > .../net/ethernet/xilinx/xilinx_axienet_main.c | 15 +-- > .../net/wireless/microchip/wilc1000/sdio.c | 10 +- > drivers/net/wireless/microchip/wilc1000/spi.c | 5 +- note the wifi driver changes go through the wireless tree and not the net tree so those should be split out separately
