summaryrefslogtreecommitdiffstats
path: root/drivers/aiodev/mc13xxx_adc.c
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2024-04-19 08:10:02 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2024-04-22 13:25:57 +0200
commit4ec1f1d2887ff37f25519536a70318d8b4934846 (patch)
tree9924b44510ad2ea5eae45deb7312874004b425ba /drivers/aiodev/mc13xxx_adc.c
parentfb6c852f5b874debe3012cf2c8a508d37ea77971 (diff)
downloadbarebox-4ec1f1d2887ff37f25519536a70318d8b4934846.tar.gz
barebox-4ec1f1d2887ff37f25519536a70318d8b4934846.tar.xz
clk: imx: composite-8m: fix muxing of core and bus clocks
The i.MX8M differntiates between three types of composite clocks (called slices): Core, Bus and IP (peripheral) clocks. How muxes are configured differs between these clocks, so the driver is populating a mux_ops variable to point at the correct struct clk_ops. Unfortunately, mux_ops wasn't actually used, leading to barebox hangs, depending on the assigned-clock-parents properties in the device tree. This oversight is likely due to the different prototypes of clk_register_composite and clk_hw_register_composite, the latter of which didn't exist when the driver was added. The API is available now, so sync the function with Linux to fix this issue. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20240419061003.2590849-3-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/aiodev/mc13xxx_adc.c')
0 files changed, 0 insertions, 0 deletions